Viewing 11 posts - 1 through 11 (of 11 total)
Until 2012, all of the previous versions of MS SQL kept the user info in the master DB. If you restore a DB to another server, those User IDs will...
May 28, 2013 at 7:14 am
OK... final update!!!
I dropped and recreated the three SPs only. I then re-ran the maintenance to see if those three errors were gone. When the maintenance ran, it had a...
May 15, 2009 at 4:50 pm
GilaMonster (5/15/2009)
Are those procs? If so, script them, drop them and then recreate them.
Three of them are and I am doing that right now.
The one is a table...
May 15, 2009 at 4:12 pm
Paul Randal (5/15/2009)
As background, someone manually changed the system tables on the database before you upgraded.
Ugh... that is not good....
May 15, 2009 at 4:10 pm
Thank you for the fast help!
I ran the query in the database that has the problem and got this result back;
SELECT Object_Name(16823222)
go
U_updateBOUserPhoneNumber
SELECT Object_Name(16055143)
go
U_Phone_Number
SELECT Object_Name(32823279)
go
U_updateSitePhoneNumber
SELECT Object_Name(48823336)
go
U_updateUserPhoneNumber
May 15, 2009 at 4:01 pm
Greg Charles (4/15/2009)
April 15, 2009 at 11:43 am
Hey Paul,
Sorry for the late reply, but the hot fix worked. After I installed it and re-ran the maintenance, I found two databases that had corruption. One seemed to have...
April 15, 2009 at 4:39 am
Thanks Paul,
As I was downloading the patch, I see that SP3 is out there. What do you think of that? Has there been any issues with that patch? Would...
April 13, 2009 at 12:11 pm
Paul Randal (4/13/2009)
Ah - ok you've definitely still got a corrupt database then. Do you have any output from the maintenance job(s)? One of them should be failing every night...
Hey...
April 13, 2009 at 11:21 am
Paul Randal (4/13/2009)
It's entirely possible (and likely) that the error...
April 13, 2009 at 10:39 am
Paul Randal (4/13/2009)
April 13, 2009 at 10:04 am
Viewing 11 posts - 1 through 11 (of 11 total)