June 6, 2011 at 2:28 pm
Guys,
How can we make sure that an object is being modified by single user at any point of time so that changes to the object definition are not overwritten. FOr example how do we make sure that a user checksout a objects makes the changes, we are having issues where the view changes are being overwritten, does the checkin/checkout applu for databse objects through SSMS.
Any suggestions and inputs would work.
Thanks
June 6, 2011 at 4:18 pm
SQL Server does not have a check out check in process per se.
However, You could implement policies and triggers on the database to ensure that only certain people make those changes. Also, through security you should be able to limit those changes to just a handful of people.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 6, 2011 at 4:34 pm
That's called a source control system, like Team Foundation Server, Subversion, etc. Make a rule that the source control system is the official truth as to system state and that all deployments are done from source control.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply