Viewing 15 posts - 286 through 300 (of 4,745 total)
I am afraid you cannot use the rolling upgrade method on SQL2005, you have to apply it to the active node and it does all the nodes together.
therefore you cannot...
February 20, 2014 at 9:34 am
MysteryJimbo (2/20/2014)
george sibbald (2/20/2014)
MysteryJimbo (2/20/2014)
george sibbald (2/20/2014)
MysteryJimbo (2/20/2014)
george sibbald (2/19/2014)
That in most cases will be a full backup
You don't even need a full backup to be restored. If...
February 20, 2014 at 4:28 am
MysteryJimbo (2/20/2014)
george sibbald (2/20/2014)
MysteryJimbo (2/20/2014)
george sibbald (2/19/2014)
That in most cases will be a full backup
You don't even need a full backup to be restored. If you have a...
February 20, 2014 at 4:02 am
MysteryJimbo (2/20/2014)
george sibbald (2/19/2014)
February 20, 2014 at 3:18 am
interesting, thanks for posting back solution. was it just the one job with the error, others were OK?
February 19, 2014 at 2:46 pm
I would check the errorlog immediately after the upgrade when the instance was in script upgrade mode and make sure there are no errors in there.
February 19, 2014 at 1:46 pm
you don't have to reconfigure from scratch, you can use the existing logshipping jobs and shares etc, you just need to reinitialise the database with a norecovery restore. That in...
February 19, 2014 at 10:32 am
OCTom (2/18/2014)
Answer: "I'm not really into continuing...
February 19, 2014 at 10:18 am
by running SSMS on the server you are using resources on the server.
There is usually a limit to the number of RDP connections that can be made as well.
February 19, 2014 at 10:11 am
good stuff.
February 19, 2014 at 6:23 am
dear oh dear, strange choice of column types!
February 19, 2014 at 6:04 am
please post the schema for the table, any column types such as varbinary?
February 19, 2014 at 5:43 am
500000 could be a bit over the top, it has an effect on msdb size.
February 18, 2014 at 7:36 am
Viewing 15 posts - 286 through 300 (of 4,745 total)