I think it's going to be much easier to drop the default for the Oid field in both tables and set it externally. Then the inserts to the two...

The only way I can think of to do it is to use one of the classic statement capture scripts in the trigger, eg.

SELECT B.text

FROM sys.dm_exec_requests A

CROSS APPLY sys.dm_exec_sql_text(A.sql_handle) B

where...

Obviously I don't know what's in your databasesize proc, but it should be possible to havce a single copy of that in the performance_unit (where you're writing the stats). ...

I don't have an SQL2k machine handy, but from memory syslogins is a view of the sysxlogins table. If you're after only the names then either is fine.

I think what is happening is that the stroed procedure is executing as the SysAdmin user but when it executes anything with the exec command it opens a new connection...

Under SQL2k it's master..syslogins.

In each user database there's a sysusers table, in which the SID maps back to the SID of the associated login in syslogins.

Yes, when restoring the full backup you will need to specify either the NoRecovery or Standby option, leaving the database in a state that further differential (or log) backups can...

You need to do something like this:

update Courses

set ExpDate = dateadd(year, 3, ExpDate)

from Courses a

where a.StudentId = 112

and a.CourseId = 124

and a.ExpDate = (select max(b.ExpDate)

from Courses b

where a.StudentId =...

The only thing that's truly mandatory when loading the database onto a different server is re-mapping and otherwise fixing up the logins/users.

I'm a bit lost as to why something would...

NORECOVERY and STANDBY are mutually exclusive: you can have one or the other but not both.

If you want users to be able to have read-only access to the log-shipped database...

On our systems that are used primarily for monthly reporting we reindex after the data has been loaded each month; others that are transactional systems but with a peak...

Check the file/directory permissions. If the service account SQL Server is starting under doesn't have rights to the directory/file you'll get that message.

A short-term fix might be to change...

If you're lucky this will fix it:

exec sp_replicationdboption

@dbname = N'AdventureWorks',

@optname = N'merge publish', -- just 'publish' for transactional

@value = N'false'

I haven't looked to see whether it cleans up master...

Another thing you do is to look in cliconfg to see what aliases are there.

We have instant initiailsation turned on for all our servers (SQL2k5+ that is). I know there's a theoretical overhead for every write if this is on (is page "zeroed...