Thanks,
Greg
At 09:31 AM 2/3/99 -0500, Greg Humphreys wrote:
>I am writing in regards to a Database problem that we had recently.
>
>The following attched files are from our efforts to correct a corruptted
>table in our Emerald database.
>
>We are trying to "fix" the remaining troubled tables...to the best of our
>knowlegde, we are not using these tables.
>
>If anyone could be of asistance, we are trying to determine if the table
>Radtriggers is actually being used...and if so, how can we correct the
>problem of its corruption?
>
>Thanks for any assistance.
>
>________________________________________
>
>Greg Humphreys ghumphreys@naxs.com
>NetAccess, Inc. http://www.naxs.com
>Network/Systems Engineer 800-644-7220
>
>----------
>> From: Greg Humphreys <ghumphreys@naxs.com>
>> To: mdavis@naxs.net; greghump@naxs.com; Chris Nickels <chrisn@naxs.com>
>> Cc: shawna@microsoft.com; markweb@microsoft.com
>> Subject: Re: Microsoft SQL Server case number SRX990203602471 ()
>> Date: Wednesday, February 03, 1999 8:55 AM
>>
>> Mark/ Shawna,
>>
>> I am enclosing the Check Database queries and subsequent report files
>that
>> we ran against our Emerald Database.
>>
>> There are some errors, these are in reference to tables that are not
>being
>> used.
>>
>> Please look over the queries and reports and let me know if there is
>> anything we can do to try and correct these errors.
>>
>> Our authentication database is currently back up and running.
>>
>> Thanks for your help.
>>
>>
>> ________________________________________
>>
>> Greg Humphreys ghumphreys@naxs.com
>> NetAccess, Inc. http://www.naxs.com
>> Network/Systems Engineer 800-644-7220
>>
>> ----------
>> > From: Chris Nickels <chrisn@naxs.com>
>> > To: greghump@naxs.com; mdavis@naxs.net; ghumphreys@naxs.com
>> > Subject: Fw: Microsoft SQL Server case number SRX990203602471 ()
>> > Date: Thursday, February 04, 1999 6:04 AM
>> >
>> > Here is the step by step instructions from microsoft.
>> >
>> > Chris.
>> >
>> > -----Original Message-----
>> > From: Mark Weber <markweb@microsoft.com>
>> > To: chrisn@naxs.com <chrisn@naxs.com>
>> > Date: Wednesday, February 03, 1999 10:02 PM
>> > Subject: Microsoft SQL Server case number SRX990203602471 ()
>> >
>> >
>> > >Chris,
>> > >
>> > >1) set database status to emergency bypass mode
>> > >sp_configure 'allow updates', 1
>> > >go
>> > >reconfigure with override
>> > >go
>> > >update sysdatabases set status=-32768 where name='EMERALD'
>> > >go
>> > >
>> > >
>> > >2) stop SQL Server and backup the database device files
>> > >
>> > >3) start SQL Server
>> > >
>> > >4) LOAD DATABASE EMERALD {from backup}
>> > > either via Networker or via the command in ISQL
>> > > LOAD DATABASE EMERALD FROM DISK='XXXXX' - where XXXXX is the fully
>> > >qualified drive-dir-file to the dumped file e.g. 'C:\mssql\mydump.dmp'
>> > > {the location needs to be nested inside of quotes}
>> > >
>> > >5) reset the status back to normal mode (e.g. not in Emergency Bypass)
>> > >update sysdatabases set status=0 where name='EMERALD'
>> > >go
>> > >
>> > >6) stop and restart SQL Server and assess functionality
>> > >
>> > >
>> > >Let me know how it goes,
>> > > Mark Weber
>> > > SQL Server Support
>> > > phone: (425) 704-5004
>> > > EM: markweb@microsoft.com
>> > > fax: (425) 704-4213
>> > >
>> > > I want you to be "very satisfied" with the service I provide.
>> > > Comments about my performance are encouraged and can be directly
>> > > sent to my manager Shawn Aebi at shawna@microsoft.com
>> > >
>> > >
>> > >
>
For more information about this list, including removal,
please see http://www.iea-software.com/maillist.html