Viewing 15 posts - 3,991 through 4,005 (of 7,503 total)
Those shouldn't be a problem:
February 20, 2009 at 1:43 am
That's just SQLServer performing the internal db upgrade at restore time if your backup originates from a lower version.
That also occurs if you attach a db from a lower version.
And...
February 20, 2009 at 12:06 am
Judy (2/19/2009)
February 20, 2009 at 12:03 am
what software level are you on ?
select @@version
You are using a login that is member of the sqlserver administrators group, right ?
February 20, 2009 at 12:00 am
Judy (2/19/2009)
February 19, 2009 at 1:13 pm
russell.sage (2/19/2009)
February 19, 2009 at 1:11 pm
Check "Monitoring Mirroring Status " in Books online to start with.
It explains there is a whole set of tools to serve you.
February 19, 2009 at 1:23 am
GilaMonster (2/18/2009)
Thank you for the confirmaton.
I did set it to checksum on the upgraded databases.
(just like i run sp_updatestats every once in a while)
Shouldn't be necessary on SQL 2005 or...
February 19, 2009 at 12:27 am
Another save point has been set 😎
I know (and have activate on all our db) PAGE_VERIFY at db level.
Is my perception correct that this would detect any issue as...
February 18, 2009 at 12:54 am
We doublechecked all clustered things were hosted on the same node.
(quorum + instances)
- shut down all applications that use sqlserver (because you know the instance(s) will get offline at some...
February 18, 2009 at 12:38 am
We use this sequence:
1) restore the db to SQL2005
2) DBCC for DATA_PURITY
3) switch to dblevel 90 (if possible)
4) rebuild all indexes (individually)
5) dbcc updateusage with count_rows
6) sp_updatestats
7) synchronize users
8) create...
February 18, 2009 at 12:13 am
rhjohnson (2/17/2009)
February 18, 2009 at 12:07 am
Viewing 15 posts - 3,991 through 4,005 (of 7,503 total)