S.K. (8/24/2010)
CirquedeSQLeil (8/24/2010)
Here are some important points for me (some already mentioned):1. Source control.
2. Ensuring that QA or beta is exactly like production (some automated process would be good here).
3. Manual entry of the scripts into the cmd scriptlet. Too much chance for a typo.
That said, I have used the same(similar) methodology in a few places for script deployment.
Thanks for the feedback, Jason. Points one and two have been a theme here and I'll keep that in mind for future articles that are submitted. For point number 3, how would you approach that?
All in all, as a first time submitter- would you have any pointers to improve on?
I should have also noted that I thought the article was good.
One thing we use to get past that currently is to use CM to deploy scripts from specific locations in TFS. That seems to work pretty well. I am still looking for a real good method to bypass the need for typing of each of the scripts.
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