this means you sqlserver instance service account cannot access "'D:\MSSQL\EC_SunAmerica200805181408.bak"

btw : mentioning "failover" for most of us triggers "clustering".

With clustering, at failover time, shared disks are reconnected to the other...

Robyn Page and Phil Factor published a CLR cribsheet at

http://www.simple-talk.com/dotnet/performance/net-performance-cribsheet/

It also mentiones the ms CLRProfiler.

You can download "CLR Profiler for the .NET Framework 2.0" at http://www.microsoft.com/downloads/details.aspx?FamilyId=A362781C-3870-43BE-8926-862B40AA0CD0&displaylang=en

SQL Server 2005 Features Comparison

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

states :

Service Broker

See...

To generate a restore statement starting from a full backup, placing the new db-files at the instance default location, I use this script:

/* generate RESTORE DATABASE from backup file */

Declare...

- if you want to play it safe, make a full backup before you start.

- then perform then integrety check, so you know the data is ok before you start...

always comming to the same problem, when not storing a column according to its natural datatype. :doze:

Declare @test varchar(15)

set @test = '9:08'

select REPLICATE('0',4 - datalength(replace(@test ,':','') )) + replace(@test ,':','')

- put a clustering index on that table ! (as tight a possible)

(or rebuild its clix)

Keep in mind, by setting a clustered index, it will need to rewrite the whole...

Indeed, the only way you can do this with the standard tools of sqlserver is by restoring the backup to another dbname, script the procs and functions.

Don't forget to script...

you can even avoid the splash screen by adding /nosplash to the shortcut statement.

keep in mind the "old" syntax (*= / =*) has been anounced for deprecation since SQL7.0 sp2.

- that setting can have the effect of >30 seconds.

The main difference with the join-syntax is that you have to know

the bases of your join.

e.g

select A.col1

, B.colz

from tablea A

, tableb B

where...

Just one remark:

Keep in mind that if you generate sql scripts for that db, because you renamed the sp, sqlserver did not change the...

You need at least CU1 if you have maintenance plans in use, because that one fixes issues with maintenance plans.

Currently we are installing CU5 to all our SQL2005 instances...

Indeed, you get the huge opportuninty :

- to meet your peers and discuss issues you experience.

- to meet the MS dev team(s) / PSS / SQLCAT and discuss issues you...