Activity overview
Latest activity by samjudson
I've only had a very quick job at testing it, but it looks very good so far - unfortunately on the project I am on the database setup is a bit complicated (a single 'project' can actually target multiple database, each of which is slightly different in terms of indexes, views, and in some cases even primary and clustered keys).
I definitely think there is a place for something like this in our organisation though, so will be trying to get something working on my next project I think.
Sam / comments
I've only had a very quick job at testing it, but it looks very good so far - unfortunately on the project I am on the database setup is a bit complicated (a single 'project' can actually target mu...
Thanks for the reply.
I have found out I can use the scripts folder to do the compare by just checking out of TFS. Now I just have to work out how to sort our databases out - we have a rather complicated set of databases (doesn't everyone I suppose). Each are based on the parent source controller version, but with many subtle differences unfortunately.
Sam / comments
Thanks for the reply.
I have found out I can use the scripts folder to do the compare by just checking out of TFS. Now I just have to work out how to sort our databases out - we have a rather compl...
Using without source control
Probably a silly thing to do, but is there any reason why you couldn't just use SQL Release based solely on two databases, i.e. the Schema of your 'Dev' database IS the source controlled version?
W...
Price Point?
Hi
Just wondering how this is going to be sold? Will it be part of the automation pack? Will it be sold separately? Do you know yet?
Sam
Yes, in the end I did the same, although this was a pain as I had about 30 databases to keep in sync and the indexes where all different in each on. / comments
Yes, in the end I did the same, although this was a pain as I had about 30 databases to keep in sync and the indexes where all different in each on.
Yes, that is the same kind of issue.
The only difference when you do have a full text index on both sides is that it drops the index, and the tries to create it as you have illustrated.
My original point however is that it doesn't need to drop and re-create the full text index, as the key index they are both based on are the same core index (i.e. same columns etc) but simply has a different name.
As a work around to this I've taken to renaming all my primary key indexes on all databases I am trying to sync so they are the same, which solves the main problem for me. / comments
Yes, that is the same kind of issue.
The only difference when you do have a full text index on both sides is that it drops the index, and the tries to create it as you have illustrated.
My original...
The primary key indexes are identical, apart from the system generated names, but SQL Compare is thinking the full text indexes are different because they are based on key indexes with different names.
It then drops the full text index and tries to recreate it based on the name of the primary key index in DB1, even though there is no index in DB2 with that name, so it falls over. / comments
The primary key indexes are identical, apart from the system generated names, but SQL Compare is thinking the full text indexes are different because they are based on key indexes with different na...
Primary Key difference when comparing Full Text Indexes
Hi
I have two databases, both of which have the same table, with the same primary key on them (an ID identity column, nothing unusual).
They both have a full text index on them, which includes a te...