I talked about this topic in an article:

SQL Server Security: Dealing with Anti-Virus Programs

SQL Server is going to use the Oracle client in order to do this. If that's the case with a linked server connection, it's going to be true of a...

Take a look at the following document:

Microsoft Windows Server 2003 Security Guide

It has a lot more than just the services. But it'll invaluable to you for...

Registry:

Regular Instance:

Edition: HKLM\Software\Microsoft\MSSQLServer\Setup\Edition

Version: HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion\CSDVersion

Named Instance:

Edition: HKLM\Software\Microsoft\Microsoft SQL Server\<InstanceName>\Setup\Edition

Version: HKLM\Software\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer\CurrentVersion\CSDVersion

I don't think Costa Rica has had the insurgency problems like El Salvador. Also, we've not had a major issue with it like we did with Panama under Noriega. No,...

I still remember taking bus trips around Oahu for 25 cents. Granted, that was the late 70s, but that probably started me along that path.

Lived in Japan as a...

Even reboots sometimes don't fix the issue. Hence the reason MS recommends using sa.

You can remove BUILTIN\Administrators but before you do, make sure the SQL Server Service account and the Cluster service account have the ability to login and are members of the...

Check the access on NEWDB1 ad NEWDB2. As indicated, there may have been something in Model. Or something else may have gotten added.

Are the two logins both in a group that has access to the databases in question?

Costa Rica doesn't have a formal military, but it does have "military" forces:

CIA - The World Factbook: Costa Rica

My thoughts and prayers are with the folks...

Are the logins you're testing with Windows logins or SQL Server logins?

Yup, I'd probably turn her down and I can't remember the last time I actually looked at a car magazine... I think it a few years ago when a buddy...

I'm not stuck with my Saturn. It's all I need and I've never had a desire for anything more.

It's a known issue. The workaround from Microsoft is to configure the job to run as sa. More here:

How to troubleshoot a SQL Server 8198 error...