Use a constistent syntax for ALTER DATABASE SET CHANGE_TRACKING - by Erland Sommarskog

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


8
0
Sign in
to vote
ID 312102 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 11/24/2007 2:03:10 PM
Access Restriction Public

Description

Consider this:

   ALTER DATABASE Northgale SET ALLOW_SNAPSHOT_ISOLATION ON
   ALTER DATABASE Northgale SET CHANGE_TRACKING = ON

Why this inconsistency? It is of benefit to no one.
Sign in to post a comment.
Posted by Microsoft on 1/4/2012 at 3:56 PM
Hi Erland,

I'm closing this discussion item for now.
Best regards
Jean-Yves Devant
Program Manager (Replication/CDC/CT)
SQL Server Engine Team
Posted by Microsoft on 1/4/2012 at 3:55 PM
Hi Erland,

We've looked into this. Although we would like to improve the product this way we will not have the means to do it in a foreseeable future.
That said your feedback is very valuable to us, we keep track of the suggestion.


Best regards
Jean-Yves Devant
Program Manager (Replication/CDC/CT)
SQL Server Engine Team
Posted by Erland Sommarskog on 12/4/2007 at 1:33 PM
But CHANGE TRACKING is the only that requires = for OFF and ON.

The best would be if = was permitted but not require for SET options to
ALTER DATABASE.
Posted by Microsoft on 12/3/2007 at 6:35 PM
Hi Erland

There are other examples of ALTER DATABASE settings using "=", such as for database mirroring and setting the compatibility level. I do appreciate the feedback, but the plan is to keeping the "=" syntax for change tracking. You are right that there is inconsistency in the ALTER DATABASE DDL with some settings using "=" and some settings not using the "=".

Thanks, Mark