Comments
Sort by recent activity
Sorry for the delay.
The good news is that we're going to add SQL Data Compare options to SQL Source Control in a future version, but I'm not sure exactly when that will be.
The reason that a binary comparison isn't the default is mainly because it will force a case sensitive comparison, which isn't ideal if you're using a case insensitive collation. It will also mean that the collation rules are also ignored.
However, a binary comparison does work better with non-unique indexes. / comments
Sorry for the delay.
The good news is that we're going to add SQL Data Compare options to SQL Source Control in a future version, but I'm not sure exactly when that will be.
The reason that a binar...
Thanks for your post.
Could you try turning on the command line logging? It might give a better idea where the problem is:
/logLevel:<logLevel>
Alias: /log
Default: None
Sets a minumum log level
Log files collect information about the application while you are using it. These files are useful to us if you have encountered a problem. By default, logging is disabled and no log files are stored.
Value Alias Description
None n Disables logging.
Error e Reports serious and fatal errors. For example, an error message might report a failed operation.
Warning w Reports warning and error messages. For example, a warning message might report a handled exception, or a problem which does not prevent you from using the application.
Verbose v Reports all messages in the log file.
The logs are normally created in '%USERPROFILE%\AppData\Local\Red Gate\Logs\SQL Compare' / comments
Thanks for your post.
Could you try turning on the command line logging? It might give a better idea where the problem is:
/logLevel:<logLevel>
Alias: /log
Default: None
Sets a minumum log level
L...
Thanks for your post.
It looks like the error is coming from the SQL Compare engine parsing one of your objects.
Could you try comparing the schemas using SQL Compare? It should give you a better error if it encounters errors reading the objects.
If it shows you which object it's having trouble with, could you post or email me the SQL for that object?
There might be a bug in the engine parsing some of the syntax you're using. / comments
Thanks for your post.
It looks like the error is coming from the SQL Compare engine parsing one of your objects.
Could you try comparing the schemas using SQL Compare? It should give you a better e...
Thanks for your post.
I've had a look into this and I think what you need to do is to remove the replication entries from the sysservers table in the master database.
Below is the procedure to remove the entries from the sysservers table, this was obtained and modified slightly from the procedure found in this article - http://www.dbforums.com/microsoft-sql-s ... ectly.html:
1. Run this code or query:
use master
sp_configure 'allow update',1
Reconfigure with Override
2. Go to Master---Sysservers---Open---and delete the entries for all the servers(even the Local server).
3. Now run this query to re-add the local server with 0 id:
sp_addserver '@server = YourServer'
See this KB article for further details -http://msdn.microsoft.com/en-us/library/ms174411.aspx
3. now run this query: @servername
It will return Null result.
So Stop and Restart the Services on the Sql Server and again run: @servername and this time it will return the Local server name.
4. On completion run this query:
use master
sp_configure 'allow update',0
Reconfigure with Override / comments
Thanks for your post.
I've had a look into this and I think what you need to do is to remove the replication entries from the sysservers table in the master database.
Below is the procedure to remo...
Thanks for your post.
I believe this can happen if your script folder in source control is set to SQL 2005.
The attribute for this is set in the RedGateDatabaseInfo.xml file in the root of the repository.
The database being treated as SQL 2005 can happen if the file is missing, or if the database was originally created from a SQL 2005 database.
You should be able to change the behaviour if you manually change the file to SQL 2008. If it's missing completely, you can create a new link to a blank repository and then take the XML file from that.
I hope this helps. / comments
Thanks for your post.
I believe this can happen if your script folder in source control is set to SQL 2005.
The attribute for this is set in the RedGateDatabaseInfo.xml file in the root of the repo...
Thanks for your post.
I'm afraid this still hasn't been implemented. We have the feature request logged under the code SDG-675 and I've added you as another vote for it.
There isn't much development for SQL Data Generator happening in the the near future, so I don't expect this to change any time soon.
The SDG project file is simply an XML file, so you could set something up to change the data sources as a workaround.
There isn't really much else you can do.
Sorry to not be very helpful. / comments
Thanks for your post.
I'm afraid this still hasn't been implemented. We have the feature request logged under the code SDG-675 and I've added you as another vote for it.
There isn't much developmen...
I'm not sure why this would happen. I would suggest logging a support ticket (support@red-gate.com) so it can be investigated. / comments
I'm not sure why this would happen. I would suggest logging a support ticket (support@red-gate.com) so it can be investigated.
Thanks for your post.
For this kind of error I would normally recommend that you check each of the data collection methods we use as described in this document.
However, it looks like the most significant error is the remote registry error, and you've already checked that.
When you tried connecting to the nodes registry remotely, did you perform the test from the same machine where the SQL Monitor Base monitor is installed?
It might be worth restarting the remote registry service on the server in case it's just being a bit flaky. / comments
Thanks for your post.
For this kind of error I would normally recommend that you check each of the data collection methods we use as described in this document.
However, it looks like the most sign...
Sorry your hitting this issue.
It sounds like a bug, but I don't think we know about it. When you encounter this error, do you get a chance to submit the error report (with your email)? / comments
Sorry your hitting this issue.
It sounds like a bug, but I don't think we know about it. When you encounter this error, do you get a chance to submit the error report (with your email)?
Hi Ed,
We have a new build available, but I don't think it's going to help you.
What they've added is a way to limit the number of objects that SQL Prompt caches in order to prevent SSMS crashing if SQL Prompt runs out of memory.
I don't think this will help with performance. What would be really useful is if you could send me a blank copy of your database schema and I can try and reproduce the performance issue here.
Is there any chance you could send it over? / comments
Hi Ed,
We have a new build available, but I don't think it's going to help you.
What they've added is a way to limit the number of objects that SQL Prompt caches in order to prevent SSMS crashing i...