Comments
Sort by recent activity
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 ...
Thanks for your reply.
Since I last posted to this thread, I've seen a similar issue with SQL Compare, which is the engine SQL Dependency tracker uses to read the schema.
It seems to happen if you have an unexpected null value for some extended properties. The older SQL Compare engine didn't seem to be so fussy.
Can you run the following query and see if anything is returned: SELECT major_id, minor_id, t.name AS [Table Name], c.name AS [Column Name], value AS [Extended Property]
FROM sys.extended_properties AS ep
INNER JOIN sys.tables AS t ON ep.major_id = t.object_id
INNER JOIN sys.columns AS c ON ep.major_id = c.object_id AND ep.minor_id = c.column_id
WHERE value IS null;
GO
/ comments
Thanks for your reply.
Since I last posted to this thread, I've seen a similar issue with SQL Compare, which is the engine SQL Dependency tracker uses to read the schema.
It seems to happen if you ...
Thanks for your post.
The only license information you can find through the tool is through 'Help | About'. This will tell you your serial number.
You can find out more information about your purchases if you log into http://www.red-gate.com/myserialnumbers
I hope this helps. / comments
Thanks for your post.
The only license information you can find through the tool is through 'Help | About'. This will tell you your serial number.
You can find out more information about your purch...
I've create the bug report now, so thanks for the poke.
1) The identity Insert problem.
I've confirmed this. If you use the 'ignore identity property' option and SQL Compare needs to rebuild the table. It forgets to set the identity insert when it inserts the data into the temp table. This is now logged under the bug tracking code SC-5647.
2) Constraint Names
It looks like the new constraint names are consistent with the names on the source schema, so I think this is the correct behaviour. The names are only ignored for the comparison, so a sync will always use the names from the source database.
3) Recreation of PK.
I couldn't reproduce this. The PK is actually recreated after the temp table is renamed to the correct table name, so it might just be happening further down the script to where you expect it, but it should be there.
Does this explain the behaviour, or have I missed anything? / comments
I've create the bug report now, so thanks for the poke.
1) The identity Insert problem.
I've confirmed this. If you use the 'ignore identity property' option and SQL Compare needs to rebuild the ta...
Thanks for your reply, and sorry for the delay.
I see what you mean, so I was just putting a test case together for the development team.
I'll update you with a bug reference number.
Sorry to not keep you updated. / comments
Thanks for your reply, and sorry for the delay.
I see what you mean, so I was just putting a test case together for the development team.
I'll update you with a bug reference number.
Sorry to not k...
Thanks for your post.
You're absolutely right about what it *should* be doing, but I'm not sure why it isn't in your case. I've tested it here with the same table structure, and it seems to add the identity insert statements correctly.
There must be something in the table that's causing the identity property to be missed.
Can you run the following query in SSMS and make sure that 128 is returned for status?
SELECT name, status FROM syscolumns WHERE name = 'ID_Link_Dossierbeheerder_Departement'
Can you let me know what is being changed when you sync sec_dossierbeheerder_departement? / comments
Thanks for your post.
You're absolutely right about what it *should* be doing, but I'm not sure why it isn't in your case. I've tested it here with the same table structure, and it seems to add the...
Thanks for your post.
In theory there shouldn't be any difference as they're using the same engine.
Can you make sure you're using the exact same options in both the UI and the CL?
Just to make sure, the environment variable you need to set is RGTemp (I'm assuming RBTemp was a typo in your post)
SQL Data Compare really shouldn't be throwing OOM exceptions anyway, so could you check the SQLDataCompare process in task manager and see what it gets to before the OOM is thrown? / comments
Thanks for your post.
In theory there shouldn't be any difference as they're using the same engine.
Can you make sure you're using the exact same options in both the UI and the CL?
Just to make sur...
I've had a go at reproducing this, but in my test it seems to filter out the partition function from the sql script.
Can you post the command you're using? / comments
I've had a go at reproducing this, but in my test it seems to filter out the partition function from the sql script.
Can you post the command you're using?