Something like this:

IF EXISTS( SELECT * FROM sysobjects WHERE name = 'T1' )

 DROP TABLE T1

GO

CREATE TABLE T1(  C1  NCHAR(1)  )

SET NOCOUNT ON

INSERT T1 VALUES( 'A' )

INSERT T1 VALUES( 'B' )

INSERT...

You can use DTS task - Trasfer Databases to copy database between servers, but you need to have SQL Server 2000 and it will be some extra network traffic during...

This post has information and links about linked servers configuration with Windows authentication:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=150105#bm150118

To use Windows authentication with linked servers you have to configure security account delegation. Your server has to be Windows 2000 (or 2003) in domain with Active Directory with...

With this 2 procedures you can query remaining linked or remote logins on your servers: sp_helplinkedsrvlogin, sp_helpremotelogin (execute them on both servers).

It is quite complicated task to configure linked servers with...

Did you include in your monitoring file T-SQL event class SQL:BatchCompleted ?

Yes, you should append log backups (you need all log backups for restore). And about last log - it has data just for last 10 minutes from 11 to 11:10 AM.

You don't need to do full backup because of more often logs backups. Data written to database file from log file every time when log backed up. So, before the next...

Try these webcasts (there are about SSL and SQL), may be they will be usefull:

http://www.database-security.info/Content/SQLServerWebcasts.asp

May be it would be better to run scheduled SQL Agent job with this procedure. And it is also better to run this job on nights as soon as you...

Some replication parameters require reinitialization of subscriptions. So, if you change something in replication make sure this settings do not require reinitialization.

Just a little suggestion to the topic. Why not use in dynamic SQL just fully qualified name, like this:

set @cmd = 'DELTEKCP..sp_grantdbaccess ' + @loginame + ', ' + @name_in_db...

Can you use job ID (from sysjobs table in MSDB) instead of job name as global parameter? So, the job can be renamed any time. In this case just don't recreate...

Think you look for this query to SQL Server log:

EXEC sp_readerrorlog 1, 'C:\MSSQL\LOGS\SQLlog.txt', 1, 'error'

where 'C:\MSSQL\LOGS\SQLlog.txt' - is location of your SQL serever error log, 'error' - is search string...