Activity overview
Latest activity by Niall
I would agree with the original request that it would be good if SQL Compare also (optionally) migrated database settings across, that is those that this makes sense for such as 'Paramaterization' as to OP mentioned 'Allow Snapshot Isolation' and others like 'Is Read Committed Snapshot On'.
This is not the isolation level Red-Gate Compare runs under as your reply deals with but the actual settings for the database as can be accessed via SQL Server Management Studio when right clicking on the DB and choosing 'Properties' -> Options. / comments
I would agree with the original request that it would be good if SQL Compare also (optionally) migrated database settings across, that is those that this makes sense for such as 'Paramaterization' ...
General Warnings rant
Since we started using SQL Compare, which generally works well enough I have been inundated each time I do a new compare with some daft 'Warnings'
1. A Schema being owned by a user that is created ...
SQL Compare has issues with columns that include [ or ]
In our datawarehouse we use columns with the [ and ] characters in them, such as "Example.[Something].[SomethingElse]" this is to allow for script built solutions and to avoid name collisions. Unfo...
Has the auto mapping thing been made optional yet? This causes us endless issues and we almost never rename columns - being a datawarehouse. It is one of the most irritating features in SQL Compare. / comments
Has the auto mapping thing been made optional yet? This causes us endless issues and we almost never rename columns - being a datawarehouse. It is one of the most irritating features in SQL Compare.
I think the reason the performance has recently got worse is due to our increasing the number of partitions we store tables and indexes on. We have recently switched from fixed quarterly to fixed monthly partitions.
It may also be the case that using the command line version works MUCH faster than the Windows GUI one. Not sure on this yet though but a command line I kicked off earler today did finish before I bothered to check it several hours later, whereas the Windows GUI has been stuck on the reading indexes step for 3 hours since. I will run a few tests next week to see if this is the case. That the command line works is not a fix as far as I am concerned as we do need to change the project config after the schema read has happened and/or only upgrade a few tables/procs now and again (all not possible using the command line). / comments
I think the reason the performance has recently got worse is due to our increasing the number of partitions we store tables and indexes on. We have recently switched from fixed quarterly to fixed m...
Auto update stats is on and I have have also for all the system tables ran update statistics with resample. / comments
Auto update stats is on and I have have also for all the system tables ran update statistics with resample.
This is still an ongoing issue, if anything it is getting worse as the long reading indexes step now happens on smaller databases than before. / comments
This is still an ongoing issue, if anything it is getting worse as the long reading indexes step now happens on smaller databases than before.
Dire compare speed in moderate sized DBs - Workaround(?) inc
I have noted that the very very long run time for scanning indexes on medium sized Data Warehouses is still an issue with 10.4 and the index read step can take 3-4 hours for a 17k object (as Red-Ga...
Odd partioning behaviour
Where I have a table that is partioned and this has partitioned indexes if the column used by the index for the partitioning scheme differs from that used by the table then SQL Compare incorectly t...
This issue is also hitting us and SQL Compare is now taking a couple of hours to do the compare on a moderate sized DataWarehouse. Running SQL Server 2012 SP1 CU3. For reasons that I cannot detemine it only hits certain instances of SQL, especially one in which there is no data in the database. A fix would be appreciated. / comments
This issue is also hitting us and SQL Compare is now taking a couple of hours to do the compare on a moderate sized DataWarehouse. Running SQL Server 2012 SP1 CU3. For reasons that I cannot detemin...