We've actually decided on holding off on installing SQL Server 2000 on Windows 2003 clusters. Unless MS has fixed this in recent days, SQL Server has to come up after...

If you hide your SQL Server instance it goes from tcp/1433 (by default) or whatever you had it set to and switches to tcp/2433. This is hard-coded. If you have...

If I remember right, no. There are some shared files the installer will try and overwrite. You'll have to stop both services when you apply SP3 to avoid a reboot,...

This product is from the same guys who discovered a bunch of vulnerabilities in Oracle and SQL Server. From when my company was looking at it, it's worth the dough.

On...

Test it on a non-production system. Baseline the system beforehand. Memory usage, processor utilization, etc. Then put 'em in and try it. Of course, how will they be called? The...

It might need an active console or something along those lines. Not saying that's the reason, but I have seen programs like that. However, if that's been the only change,...

You might try something along these lines...

The ASP page sends an email that Exchange recognizes in some way. Perhaps it drops it in a folder, etc. Exchange can fire an...

No, not by any normal means. Is there a reason you need to?

If the only change has been the Oracle client, I'd start there. Is the Oracle client the same version as before? Were there any other configuration settings, etc.?

Oops. Try and replace this whole piece:

SELECT @sql = 'EXEC sp_addumpdevice ''disk'', ' +@DBNAME+

', ''C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\Diffs\''' +@DBNAME+ '_Diff.BAK'

with this:

SELECT @sql = 'EXEC...

Need to know a bit more about what the DTS package does. Post general things like, "Update a table" and "Read a file" so you don't reveal anything that might...

Change this:

''C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\Diffs\'''

to:

''C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\Diffs\'

I've removed two single quotes at the end. That tells SQL Server to add a single quote into the string.

The next question is, is there a need to do this from inside SQL Server?

This depends. If the stored procedure/view and back-end table are both owned by the same user, ownership chaining is in effect. They only need permissions on the first object. This...

When you say no one can update or delete, did you take away permissions just as a check?

Test your trigger. Create a dummy record into the table and then delete...