September 5, 2010 at 11:32 pm
Hi ,
i will be grateful if somebody will suggest me how to know when and what was changed in a specific stored precedure/view/function in sqlserver 2005.
September 6, 2010 at 12:45 am
You mean in the DDL of these objects ?
check database triggers !
e.g. http://qa.sqlservercentral.com/scripts/DDL+Triggers/64536/
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 6, 2010 at 5:48 pm
faheemahmad14 (9/5/2010)
i will be grateful if somebody will suggest me how to know when and what was changed in a specific stored precedure/view/function in sqlserver 2005.
Check the web for version control software. There are some fairly good products for free.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.September 7, 2010 at 5:42 am
Place your stored procedures, indeed, your entire database, into source control. Subversion is a great opensource product. Microsoft's Team Foundation Server (TFS) is fantastic as well. There are a number of reasons why you should do this, but one of the most important you've already outlined. You'll know what changed when in your stored procedures (and tables, and indexes, and...).
The only trick is, you need to also develop a process whereby you deploy from source control. There are a number of ways to do this, including Visual Studio database projects, Red Gate's SQL Source Control, and others. Find the one that works best in your environment.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply