Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DBAWinnipeg
Starting Member
3 Posts |
 Posted - 2004-05-27 : 14:58:51
|
| I thought I was going to be smart and create a trigger on sysobjects :) and SQL does not allow triggers on system tables.How can I accompish auditing on database objects?Thanks in AdvanceColin in da 'Peg |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-27 : 15:05:29
|
| You can't. It's pretty manual in SQL Server. Script out your objects into individual files. Put those files into your source control software. Then only deploy from your source control software and not from the development database. That way developers must check in their items in the software in order to get them deployed.Tara |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-05-27 : 18:25:10
|
| In Yukon, you'll be able to do that. WOO HOO!!!. We use SourceSafe for this and it works. You have to use SourceSafe for development. You have to share and branch objects into a rollout project to promote to production. Only the DBAs promote to production. Developers do not have access to promote.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
Change Control on SQL Server 2000 Database Objects