May 28, 2013 at 12:13 am
Comments posted to this topic are about the item Change the Settings of a Database Object Using Powershell
Regards,
Ravi.
May 28, 2013 at 7:37 am
Nice short script, Ravi. Thanks for posting it.
I guess my only concern is that the defaults for SSMS are to have both of these settings "ON". If a column were somehow created with the settings off, I believe that there's a pretty good chance that the column was added by a Developer instead of a DBA. For me, that would be the "rub" because I don't allow Developers the privs to make such changes to the database.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 2, 2013 at 9:12 am
Wonderful.
Share a website with you ,
Believe you will love it.
We accept any form of payment.
June 4, 2013 at 5:31 am
You are correct, Jeff. My script will be useful for the database objects which are created in older SQL versions and left unmodified and these objects throw error when the underlying tables are changed by adding computed columns or creating indexed views.
Regards,
Ravi.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply