Best Practice

[DrSql]

I read several Best Practcie articles stating that always reccoemnded to use DROP and CREATE objects excpet for tables when making chnages production. Can anyone give me a justification for this?


Dr.Sql
Good Luck.

 

[mrdenny]

Please like to use DROP and CREATE commands for procedures and views because there was not ALTER timestamp for when objects where changed. SQL Server 2005 now gives you a ALTER Timestamp in the sys.procedures DMV so dropping and recreating the objects isn't needed.

The down side to using DROP And CREATE commands for procedures and views is that the rights are lost each time you update the object. So if you have granted specific rights outside of your stored script you will loose them when you drop and create the object.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[DrSql]

Thank you for the quick answer.

Dr.Sql
Good Luck.

 

[mrdenny]

No problem.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog