Comments
Sort by recent activity
Hi Troy,
I'm afraid your syntax is correct and this is a bug with SDC 9.0 (bug ref: SDC-1243). The /include switch doesn't seem to work.
There are a few workarounds you could use for the time being:
1) Create a project in the GUI, and then reference the project file using /project switch
2) The /exclude switch still works, so you could exclude the tables you don't want.
3) Downgrade to SQL Data Compare 8
I hope this helps for now, and sorry for the inconvenience.
Regards,
Chris / comments
Hi Troy,
I'm afraid your syntax is correct and this is a bug with SDC 9.0 (bug ref: SDC-1243). The /include switch doesn't seem to work.
There are a few workarounds you could use for the time being...
Thanks for your post.
This issue is new to me, so I can't tell you exactly why it's happening.
Can you tell me:
1) Which version of SQL Data compare 9 are you using? (help> About)
2) Does this happen when you use the GUI, or is it just commandline or API?
3) Were the data scripts created by SQL Data Compare?
4) Are you checking out just the data scripts from SVN and comparing them, or are you also checking out the schema statements in the /tables folder too?
5) Could you post the DDL for the dbo.MyTable?
Thanks, / comments
Thanks for your post.
This issue is new to me, so I can't tell you exactly why it's happening.
Can you tell me:
1) Which version of SQL Data compare 9 are you using? (help> About)
2) Does this happ...
James is on holiday this week, so he's asked me to take a look at this.
Would you be able to send a SQL Compare snapshot, or a backup of the database we can look at? If we could set up a similar project we could see if we find the same issue.
If you are able to provide the schema, could you contact support@red-gate.com and we'll open a ticket.
Regards,
Chris Auckland / comments
James is on holiday this week, so he's asked me to take a look at this.
Would you be able to send a SQL Compare snapshot, or a backup of the database we can look at? If we could set up a similar pr...
Thanks for your post.
You're correct. Restoring the database with RECOVERY will only bring the database online in that particular instance. This can be done manually running the 'restore with recovery' command, or by restoring the last T-log with recovery.
You will still need to point everything that used to reference the production database to the new DR database.
I hope this helps clarify. / comments
Thanks for your post.
You're correct. Restoring the database with RECOVERY will only bring the database online in that particular instance. This can be done manually running the 'restore with recov...
Ok, I'll test this out. It sounds like a bug. / comments
Ok, I'll test this out. It sounds like a bug.
What version of SQL Data Compare are you using?
I just tried synchronising a VARBINARY(max) column with 36466 characters, and that migrated ok.
Would you be able to send me the DDL for both tables, so I can try and recreate the same project? / comments
What version of SQL Data Compare are you using?
I just tried synchronising a VARBINARY(max) column with 36466 characters, and that migrated ok.
Would you be able to send me the DDL for both tables,...
Thanks for your post.
Is the column varbinary(max) on both the source and the target table? / comments
Thanks for your post.
Is the column varbinary(max) on both the source and the target table?
Thanks for your post and I hope you don't mind me replying on Peter's behalf.
I agree that having the password in the error log probably isn't very safe. However, you can supply the backup password encrypted. e.g.
PASSWORD = ''<ENCRYPTEDPASSWORD>o5Y6c8LmZGHkzaw=</ENCRYPTEDPASSWORD>''
This encrypted string can be created when you generate the job script through the GUI. This is also preferable to storing the non encrypted password in the SQL Agent job. / comments
Thanks for your post and I hope you don't mind me replying on Peter's behalf.
I agree that having the password in the error log probably isn't very safe. However, you can supply the backup password...
Thanks for your post.
It sounds like you need to put the where clause on table b. e.g.
b.FKID = 1 / comments
Thanks for your post.
It sounds like you need to put the where clause on table b. e.g.
b.FKID = 1
Do the non default filegroups already exist on the target database?
SQL Compare cannot create the physical files because it doesn't know where to create them, but if the files are already present, then they should synchronize. / comments
Do the non default filegroups already exist on the target database?
SQL Compare cannot create the physical files because it doesn't know where to create them, but if the files are already present, ...