ramyours2003 (9/22/2009)

---

the backup files are updated in the disks showing the backups are successful but in the job history showing the failed status . The error message is

Message

[264]...

np, glad to know it helped. let us know if you need any more help

You could always go the other way, and look at it from a developer ppint of view. You could search the syscomments table and look for stored procedures that use...

You can set filters up on profiler and search for long running queries that way, or you can use some of the performance dashboard reports like performance top queries by...

Can you post the history of the job, so that we can see what you are saying

Remember to take this into account.

sp_updatestats updates only the statistics that require updating based on the rowmodctr information in the sys.sysindexes catalog view, thus avoiding unnecessary updates of statistics on...

The error...

ramyours2003 (9/22/2009)

---

we ve some backup jobs which runs daily night at 9pm , even the jobs are running fine. status is displayed as failed in job history , what...

ashaaban (9/21/2009)

---

Hi

I have been struggling to find a solution for this issue. I have a database that is about 90GB in size, I run a reindexing job on saturday around...

Yep agree with that, can you post the actual error you are receiving. already looked at the code you posted.

You have the time that the recovery model change was made, check the logs and sql job history to see what ran at that point and isolate what could have...

it is a best practise, we have 16 cpu machines here, tempdb is split, 1 mdf and 15 ndf. size has to be the same, I normally set them to...

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

If you are using...

You need to leave the settings as they are, otherwise you would hit problems

To add to this post, if this is a dedicated sql box, I would leave about 3...

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...