Comments
Sort by recent activity
Thanks for your post.
This could be a licensing issue. Are you evaluating the SDK, or do you have a license?
Can you make sure you have a valid licenses.licx file in your project and you have activates the tool? http://www.red-gate.com/supportcenter/C ... c68944.htm / comments
Thanks for your post.
This could be a licensing issue. Are you evaluating the SDK, or do you have a license?
Can you make sure you have a valid licenses.licx file in your project and you have activ...
Thanks for your post.
Unfortunately, the fix for this didn't make it into SQL Prompt 4. I believe the temporary workaround was to stop SQL Prompt laying out ALTER VIEW statements.
We are still working on the fix, and it is still open and scheduled for a future version. However, I'm not sure exactly when you can expect it.
For your reference the bug tracking number for this is SP-2770. / comments
Thanks for your post.
Unfortunately, the fix for this didn't make it into SQL Prompt 4. I believe the temporary workaround was to stop SQL Prompt laying out ALTER VIEW statements.
We are still work...
Thanks for your post.
Unfortunatly, we don't have a facility for you to check bugs/features yourself.
If you would like to know the status of any bugs/features, please send an email to support@red-gate.com and quote the bug reference number (if you were given one). If you don't have a bug number, could you describe the fault, and we can try and look it up. / comments
Thanks for your post.
Unfortunatly, we don't have a facility for you to check bugs/features yourself.
If you would like to know the status of any bugs/features, please send an email to support@red-...
I though I would update this post in case anybody else finds a similar problem.
There is a bug in SQL Compare 8 that causes a command line comparison to include identical objects in the script. This is where it differes from the UI as the UI knows to filter out the identical objects.
All that happens when the identical objects are included in the script is that sp_refreshview will be scripted for each view in the schema.
The bug reference for this issue is SC-4542 and is scheduled to be fixed in the next minor release.
As a workaround for this issue, you can add /exclude:Identical to the command to remove the sp_refreshview statements. / comments
I though I would update this post in case anybody else finds a similar problem.
There is a bug in SQL Compare 8 that causes a command line comparison to include identical objects in the script. Thi...
Can you confirm that the public card, i.e. the one that you are trying to connect to, is the top binding card.
To find this, go to the machine that the alert repository is on and go to Network Connecitons > Advanced (along top menu bar) > Advanced Settings.
SQL Response automatically looks for the top card, therefore if the card that you are connecting to isn't at the top then you will have issues.
I hope this helps. / comments
Can you confirm that the public card, i.e. the one that you are trying to connect to, is the top binding card.
To find this, go to the machine that the alert repository is on and go to Network Conn...
Thanks for your post.
My initial suspicion is that SQL Data Compare was unable to automatically map the tables together.
SDC can only automatically map the tables if the table contains a PK, unique index or unique constraint. If the table doesn't have one of these set then SDC doesn't know what to use for a comparison key, and leaves it up to you to choose one.
If this is the case, then the easiest way to get round this will be to set up a GUI project where you set all the custom comparison keys, and then call the GUI project file from the command line. e.g. sqldatacompare /project:myProject.sdc /sync
You set the comparison keys in the 'Tables & Views' tab.
I hope this helps. / comments
Thanks for your post.
My initial suspicion is that SQL Data Compare was unable to automatically map the tables together.
SDC can only automatically map the tables if the table contains a PK, unique...
Thanks for your post.
The reason the table is at the bottom of the list is because once you have referenced a table, SQL Prompt assumes that it's the last table you would want to reference again. I guess they didn't think about self joins [image]
I have logged this as a bug with SQL Prompt 4. Hopefully it will be addressed in a future version.
For your reference the bug tracking code for this issue is SP-2882. / comments
Thanks for your post.
The reason the table is at the bottom of the list is because once you have referenced a table, SQL Prompt assumes that it's the last table you would want to reference again. I...
Thanks for all the info you have supplied.
It seems that the reason you're having this problem with version 6.3 is because of a bug with the 'Kill existing Connections' option. If you don't use this option, your restore should work correctly.
However, you will have to make sure yourself that there isn't any other connections to the database before you attempt the restore.
I have logged this as a bug with SQL Backup 6.3, and it should hopefully be fixed in future release.
For your reference the bug tracking code for the issue is SB-4446.
Sorry you found this fault, but thanks for letting us know. / comments
Thanks for all the info you have supplied.
It seems that the reason you're having this problem with version 6.3 is because of a bug with the 'Kill existing Connections' option. If you don't use thi...
Thanks for your post.
The error message isn't very informative, so I can't say for sure why you're getting this error.
I suspect that you are possibly backing up over a network and this error is caused by some kind of connection loss.
If you are backing up over a network, then you might like to consider upgrading to SQL Backup 6 as this version contains some network resilience features to retry after any network related failures.
If you do not wish to upgrade, then I would recommend backing up to a local drive first, and then copy the file to the network location using the COPYTO command.
If you are already backing up locally first, can you post the backup script you are using, and I’ll see if there could be anything else that might be causing this error.
I hope this is helpful. / comments
Thanks for your post.
The error message isn't very informative, so I can't say for sure why you're getting this error.
I suspect that you are possibly backing up over a network and this error is ca...
I see what you mean.
I have logged this as a bug with SQL Prompt. Hopfully it will be addressed in a future version of the tool.
For you reference, the bug tracking code for the issue is SP-2879. / comments
I see what you mean.
I have logged this as a bug with SQL Prompt. Hopfully it will be addressed in a future version of the tool.
For you reference, the bug tracking code for the issue is SP-2879.