Trooper,

Also be aware of the fact that breaking the log chain has potential issues that could be disastrous to your company. Here is an example:

Full backup at 1am yesterday

Transaction...

As a wish list - I would ask for two systems (clustered) running Windows Server 2008 x64 - 64GB RAM and 4 hex core processors to host SQL Server 2005/2008.

I...

Nope - you're not alone.

All of my training is self-taught on the job - no degree. Company won't pay for a laptop - so I bought my own, but...

Check the other scheduled processes that run during the same time. You probably have another job that is recreating that table while your maintenance plan is running. Or,...

benyos (9/6/2009)

---

You are absolutely correct.

You must use 3 part naming convention (Server.DB.Object) or even 4 part (Server.DB.Schema.Object) in order to get away with it.

If your solution refers to 10 objects...

In your situation, you need a combination of linked server and synonyms. You have to have the linked server for the connection to the other system/database unless the other...

The checkpoint won't cause you any problems - but, truncating the log breaks the log chain. You should never truncate the log unless you are fixing an unusual event...

Do you realize that 100GB is less than 10% of your 1.6TB database? Do you also realize that you want at least 10% (and probably more like 20%) space...

From what you have stated so far - I believe synonyms (or views) will work for you. I prefer synonyms because they are a little easier to manage and...

Steve Jones - Editor (9/4/2009)

---

You can shutdown SQL Server from within SSMS using SHUTDOWN as a T-SQL command. (http://msdn.microsoft.com/en-us/library/ms188767.aspx)

I almost never restart my servers from the command prompt. The GUI...

If you are looking at the first property page for the server properties, you need to understand that the number shown there as free space includes the transaction log.

It could...

HarryH (9/2/2009)

---

Was there any proper resolution to this?

I'm having the same issue with the Maintenance Cleanup Task (and xp_delete_file ) on many of my SQL 2005 servers (SP2 & SP3...

You are welcome - and it is good to hear that you are able to identify the problem.

That's great - glad you were able to get past that problem.

Instead of looking at the job history - try reviewing the maintenance plan history instead. You might find additional information there.