Comments
Sort by recent activity
BJ wrote:
Brian Donahue wrote:
Hi BJ,
This looks to be more of a command-parsing error. Have you tried enclosing all of your arguments inside double-quotes?
I have not tried that. I will try today and let you know. Thanx for the suggestion.
just for a reference, I went and looked at a log file from last week when it actually worked.
DB1 = ark01aesmdata02.AESM
DB2 = ark01aesmrep02\reports.AESM_REP
it was seperating the DBName from the Server with a "." instead of "/"
which is what it is doing now. Can you think of anything that might have made this change? or a way to set it back to use the period? / comments
BJ wrote:
Brian Donahue wrote:
Hi BJ,
This looks to be more of a command-parsing error. Have you tried enclosing all of your arguments inside double-quotes?
I have not tried that. I will t...
Brian Donahue wrote:
Hi BJ,
This looks to be more of a command-parsing error. Have you tried enclosing all of your arguments inside double-quotes?
I have not tried that. I will try today and let you know. Thanx for the suggestion. / comments
Brian Donahue wrote:
Hi BJ,
This looks to be more of a command-parsing error. Have you tried enclosing all of your arguments inside double-quotes?
I have not tried that. I will try today and ...
Here is the cmd line we are using if that helps any
utils\SQLCompare.exe /out:utils\SQLCompare.log /force /server1:ark01aesmdata02 /database1:AESM /username1:sa /password1:xxxxxxx /server2:ark01aesmrep02\Reports /database2:AESM_Rep/username2:sa /password2:xxxxxxx /synchronize /options:IgnoreTriggers
/ comments
Here is the cmd line we are using if that helps any
utils\SQLCompare.exe /out:utils\SQLCompare.log /force /server1:ark01aesmdata02 /database1:AESM /username1:sa /password1:xxxxxxx /server2:ark01a...
I am getting errors with named instances using the cmd line version
Serial Number:xxxxxxxx
Registering databases
Creating mappings
Comparing
Replaying user actions
Creating SQL
Synchronizing databases
Error: Error Comparing ark01aesmdata02/AESM vs ark01aesmrep02\reports/AESM_REP :Incorrect syntax near '\'. Incorrect syntax near '\'. Incorrect syntax near '\'.Incorrect syntax near '\'.
This error just popped up. We have been using the same instances for months, but with version 6, i am getting this error. It works fine with default instances. / comments
I am getting errors with named instances using the cmd line version
Serial Number:xxxxxxxx
Registering databases
Creating mappings
Comparing
Replaying user actions
Creating SQL
Synchronizing datab...
yes, the UI syncronizes correctly on sql 2k5. the same options are used.
good news though. while waiting for your reply, I a version 5 SQLBundle on the server, and everything worked great. I believe I am passed the problems I was having. If the testing over the next week goes correctly, we will be upgrading our old to the new.
thank you very much for your help. I am hoping it was just the old version, as it seems now!
bj / comments
yes, the UI syncronizes correctly on sql 2k5. the same options are used.
good news though. while waiting for your reply, I a version 5 SQLBundle on the server, and everything worked great. I bel...
Brian Donahue wrote:
Thanks, but the version of the dll is probably different than the executable.
sure was! sorry about that.
3.1.9.12 / comments
Brian Donahue wrote:
Thanks, but the version of the dll is probably different than the executable.
sure was! sorry about that.
3.1.9.12
ok..i posted that information in my first post. If you have any ideas on the 14 day trial, I am more than happy to try them. I installed the trial on my computer, then tried to move the files to the server where the cmd line is actually run from.
BJ wrote:
Let me start off by saying I inherited this current process, so I am at a total disadvantage. What I do know:
we are creating a new db, then using syncronize to make them the same before replicating to the new db. Assembly Version = 1.0.1.18
using commandline utility, not the GUI
BJ wrote:
I tried to d/l the latest version for the 14 day trial, but when i run the same command, i get the error:
Error: Exception of type '_3' was thrown.
/ comments
ok..i posted that information in my first post. If you have any ideas on the 14 day trial, I am more than happy to try them. I installed the trial on my computer, then tried to move the files to ...
I have corrected that, it was a few deprecated sp's.
now, i have gotten to the point where the sync will work with the gui, but i am still on the same null reference error on the command line. any thoughts on the difference?
note: the ui is a much later version. I am guessing herein lies the problem. However, when i try to run the cmd line of the new version i get the aformentioned error(post 1)
bj / comments
I have corrected that, it was a few deprecated sp's.
now, i have gotten to the point where the sync will work with the gui, but i am still on the same null reference error on the command line. any...
Brian Donahue wrote:
Hi BJ,
I have to say, our error message is completely useless. In order to find the problem, we'd either need 1. a copy of the databases in question to reproduce the problem, or 2. a crash dump of the application (would require that you know how to use a debugger).
I can't send our db for several reasons, but I did narrow the problem down to a specific area. Functions. I created a new db with no data, 2 tables, and 1 function. I get the same error on this db. Here is the function I used. CREATE FUNCTION [dbo].[fnStrParser](@strIN VARCHAR(4000))
RETURNS @UStrTable TABLE (strval varchar(100))
AS
BEGIN
DECLARE @i INT , @pos INT, @len INT
SELECT @i = 1, @pos=1, @len = LEN(@strIN)
WHILE (@pos > 0)
BEGIN
SELECT @pos = CHARINDEX(',', @strIN, @i)
IF @pos > 0
INSERT @UStrTable VALUES (SUBSTRING(@strIN, @i, @pos-@i))
ELSE
INSERT @UStrTable VALUES (SUBSTRING(@strIN, @i, @len))
SET @i= @pos+1
END
RETURN
END
GO
I can also send a script of the db if you prefer. / comments
Brian Donahue wrote:
Hi BJ,
I have to say, our error message is completely useless. In order to find the problem, we'd either need 1. a copy of the databases in question to reproduce the problem...
Thank you for the quick reply. I followed your advise, and tried to synchronize through the UI. I recieved this error.
The following error message was returned from the SQL Server:
[8102] Cannot update identity column 'RecordHistoryID'.
The following SQL command caused the error:
We have many identity columns, why would this error just now be showing? this table and stored procedure hasn't been changed since Jan '06? Does SQLServer 2005 have more stringent checks than 2000 in this area? Or is this something I can correct through SQLCompare?
thank you,
bj / comments
Thank you for the quick reply. I followed your advise, and tried to synchronize through the UI. I recieved this error.
The following error message was returned from the SQL Server:
[8102] Canno...