I've had that issue with Idera SqlSafe before...their extended stored procedures fragmented it. I'm sure they have improved since I used it, but at the time the only solution...

Making a DBA and Service account a local admin is by no means a necessity, but often makes things easier. I've worked both ways...one job I was at gave...

Clever! It would be nice if the documentation on creating an operator mentioned that you could have more than one address in there...it never occured to me to try...

E-mailing a distribution list is definatly a solution if you can convince your mail administrators to set it up for you.

Can you have an operator with more than...

Assuming your errors a mild enough to not stop the execution of the stored procedure, you can use the msdb.dbo.sp_send_dbmail stored procedure. Books online gives you all the arguments...

I've used the built in alert / database mail in SQL2005 for quite awhile and it has always worked fine for me. I've never used anything but e-mail as...

Made me nervous too...but I stumbled onto this: http://msdn2.microsoft.com/en-us/library/aa215459(SQL.80).aspx which made is sound OK. So I crossed my fingers and let it rip, and it fixed the...

We don't even have that excuse 🙂 of the 25 some-odd SQL2K boxes we have, only 3 of them are RTM, the rest are all SP3 or SP4.

Can I run that script against RTM without upgrading to SP4 first?

The objection? I said it was a long story 😛 ... We have a perfectly good...

Are you sure none of the service accounts aren't trying to run as your user and have the wrong password?

I've occasionally had Management Studio lock me out if I change...

If you are doing the backups with a script, then setting up the job is basically the same as it was in SQL 2000. The Management studio interface is...

How do you figure?

If the account that the sql server agent service is running as is a local admin, I can't imagine it's a permission issue. Did you verify that the password...

leokarp (12/21/2007)

---

If an application has embedded SQL statements and they are referencing system tables directly that may be the case of application being compatible only with a particular SQL Server...

If your vendor says his app is only 2000 compatible, I wouldn't mess with putting it on 2005, even if that DB is in 2000 compatablity mode. Even if...