I don't know if this problem still exists with SQL 2008, but we had multiple issues when we installed SQL 2005 onto a Windows 2008 Server cluster. We discovered that...

I agree with the poster who stated that the Model db should be changed to default to SIMPLE rather than FULL recovery mode. We have well over 200 dbs and...

There's a GUI tool available, too.

You can find all the info here: http://ftp.red-gate.com/supportcenter/Content.aspx?p=SQL%20Backup&c=SQL_Backup/help/6.2/SBU_Installingthegraphicaluserinterface.htm&toc=SQL_Backup/help/6.2/toc84715.htm

Thank you. This will be useful.

I noticed that, if you've installed multiple instances, over time, it only reports the date that the last instance was installed on the server.

andrewba (5/2/2010)

---

The 2005 SP3 release notes agree with alen - the upgrade order should be D, P, S. See http://download.microsoft.com/download/5/7/1/5718A94A-3931-457B-8567-AA0995E34870/ReleaseNotesSQL2005SP3.htm%5B/quote%5D

You are correct. Sorry for the bad info....

andrewba (4/29/2010)

---

How did this upgrade go?

I have to upgrade two SQL Server 2005 servers participating in transactional replication with updates at the subscriber. I will be starting from build...

We've used the following in a batch command file. You can of course execute that from a scheduled SQL Server Agent Job.

@echo off

echo.

echo Removing old emrRun log files

forfiles /p E:\MSSQL.1\MSSQL\BACKUPS...

Kendal Van Dyke (3/31/2010)

---

I'm guessing that's in part dueto the rewritten network stack in Windows 2008....

Good article!

I see that the Distributor Properties for the Transaction retention value is 72 hours, and the History retention value is 48 hours. These are default values. I'm curious if...

You can't use replication monitor to change these values. It won't work if you do it that way. You have to use the script that I sent. The script also...

We find that it's easiest to backup to a Backup Device, that'll have a static name. Then we XCopy that Backup device file to the server were we want to...

As I recall, there's was a bug introduced with SQL 2005 SP2 that forces you to manually enable the alert and set the time value for the threshold. We encountered...

You can just change the owner on the Job Properties screen to domain_name\group_name. Of course the group has to have the correct server role - i.e. sysadmin.

We don't use groups...

Yes - You can setup a job to use a Windows group.