This function allows you to capture the next valid error number to use in the sp_addmessage sp. No matter hoy much user errors you have define, you will always get the next available error number.
GO IF EXISTS (SELECT * FROM sysobjects WHERE name = 'fn_NroError' AND xtype = 'FN') DROP FUNCTION fn_NroError GO CREATE FUNCTION fn_NroError () RETURNS INT AS BEGIN /* Capture the last error number */DECLARE @ErrorNro AS INT SELECT @ErrorNro = MAX(Error) FROM master.dbo.sysmessages /* if it is minor that 50000 then it is a system error, so I use 50001 */IF @ErrorNro < 50000 SELECT @ErrorNro = 50001 /* if it is bigger then I use the next one */ELSE SELECT @ErrorNro = @ErrorNro + 1 /* returns the value */RETURN @ErrorNro END GO
It is used to show information from a database. It shows the creation date, it calculates the time in days, months and hours since its creation and it shows all the users with rights in that database.
2002-01-27
2,163 reads
Script that executes DBCC Checkdb in all databases, creates a log file in c:\Checkdb\ in a folder with the current date, and a file with the format: DB_Date.log Also sends each log in an attachment by Email.
2002-01-27
6,206 reads
When implementing a pilot study of audit trail triggers, you often want a way of removing all triggers in the database in order to retest your scripts: here it is!
2001-11-08
1,491 reads
Like the one posted before, the use of the SP is like this: proc_alerts 1,18. This will show the first 18 alerts on the system. OR proc_alerts 20,35 will show from 20 to 35. This lets you manage the list without letting go out of the screen.
2001-11-03
1,039 reads
If you are using OSQL or ISQL from DOS querys are really hard to use, because the result is to big for the screen. With this procedure, you can especify from wich column to wich column show the list of tables. For Example: proc_tables master, 3, 10 will show you only a short list of […]
2001-10-28
744 reads
