Comments
Sort by recent activity
Thanks for your post.
Does the error always happen at the same point with whatever backup file is used? If the backup is situated on a network share, my initial guess would be that there was some kind of network glitch that caused the connection to drop. there isn't anything in the tool to recover from a network outage, so this might be a possibility.
Would you be able to try using SQL Virtual Restore to mount the backup file?
<http://www.red-gate.com/products/dba/sql-virtual-restore/>
This will probably give you better results, as it will allow you to compare the backup file as a live database, rather than the slightly more limited comparison you can do directly through SQL Data Compare backup reader.
I hope this helps. / comments
Thanks for your post.
Does the error always happen at the same point with whatever backup file is used? If the backup is situated on a network share, my initial guess would be that there was some k...
Thanks for your post.
It sounds like you're more looking to find invalid references to objects in your schema, rather than dependencies between objects.
We have another tool called SQL Prompt 5 which has a feature called 'find invalid objects'. When you run this it will search through your database and find any objects that have bad references. i.e. references to missing columns in views, stored procedures that don't exist etc.
This might be what you're looking for.
I hope this helps. / comments
Thanks for your post.
It sounds like you're more looking to find invalid references to objects in your schema, rather than dependencies between objects.
We have another tool called SQL Prompt 5 whi...
Thanks for your post.
It sounds like SQL compare might actually be running out of memory.
Could you check how much memory the SQL Compare process is consuming? If it's over 1.5 GB, then as SQL Compare is a 32bit application and the process is therefore limited to 2GB of mem, it could be exceeding the limit.
This would mean that you have an impressively large schema, as it's pretty rare for a schema to be so large it causes SQL Compare to run OOM.
If this is the issue, then you could try a special 64bit build we have, that isn't limited to 2GB.
<ftp://support.red-gate.com/patches/SQL_Compare/SQL_Compare_8.50_x64.zip>
Please note that this version has not been fully tested, so the normal caveats apply.
I hope this helps. / comments
Thanks for your post.
It sounds like SQL compare might actually be running out of memory.
Could you check how much memory the SQL Compare process is consuming? If it's over 1.5 GB, then as SQL Comp...
I think the problem here is that when you add all database objects, then tables and stored procedures will never be independent as they will always have at least an associated schema.
You should get the results you're looking for if you only add tables and stored procedures to the diagram.
I hope this helps. / comments
I think the problem here is that when you add all database objects, then tables and stored procedures will never be independent as they will always have at least an associated schema.
You should ge...
Thanks for your post.
You can configure the way you want the aliases inserted through 'SQL Prompt 5' > 'Options' > Aliases
It's not possible to configure the shortcut keys in SQL Prompt. This is because the available shortcut keys are limited by restrictions in SSMS i.e. most key combinations are already reserved, it didn't make much sense to meke it configurable. / comments
Thanks for your post.
You can configure the way you want the aliases inserted through 'SQL Prompt 5' > 'Options' > Aliases
It's not possible to configure the shortcut keys in SQL Prompt. This is be...
Thanks for your post.
I don't believe there is any way to ignore the trailing spaces in object names. A space is considered a valid character in an object name, so the objects with the trailing spaces are considered different objects.
The 'ignore whitespace' option is more for the syntax used in object definitions, not the actual object names.
The option to 'ignore spaces in object names' is actually a SQL Data Compare option, not a SQL Compare option.
It's slightly harder to map differently named objects together in SQL Compare, as you also have to take into account all the dependant objects and map them accordingly too.
I hope this helps explain. / comments
Thanks for your post.
I don't believe there is any way to ignore the trailing spaces in object names. A space is considered a valid character in an object name, so the objects with the trailing spa...
Thanks for your post.
It's probably because the role has a dependency on the schema, and the project option 'include dependencies' is being used. This option is always selected by default, to help avoid leaving your database in an inconsistent state after a synchronization.
If you're using the GUI, you can uncheck the option on step 2 of the sync' wizard.
I hope this helps. / comments
Thanks for your post.
It's probably because the role has a dependency on the schema, and the project option 'include dependencies' is being used. This option is always selected by default, to help ...
Thanks for your post.
It sounds like there must have been some changes to the underlying tables which has caused the views to become invalid and therefore fail when they are refreshed.
You could try using the 'find invalid objects' feature of SQL Prompt 5 to help you find all these objects. At least you will be able to tell your SQL Team exactly which objects are broken.
I hope this helps. / comments
Thanks for your post.
It sounds like there must have been some changes to the underlying tables which has caused the views to become invalid and therefore fail when they are refreshed.
You could tr...
Actually, it appears the help is wrong. There has never been an option to 'ignore column order' as that is the default behaviour.
If you want to preserve column order, you can set the option 'Force column Order', but column order will always be ignored by default.
I'll inform our tech authors and get the help updated. / comments
Actually, it appears the help is wrong. There has never been an option to 'ignore column order' as that is the default behaviour.
If you want to preserve column order, you can set the option 'Force...
Thanks for your post.
The column order is actually ignored by default and won't be included in the migration script, unless you use the option 'Force column order'. However, the SQL Differences pane will highlight all textual differences.
Here is the explanation from the help: Why do identical objects have highlighted differences?
Object creation scripts may contain differences that do not affect the schema. The objects shown as different in the Results pane are those with differences that are considered meaningful. Purely textual differences, such as whitespace, are highlighted in the SQL Differences pane, even for identical objects.
You can use the Project Configuration options to control which objects are listed as different in the Results pane. Example: ignoring column order
If the order of columns in a table is different, and this difference is irrelevant to your comparison, you can set the option to ignore column order.
A table whose only difference is the order in which the columns are specified is then shown as identical in the comparison results. However, this difference is still highlighted in the SQL Differences pane.
I hope this helps explain. / comments
Thanks for your post.
The column order is actually ignored by default and won't be included in the migration script, unless you use the option 'Force column order'. However, the SQL Differences pan...