Just an fyi.  On really large database, dropping and restoring vs. restoring over old database is waaaaay slower because of how SQL Server 2000 claims space in the database file. ...

When you do this migration, don't forget to migrate the users "correctly".  I can't tell you how many posts I've seen with people crying over this one. 

http://www.databasejournal.com/features/mssql/article.php/2228611

Have a look at SQL Sentry also.  For job management and history, that one is hard to beat.  The Idera stuff is looking good also though, so can't hurt to...

Hey Aaron, how many of the forums did you post this on?  Is this part of your daily routine? 

No.  The only way you can determine that is if you drop and recreate the table each time.  Normally, you would have these changes stored in SourceSafe or somewhere so...

SET ANSI_NULLS ON

GO

SET ANSI_WARNINGS ON

GO

CREATE PROCEDURE test

@m1 varchar(10)

as

declare @sql varchar(100)

select @sql = 'select LastName from   ' + @m1 + '.Northwind.dbo.employees'

print @sql

exec (@sql)

GO

In the window you EXEC the query,

SET ANSI_NULLS ON

GO

SET...

You should be able to look in the SQL Server Event Log and view the exact error.  Either way though, run DBCC CHECKDB on the affected database in Query Analyzer. ...

They wouldn't have a problem with Analysis Services.  If you install Reporting Services on ANY other server than the SQL Server the reports are derived from, you MUST pay reporting...

The only exception to this is if you use an active/passive server.  You then do not have to license the passive server.  If you do this, you "cannot" use the...

The only way you can find this is if the procedure or function was dropped and recreated.  SQL Server only stored the create date.  Otherwise, you would need to have...

We have the same requirements here.  We're doing a few things to insure we're compliant:

1.  Seperation of duties.  Developers can't change ANYTHING in production.

2.  Set up a trace to monitor...

There are no dependencies across databases physically.  You can write a procedure to "look for" the logical dependencies between databases, but that would be pretty hard unless you've really been...

I'm going to go out on a limb here and guess you didn't help him too much Phil. 

DECLARE

 @directory NVARCHAR(255),

 @sql NVARCHAR(2000)

IF (SELECT OBJECT_ID('tempdb..#cmdshell')) IS NOT NULL

 BEGIN

  DROP TABLE #cmdshell

 END

CREATE TABLE #cmdshell(results VARCHAR(8000))

SELECT @directory = 'c:\'

SELECT @sql = 'dir '+ @directory + ' /B /A:-D'

INSERT #cmdshell(results)

 EXEC xp_cmdshell @sql

SELECT results FROM...

??  EXEC xp_cmdshell 'dir c:\whatever\'