Activity overview
Latest activity by mzcopea
Redgate 7.1 for Sql 2005 64-bit
We just received Sql Compare 7.1 and we are also in the the process of moving to 64-bit Sql 2005 servers.
Two questions -
1. Can I use the executable to install your software on either a 32-bit or...
David -
That works! I never would have figured that one out. Thanks a bunch.
Abbe / comments
David -
That works! I never would have figured that one out. Thanks a bunch.
Abbe
David --
Using "/exclude:ALL:EMT.*" works too good -- it removes all objects that have EMT anywhere in the name. I need to exclude only object that begin with EMT. Do you have any other ideas?
Thanks.
Abbe / comments
David --
Using "/exclude:ALL:EMT.*" works too good -- it removes all objects that have EMT anywhere in the name. I need to exclude only object that begin with EMT. Do you have any other ideas?
Th...
Michelle: Your suggestion to use EMT.* results in anything with EMT in the name being excluded. I need for the objects that begin with EMT to be excluded. Do you have any other ideas?
David: You asked how we would like to specify the exclude filter for consideration in future releases. Ideally, what I would have liked to do is this:
/exclude:ALL:EMT.* in order to exclude all objects that start with EMT. / comments
Michelle: Your suggestion to use EMT.* results in anything with EMT in the name being excluded. I need for the objects that begin with EMT to be excluded. Do you have any other ideas?
David: Yo...
Exclude using wildcards?
Can I use wildcards with /exclude? If so, how? For example, I need to exclude all tables that start with EMT.
Thanks!
Disable Triggers using Command-line
Can we use the option to disable triggers when we use sqldatacompare from the command line? How?
System Objects - Redgate no longer ignores
A developer applied changes to ALL stored procedures under our development database, including the system stored procedures. Now when we use Red-gate to compare that database to production, Red-ga...
Excluding Tables
Our developers want to know if there is a Sql commandline option we can use to exclude their temporary tables when the compare script is created.
Thanks.
here is our commandline script:
sqlcompare.exe /snapshot1:\d:\snap\namesnap.snp /server2:servername /database2:dbname /exclude:user /exclude:role /scriptfile:D:\scripts\Test\TestSynchronizationSql.sql /force /options:forcecolumnorder,ignorewhitespace
Thanks, Jonathan! / comments
here is our commandline script:
sqlcompare.exe /snapshot1:\d:\snap\namesnap.snp /server2:servername /database2:dbname /exclude:user /exclude:role /scriptfile:D:\scripts\Test\TestSynchronizationSql....
hi jonathan,
no, the developers do not existing on the target system because we do not grant any permissions to the developers on other environments. are you saying that they need to exist on the target systems?
i should have explained that we are using the command-line sqlcompare. we have not used the "ignorepermissons" option because we thought that exluding /users and roles would exlude the permissions - would simply using the option "ignorepermissons" solve this problem?
i don't know how to disable the include dependencies, using the command-line. should we be doing this?
thanks for your help.
mzcopea / comments
hi jonathan,
no, the developers do not existing on the target system because we do not grant any permissions to the developers on other environments. are you saying that they need to exist on the ...