Comments
Sort by recent activity
Thanks for your post.
Did you get any warnings before the error occurred?
Could you cause the error to happen again and then send us the latest log located in %USERPROFILE%\Local Settings\Application Data\Red Gate\Logs\SQL Source Control 0
to SQLSourceControlSupport@red-gate.com
Also, when the problem occurred, did an exception report get generated, and were you able to send it to us? / comments
Thanks for your post.
Did you get any warnings before the error occurred?
Could you cause the error to happen again and then send us the latest log located in %USERPROFILE%\Local Settings\Applicati...
I'm not sure I completely follow what you're trying to do. You could run the query on both databases and then compare the results.
If you want to find a list of all columns that are present in both databases, then you could do something like:
Select sc.name as columnname
INTO #temp1
from db1..sysobjects AS so
Join db1..syscolumns sc on so.id=sc.id
WHERE so.[xtype] = 'U'
GROUP BY sc.name
Select sc.name as columnname
INTO #temp2
from db2..sysobjects AS so
Join db2..syscolumns sc on so.id=sc.id
WHERE so.[xtype] = 'U'
GROUP BY sc.name
SELECT [t].[columnname] [Column Name] FROM [#temp1] AS t
JOIN [#temp2] AS t2 ON [t].[columnname] = [t2].[columnname]
GROUP BY [t].[columnname]
DROP TABLE [#temp1]
DROP TABLE [#temp2]
However, I'm not sure this is what you're looking for either.
The report you're looking for isn't a function of SQL Compare, but I wish you luck trying to find a solution. / comments
I'm not sure I completely follow what you're trying to do. You could run the query on both databases and then compare the results.
If you want to find a list of all columns that are present in both...
Thanks for your post.
SQL Compare doesn't do this, but it might be something you can do yourself through SQL.
Something like the following should give you a count of identically named columns in your user tables:
select sc.name as columnname, COUNT(sc.name) AS count
from sysobjects so
join syscolumns sc on so.id=sc.id
WHERE so.[xtype] = 'U'
GROUP BY sc.name
I hope this helps. / comments
Thanks for your post.
SQL Compare doesn't do this, but it might be something you can do yourself through SQL.
Something like the following should give you a count of identically named columns in yo...
We have opened up a support ticket for you, feel free to reply to that. / comments
We have opened up a support ticket for you, feel free to reply to that.
Thanks for your post.
I think this message is telling you that you cannot use SQL Data Compare to sync the data while you are currently processing a snapshot.
"UPDATETEXT statements cannot be performed on data marked for replication while it is being extracted during concurrent snapshot processing. If you initiate an UPDATETEXT statement, you will get an error indicating that the operation is not allowed because of concurrent snapshot processing. After the snapshot is complete, UPDATETEXT statements can be performed again."[http://msdn.microsoft.com/en-us/library/aa179423(SQL.80).aspx]
This should mean that after you have completed the snapshot, SQL Data Compare should run ok.
I hope this helps. / comments
Thanks for your post.
I think this message is telling you that you cannot use SQL Data Compare to sync the data while you are currently processing a snapshot.
"UPDATETEXT statements cannot be perfo...
That's interesting about fixing this problem by changing the logging level.
We do actually have a patch that fixes this issue:
See here / comments
That's interesting about fixing this problem by changing the logging level.
We do actually have a patch that fixes this issue:
See here
Thanks for your post.
The most common way to automate SQL Data compare will be to use the command line interface.
You can then create a batch file that you can schedule through a Windows Scheduled Task.
Here is some info: http://www.red-gate.com/supportcenter/C ... 700052.htm
I hope it helps. / comments
Thanks for your post.
The most common way to automate SQL Data compare will be to use the command line interface.
You can then create a batch file that you can schedule through a Windows Scheduled ...
Thanks for your clarification.
I've been able to reproduce this now, so I've logged it as a bug with the API (CSD-127).
As a workaround for the time being, you could reset the culture immediatly after CompareDatabases e.g.
System.Threading.Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("de-CH");
I hope this helps.
I'll let you know if we get a patch out that fixes this problem. / comments
Thanks for your clarification.
I've been able to reproduce this now, so I've logged it as a bug with the API (CSD-127).
As a workaround for the time being, you could reset the culture immediatly af...
Hi Demian,
This is now fixed in the latest SQL Data compare engine.
You can download the patch for SQL Data compare here.
Or the updated SDK with the new SQL Data compare engine here.
I hope this helps. / comments
Hi Demian,
This is now fixed in the latest SQL Data compare engine.
You can download the patch for SQL Data compare here.
Or the updated SDK with the new SQL Data compare engine here.
I hope this h...
Thanks for your post.
Are you refering to the date format setting at the start of the script?
SET DATEFORMAT YMD
GO
If so, then this is just the dateformat for the session and will only be used for this one script. It doesn't need to be set back afterwards as it is only used for the session.
This session setting was added to the script in SQL Data comapre 8, to get round a problem where the dateformat for certain cultures wasn't properly scripted.
I hope this helps explain. / comments
Thanks for your post.
Are you refering to the date format setting at the start of the script?
SET DATEFORMAT YMD
GO
If so, then this is just the dateformat for the session and will only be used for...