Comments
Sort by recent activity
We worked on this issue and it seems that turning off the option to support 'linked servers' resolved the issue. Something to do with the linked server was triggering the Windows Authentication errors in the background. We are going to look into this to see if there's anything we can do to prevent these from occurring in the future. / comments
We worked on this issue and it seems that turning off the option to support 'linked servers' resolved the issue. Something to do with the linked server was triggering the Windows Authentication err...
I think that the following document should help answer your question - http://www.red-gate.com/supportcenter/C ... onTags.htm
You can add tags to your backup location to add a datetime stamp. For example if you want your backups to go to separate folders based on datetime you can make the path similar to the following:
C:\Backups\<DATETIME yyyymmdd>\<database>.sqb
This would save your full backups in a folder named the date that they were created and the backup file would be named the same as the database backed up e.g.
C;\Backups\20080929\Adventureworks.sqb / comments
I think that the following document should help answer your question -http://www.red-gate.com/supportcenter/C ... onTags.htm
You can add tags to your backup location to add a datetime stamp. For ex...
We are aware that comparing databases with merge replication enabled is significantly slower than without. I have already raised an issue in our tracking software with regards to this and I will add your comments to it, to help increase it's importance. This will be reviewed for inclusion in a future release.
For your reference the issue tracking code is: SC-3677 / comments
We are aware that comparing databases with merge replication enabled is significantly slower than without. I have already raised an issue in our tracking software with regards to this and I will ad...
I take it that you've tried refreshing the schema, after opening your project? This should go and 'grab' the latest version of your schema including the recent changes. Just click the 'Refresh Schema' button next to the 'Save Project' button.
If you've already tried this without success could you give me a little more information? i.e. what was the data type of the column changed from and to? / comments
I take it that you've tried refreshing the schema, after opening your project? This should go and 'grab' the latest version of your schema including the recent changes. Just click the 'Refresh Sche...
Thanks for all of the information that you've provided, it will definitely help us track down the cause. I'll add all of this to the bug entry and hopefully the developers will get this fixed in the next version of SQL Prompt. / comments
Thanks for all of the information that you've provided, it will definitely help us track down the cause. I'll add all of this to the bug entry and hopefully the developers will get this fixed in th...
I'm sorry that you experienced this error. Has this only occurred the once or is it something that you're able to reproduce? I've raised a bug in our tracking database for this issue which the developers will look into. For your reference the bug tracking code is: SP-1351 / comments
I'm sorry that you experienced this error. Has this only occurred the once or is it something that you're able to reproduce? I've raised a bug in our tracking database for this issue which the deve...
I've given this a try and I experience the same issue as you. When adding constraints and indexes, SQL Prompt doesn't supply you with the correct column options e.g.
ALTER TABLE table1 ADD PRIMARY KEY NONCLUSTERED<prompt>
won't give the available columns from table1. This is something that we can definitely improve upon. Therefore I have raised it in our bug tracking software for the developers to look at. They are currently working on the next version of SQL Prompt and hopefully this is something that they'll be able to implement in this next version. / comments
I've given this a try and I experience the same issue as you. When adding constraints and indexes, SQL Prompt doesn't supply you with the correct column options e.g.
ALTER TABLE table1 ADD PRIMARY ...
Does this affect multiple servers or just one in particular? Does it seem to affect long running queries or all types of query? This is generally a basic connectivity error meaning the client could not connect to the target SQL Server. The fact that it occurs randomly makes it fairly tricky to troubleshoot.
If there's constantly an issue connecting it can be down to the protocols that you have enabled, firewalls etc. However in your case this doesn't seem to be the cause as sometimes it connects and sometimes not. Do you have TCP/IP enabled on the SQL Server as well as Named Pipes? You can check this by opening the Server Network Utility. If so could you try connecting to the server using TCP/IP to see if it causes the same issues? If you're using a port other than the default 1433 then you'll have to force this in the connection string. When adding the server to your distribution list, choose 'Add a SQL Server not listed' and add the server name with the port number appended afterwards e.g. SERVERNAME\INSTANCENAME,1234
Also, is the network that you're working across fairly solid? Have you checked to see whether there were any network issues at the times that the errors were thrown? / comments
Does this affect multiple servers or just one in particular? Does it seem to affect long running queries or all types of query? This is generally a basic connectivity error meaning the client could...
I'm sorry that you're experiencing this issue, it seems that this something that has been introduced into SQL Data Compare 7. The developers are well aware of this problem and are working on a fix for it as we speak. There should be a patch released within the next few weeks. I will notify you as soon as it is available.
You may be able to work around the issue for the time being by outputting the synch script and running it in your SQL Server sql editor. Making sure that you manually add SET LANGUAGE 'US_ENGLISH' before running the script. / comments
I'm sorry that you're experiencing this issue, it seems that this something that has been introduced into SQL Data Compare 7. The developers are well aware of this problem and are working on a fix ...
Thank you for the feedback. I have raised this suggestion as a feature request in our tracking software. The developers will consider implementing this in the next version of SQL Prompt. / comments
Thank you for the feedback. I have raised this suggestion as a feature request in our tracking software. The developers will consider implementing this in the next version of SQL Prompt.