Viewing 15 posts - 12,556 through 12,570 (of 49,557 total)
Yes. Set the CPU affinity.
June 27, 2013 at 4:33 am
psingla (6/27/2013)
if i were you then i would have taken the backup first thentried
DBCC CHECKDB (<db>, REPAIR_ALLOW_DATA_LOSS)
Note:note sure this will work on 2000 or not?
Got nothing to do...
June 27, 2013 at 4:19 am
Don't even try to upgrade that, the upgrade will very likely fail due to the severe corruption and you may well end up with a completely unusable database and complete...
June 27, 2013 at 4:07 am
I didn't say change the file names in SQL. I said change the names of the files to match what you told SQL they would be.
Open explorer, browse to where...
June 27, 2013 at 3:43 am
suneet.mlvy (6/27/2013)
but for log you can detach database then rename log file and again attach database then new log is created.
You can't detach system databases and rebuilding the log as...
June 27, 2013 at 3:16 am
Rename the files to match the names you gave SQL. No detach or offline or anything like that is necessary since SQL's not running, just change the file names. Hope...
June 27, 2013 at 3:08 am
Timestamp, despite it's name, has nothing at all to do with times. It's a binary value, automatically incremented whenever the record is updated. It's a row version indicator, not a...
June 27, 2013 at 2:36 am
Apologies if any arrogance is showing through this morning.
June 27, 2013 at 2:16 am
psingla (6/26/2013)
BTW sysobjects view exists in 2005+ versions also.
The view does, but it's a view and not a table and since a view does not store data, sysobjects cannot become...
June 27, 2013 at 2:12 am
psingla (6/26/2013)
but how you came to know this is SQL 2000?I haven't worked on 2000...
Because it's posted in the SQL 2000 forum, because the error messages are in the SQL...
June 26, 2013 at 12:45 pm
First things first, with multiple instances, you do not want max server memory at default, it's going to cause problems.
Figure out what memory to leave for the OS (I'm sure...
June 26, 2013 at 12:40 pm
psingla (6/26/2013)
If it is a very big database then you can restore only page (1:1610) to save restoration time
No, he can't.
Firstly because it's a SQL 2000 database and page restore...
June 26, 2013 at 8:28 am
If you are absolutely certain you don't need point in time recovery, that restoring to the last full/diff backup is fine, simple recovery.
June 26, 2013 at 3:13 am
Hex editor works.
Pick a page you want to corrupt, identify an allocated page using DBCC IND for a table and cacluate the offset as (page Number)*8192 bytes
Take the DB offline,...
June 26, 2013 at 3:03 am
Restore from a clean backup, your database is irreparably corrupt.
Once done, check your IO subsystem for errors.
June 26, 2013 at 2:58 am
Viewing 15 posts - 12,556 through 12,570 (of 49,557 total)