If you see from the management prospective and incase you SQL in on mixed mode authentication, you can approach the windows user group.

In my environment, I have clubbed all users...

The most possible reasons are already stated, May be the job itself or the schedule is disabled.

Can you try pointing the job and schedule again from Maintenance plan?

This week I am splitting my TempDB file to the number of physical CPUs (8 dual core) for an upcoming production environment.

Seems like your job is able to backup but one or many of its steps or Part is raising error message. To trouble shoot, pull out the script in QA...

Just a suggestion, incase you mean to say you are not aware what this error number 2812 means, you can look in to the sysmessages table for error massages.

Hi krypto69,

What Security mode your linked server is using?

Basically, seems like your linked server user account is failed to handshake with the partner server and that's why SQL Server...

Okay, and what was the problem? Something related to schema?

Silverfox (9/22/2009)

---

Nope, MSSQL.(number) is dependent on the components that are being installed and the order in which they are installed

If you are...

if you are a OKAY in scripting, you may like it.

SP_MSFOREACHDB

SP_MSFOREACHTABLE

oraculum (9/21/2009)

---

Hi Everyone!

Just thought I would update you, I tried a clean restore of the database and ran a rebuild index job then a shrink, and blow me down with...

Okay, what was that problem?

Timothy.Cloud (9/21/2009)

---

So I get an email from the boss on Sunday.

Turns out that he decided to upgrade the production SQL 2005/Windows 2003 (both 32-bit) from 16gb of RAM to 32gb...

espanolanthony (9/21/2009)

---

I am using SQL Server 2005. i have 3 jobs that runs full bak, differential baks, and a transactional backups.

now as of now i need to show...

Generally its "Drive:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportManager\Home.aspx"

gk-411903 (9/21/2009)

---

I am new to this SQL Server stuff. I am seeing the error below in our Project Server

running on SQL Server 2005.

Message

Sourcespid77

A read operation on a large object failed...