Comments
Sort by recent activity
Hi Aaron,
The UI currently uses your locale to format date times (not the servers). We are just about to release 5.1 so I cannot see this making it into that release however I have added your request to our tracking system and it will be review for future releases.
Sorry that I cannot be of more help,
- James
--
James Moore
Red Gate Software Ltd / comments
Hi Aaron,
The UI currently uses your locale to format date times (not the servers). We are just about to release 5.1 so I cannot see this making it into that release however I have added your reque...
Hi there,
This is a bug in SQL Data Compare however it was classified as unlikey to occur for a customer so didn't get fixed - Sorry [image] - the reason it is happening is you have a very large number of Key columns which are normally fixed to the left of the grid and the scroll bar appears to the right of the key columns under the non-key columns - the best work around I have for you at this second is to resize your key columns so they take less space up and your non key columns will then be scrollable (the scroll bar will be at the end of your key columns) - Hope this makes sense.
Sorry that you have been affected by this issue and it will be reviewed to be fixed in future versions.
- James
--
James Moore
Red Gate Software Ltd / comments
Hi there,
This is a bug in SQL Data Compare however it was classified as unlikey to occur for a customer so didn't get fixed - Sorry - the reason it is happening is you have a very large number of...
I dont think that SQL Dependency Tracker can do this easily (I'm sure Dan will confirm this or tell you how to achieve what you want later on) however you might want to look at our SQL Compare Tool (http://www.red-gate.com/products/sql_compare/index.htm). If you compare your current database against an empty database it will create a schema creation script for you with all of the dependencies in the right order.
SQL Data Compare can be used to migrate the data.
Hope this helps and glad you like the tool!
- James
--
James Moore
Red Gate Software / comments
I dont think that SQL Dependency Tracker can do this easily (I'm sure Dan will confirm this or tell you how to achieve what you want later on) however you might want to look at our SQL Compare Tool...
The other possibility of the process hanging at 100% with that amount of rows/tables would be during clean up where its taking a while to clean up the temporary files used before recomparing the database.
Having said that though I would have expected the transaction to have been committed by that point so that changes should have taken affect. What happens if you attach a profiler to your SQL Server when its hanging - is any SQL being executed? If you run sp_who2 do you still see connections from Data Compare etc and what state are they in?
--
James Moore
Red Gate Software / comments
The other possibility of the process hanging at 100% with that amount of rows/tables would be during clean up where its taking a while to clean up the temporary files used before recomparing the da...
Hi Robert,
The way to do this is to choose the Export Comparison Results menu item from the Tools menu then export everything - this will create a load of files in the target directory - 4 for each table and 1 called Results Summary.csv - the results summary contains the same information as the main grid - you should then be able to load it into excel. Each of the other files contains the actual data for each table in CSV if you do not need these you can delete all but the Results Summary.csv file after the export.
Hope this is what you are looking for.
- James
--
James Moore
Red Gate Software Ltd / comments
Hi Robert,
The way to do this is to choose the Export Comparison Results menu item from the Tools menu then export everything - this will create a load of files in the target directory - 4 for each...
You are indeed correct - this is an inconsistency caused by using sp_rename. The stored proc is renamed but its definition SQL is not - SQL Compare uses the definition SQL and thus this is where the problem arises - it can be resolved as you correctly point out by updating the definition SQL.
- James
--
James Moore
Red Gate Software Ltd / comments
You are indeed correct - this is an inconsistency caused by using sp_rename. The stored proc is renamed but its definition SQL is not - SQL Compare uses the definition SQL and thus this is where th...
You can always use ADO.NET to run the script.. have a look at the following: http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlcommand.aspx
You might also want to look at the SqlConnection object.. but it should be fairly easy to put some code together which uses ADO.NET.
Hope this helps,
- James
--
James Moore
Red Gate Software Ltd / comments
You can always use ADO.NET to run the script.. have a look at the following:http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlcommand.aspx
You might also want to look at the SqlConn...
This looks a little strange.. you should have version 2.8.x in there rather than 2.6 - can you try reinstalling MDAC 2.8 as it seems somthing might have installed 2.6 back over it.
Also if you could follow the steps in http://support.microsoft.com/?kbid=301202 to check your MDAC version as well please (The first part not the registry part).
Many thanks,
- James
--
James Moore
Red Gate Software / comments
This looks a little strange.. you should have version 2.8.x in there rather than 2.6 - can you try reinstalling MDAC 2.8 as it seems somthing might have installed 2.6 back over it.
Also if you coul...
Can you please let me know the value of the registry key under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\FullInstallVer
Many thanks,
- James
--
James Moore
Red Gate Software / comments
Can you please let me know the value of the registry key under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\FullInstallVer
Many thanks,
- James
--
James Moore
Red Gate Software
This error seems to be related to SQL Server Collations and having different collations across two tables you are trying to join. I'm not sure why SQL Backup would cause this problem however you might want to look at http://www.ssw.com.au/SSW/KB/KB.aspx?KBID=Q211874 and see if it resolves the issue for you.
If not please repost here and also post the statement which is generating this error.
Many thanks,
- James
--
James Moore
Red Gate Software / comments
This error seems to be related to SQL Server Collations and having different collations across two tables you are trying to join. I'm not sure why SQL Backup would cause this problem however you mi...