How can we help you today? How can we help you today?
chengvoon.tong
Activity overview Badges (0) Posts (13) Comments (5)

Comments

Sort by recent activity
We have reached a point with the implementation of SQL Compare’s support for SQL Server 2014 where we really need help with how the community wants us to handle a scenario: Microsoft’s first cut of memory-optimized tables and natively compiled stored procedures in SQL Server 2014 does not allow schema/ddl operations inside of transactions. As SQL Compare wrap all operations up in transactions by default - to ensure we don’t leave a database in a partially deployed state - we have a conflict of behavior. Whilst it is possible to disable transactions most people don’t for the obvious reasons. We have come up with a number of possible ways to address this issue: 1) Only allow MOTs and NCSPs to be scripted when you have transactions disabled. We would add extra error checking to the scripts SQL Compare generates so they would fail on the first error encountered. If the script fails through connection error, permission violations or an illegal schema operation we would provide users with information about where the failure occurred and a suggested course of action. However, users would have to carry out these actions themselves. If users wanted to still use transactions for their non memory-optimized objects they would have to carry out deployments in two phases – migrating the MOTs and NCSPs with the transaction option disabled and then migrating the rest of their database with the transaction option enabled. In addition to this we could provide extra functionality which would help with the recovery of the database to its intended new state or roll back to the pre deployment state, for example: a. Creating a backup at the start of the script b. Creating a SQL Compare snapshot at the start of the script (although this would not help with recovering data) c. For recovering data that might have been dropped as part of schema operations we would have to create extra tables in the target database during the deployment to safely hold data until the deployment completed. 2) Have SQL Compare generate a script which has all the MOT and NCSP schema operations at the top of the script in a non-transactional area, followed by the non memory-optimized work in a transactional area. If a failure occurred the database would still be left in an inconsistent state which users would have to recover themselves, as we cannot rollback the non-transactional area, however this would be reduced to just the MOT and NCSP objects. We feel that (2) offers nicer behavior. However, as our user base covers a wide range of experience types, from accidental DBAs to SQL gurus, we are concerned that not all of them will be aware of the limitation that memory-optimized objects have to be deployed outside of transactions. Therefore, they may get an unpleasant surprise when they discover that our previously entirely transactional scripts are now only partly transactional. Admittedly users of MOTs and NCSPs will be working with the Enterprise edition of SQL Server, therefore this change isn’t going to affect all users. The main question is, how upset will people be if their ‘transactional’ script turns out to not cover MOTs and NCSPs? There is a precedent for this as users/schemas creation is problematic in transactions, although this is fairly lightweight when compared to tables. Any thoughts about these options from the community would be gratefully received. Thanks, SQL Compare Team / comments
  1. Community
  2. SQL Compare 11
  3. SQL Compare beta v11.0.0.226 & we need your help!
We have reached a point with the implementation of SQL Compare’s support for SQL Server 2014 where we really need help with how the community wants us to handle a scenario: Microsoft’...
0 votes
Yes, indeed. / comments
  1. Community
  2. SQL Data Compare 11
  3. SQL Data Compare beta v11.0.0.120 is now available
Yes, indeed.
0 votes
Hi gildemandware, We are hoping to do v11 release within a month. Thank you for your patience. SQL Data Compare Team / comments
  1. Community
  2. SQL Data Compare 11
  3. SQL Data Compare beta v11.0.0.120 is now available
Hi gildemandware, We are hoping to do v11 release within a month. Thank you for your patience. SQL Data Compare Team
0 votes
We've now released v11.0.0.198. Please could you try installing the new beta version and see if it fixes your issue? I'd like to point out that this version is timebombed to expire on 30 September 2014 and you'd see trial expired issue if your system date had been interfered after installation. / comments
  1. Community
  2. SQL Compare 11
  3. Expired trial error
We've now released v11.0.0.198. Please could you try installing the new beta version and see if it fixes your issue? I'd like to point out that this version is timebombed to expire on 30 September ...
0 votes
Thanks for your message. We're currently looking into the issue. It'd be greatly appreciated if you could let us know what version you upgraded from. / comments
  1. Community
  2. SQL Compare 11
  3. Expired trial error
Thanks for your message. We're currently looking into the issue. It'd be greatly appreciated if you could let us know what version you upgraded from.
0 votes
Total activity
21
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
3