Re: Tracking Stored Procedure changes
From: Erland Sommarskog (sommar@algonet.se)
Date: 07/27/02
- Next message: Erland Sommarskog: "Re: Transaction Log"
- Previous message: BP Margolin: "Re: Column level security"
- In reply to: Neal Wright: "Tracking Stored Procedure changes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Erland Sommarskog <sommar@algonet.se> Date: Sat, 27 Jul 2002 21:45:34 +0000 (UTC)
Neal Wright (nwright@edgewater.com) writes:
> I recall earlier versions of SQL Server contained an
> update timestamp for tracking stored procedure
> modifications. Does anyone have any idea if this is
> possible in 2k? I see that 2k has a version number of
> sorts in the sysobjects table but this merely notes that
> it has been modified.
In SQL 6.5 your only option when you changed a stored procedure was
to drop the existing version and then create it anew. This way
sysobjects.crdate would reflect when the procedure last was updated
in the database.
In SQL7/SQL2000 you can change the procedure with ALTER PROCEDURE which
does not change sysobjects.crdate. It appears though that
sysobjects.schema_ver is updated each time, so if you save the previous
value, you can tell that someone has fiddled with the procedure, but
you cannot tell when.
-- Erland Sommarskog, SQL Server MVP sommar@algonet.se Books Online (updated!) for SQL 2000 at http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
- Next message: Erland Sommarskog: "Re: Transaction Log"
- Previous message: BP Margolin: "Re: Column level security"
- In reply to: Neal Wright: "Tracking Stored Procedure changes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
