Comments
Sort by recent activity
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...
Thanks for your post.
The number of columns in a table can be a cause of performance issues, but since you have other tables with more columns then it might not be the problem.
Would you be able to send me the table structure of TableA and TableB and I'll try and reproduce the issue here? / comments
Thanks for your post.
The number of columns in a table can be a cause of performance issues, but since you have other tables with more columns then it might not be the problem.
Would you be able to...
Many thanks for the information.
The number of rows in any particular table shouldn't matter, but the cumulative effect of having lots of tables with a large number of columns is an issue we've seen before.
We are actually working on a version of SQL Prompt that will handle schemas with a large number of objects better, which is (optimistically) going to be available on Friday 9th March.
We are also going to reinstate the feature to ignore certain databases at some point, but I don't think it's going to appear in the release on Friday.
I'll let you know on Friday if you can try the new version on not. / comments
Many thanks for the information.
The number of rows in any particular table shouldn't matter, but the cumulative effect of having lots of tables with a large number of columns is an issue we've se...
Thanks for your post.
I wasn't aware that upgrading would break the old project files, so I'm sorry this is happening.
Are you able to recreate the project in the new version? Has this happened to all your existing projects? / comments
Thanks for your post.
I wasn't aware that upgrading would break the old project files, so I'm sorry this is happening.
Are you able to recreate the project in the new version? Has this happened to ...