Viewing 7 posts - 1 through 7 (of 7 total)
I've seen this happen before. Deleting the maintenance package and re-adding it solved it for me.
October 27, 2009 at 12:19 pm
We name our backup files w/ date/time stamps, so it's always clear on which date they were created. The standard SQL Backup job in the maintenance plan does this for...
October 13, 2009 at 8:24 am
john.woods (10/8/2009)
The full backup takes...
October 12, 2009 at 4:07 pm
I'd suggest to create a linked server to your production server and then query the system tables on your production server to see what the filename(s) of the last full...
October 12, 2009 at 3:53 pm
Seems like your biggest problem was that the nodes didn't see the disks. Did you get that resolved?
September 22, 2009 at 12:20 pm
Actually.. nevermind... I figured it out.
The correct query is:
SELECT DISTINCT tblAid.dtmAidDate, tblAid.intSendingNation, tblSendingNations.strNationRuler as strSendingNationRuler, tblSendingNations.strNationName as strSendingNationName, tblSendingNationsInAlliance.strAllianceName as strSendingAllianceName, tblAid.dblMoney, tblAid.dblSoldiers, tblAid.dblTech, tblAid.intReceivingNation, tblReceivingNations.strNationRuler AS strReceivingNationRuler, tblReceivingNations.strNationName as...
July 20, 2009 at 8:35 am
I've had this same issue. This isn't really related to just clusters. It's the same on a stand-alone SQL Server 2005 that does not have a power of 2 number...
July 14, 2009 at 10:17 am
Viewing 7 posts - 1 through 7 (of 7 total)