excuse my ignornace on switching recovery models

hello,
i just swtiched a database from Full to simple...
1) backed up the database,
2)ran truncate Log in SQl analyser
3) switched to simple
4) ran DBCC shrinkfile
i have a 20 mb database that had a transaction log that grew to 500MB -- i
do no need the logs because this database does not change often... i can
deal with losing one days worth of data.
my question is, Did I mess up anything by doing the steps above? I just want
to be able to restore the main database (no logs) in the event of a
disaster.
i am not sure if somehow i may have lost data...just checkingFollowing the steps you outlined, you should not have 'lost' any data.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"JM" <j_nospaM> wrote in message
news:OAnsiJKFHHA.2452@.TK2MSFTNGP06.phx.gbl...
> hello,
> i just swtiched a database from Full to simple...
> 1) backed up the database,
> 2)ran truncate Log in SQl analyser
> 3) switched to simple
> 4) ran DBCC shrinkfile
> i have a 20 mb database that had a transaction log that grew to 500MB -- i
> do no need the logs because this database does not change often... i can
> deal with losing one days worth of data.
> my question is, Did I mess up anything by doing the steps above? I just
> want to be able to restore the main database (no logs) in the event of a
> disaster.
> i am not sure if somehow i may have lost data...just checking
>
>|||great thanks
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%23gh2gMKFHHA.3540@.TK2MSFTNGP02.phx.gbl...
> Following the steps you outlined, you should not have 'lost' any data.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "JM" <j_nospaM> wrote in message
> news:OAnsiJKFHHA.2452@.TK2MSFTNGP06.phx.gbl...
>> hello,
>> i just swtiched a database from Full to simple...
>> 1) backed up the database,
>> 2)ran truncate Log in SQl analyser
>> 3) switched to simple
>> 4) ran DBCC shrinkfile
>> i have a 20 mb database that had a transaction log that grew to 500MB --
>> i do no need the logs because this database does not change often... i
>> can deal with losing one days worth of data.
>> my question is, Did I mess up anything by doing the steps above? I just
>> want to be able to restore the main database (no logs) in the event of a
>> disaster.
>> i am not sure if somehow i may have lost data...just checking
>>
>sql

EXCEPTION_ACCESS_VIOLATION

I have installed SQL 2000 sp3a and I am getting and access
violation on even the simplest queries performed from the
Query Analyser.
Example
Select * from tblcode
Returns
SqlDumpExceptionHandler: Process 54 generated fatal
exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
is terminating this process.
Any ideas will be greatly appreciated.| From: "Doug" <dougs@.inquiry-tracking.com>
| Sender: "Doug" <dougs@.inquiry-tracking.com>
| Subject: EXCEPTION_ACCESS_VIOLATION
| Date: Tue, 9 Dec 2003 10:36:06 -0800
|
| I have installed SQL 2000 sp3a and I am getting and access
| violation on even the simplest queries performed from the
| Query Analyser.
|
| Example
| Select * from tblcode
|
| Returns
|
| SqlDumpExceptionHandler: Process 54 generated fatal
| exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
| is terminating this process.
|
| Any ideas will be greatly appreciated.
--
Hi Doug,
You should raise a product support call on this.
Thanks,
--
Eric Cárdenas
SQL Server support
||||Same sh*t that happens to me, seems to be connected to sqlServer now
generatign faulty indexes, beats me as to how I'm to handle it.
Everytime the maintenanceplan has been run it fails and leaves a certain
table inoperable/inaccesible (due to sqlServer generation badly namded
_and_ duplicate named indexes that cannot be deleted) :(
Anyone else experiencing this problem?
Peace,
Johan
In article <1058e01c3be83$4ed4fbc0$a601280a@.phx.gbl>, dougs@.inquiry-
tracking.com says...
> I have installed SQL 2000 sp3a and I am getting and access
> violation on even the simplest queries performed from the
> Query Analyser.
> Example
> Select * from tblcode
> Returns
> SqlDumpExceptionHandler: Process 54 generated fatal
> exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
> is terminating this process.
> Any ideas will be greatly appreciated.
>|||Just found the answer - in article
http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com:80/support/kb/articles/Q293/1/77.ASP&N
oWebContent=1
But since this only recognizes the problem with 'hind%'-indexes you'll
have to adjust statement to include (for example) '== '. This problems
seems to have been a well known fact for sql7 and "known" for sql2000.
After scanning this newsgroup it seems that I'm not the only one
experiencing this problem, and it seems to have risen to "fame" with
sp3a...
2 words - "fuck" & "microsoft"...
Peace,
Johan
In article <MPG.1a47a16784ac9671989681@.news.internet5.net>, johan@.fap.se
says...
> Same sh*t that happens to me, seems to be connected to sqlServer now
> generatign faulty indexes, beats me as to how I'm to handle it.
> Everytime the maintenanceplan has been run it fails and leaves a certain
> table inoperable/inaccesible (due to sqlServer generation badly namded
> _and_ duplicate named indexes that cannot be deleted) :(
> Anyone else experiencing this problem?
> Peace,
> Johan
> In article <1058e01c3be83$4ed4fbc0$a601280a@.phx.gbl>, dougs@.inquiry-
> tracking.com says...
> > I have installed SQL 2000 sp3a and I am getting and access
> > violation on even the simplest queries performed from the
> > Query Analyser.
> >
> > Example
> > Select * from tblcode
> >
> > Returns
> >
> > SqlDumpExceptionHandler: Process 54 generated fatal
> > exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
> > is terminating this process.
> >
> > Any ideas will be greatly appreciated.
> >
>|||| 2 words - "fuck" & "microsoft"...
|
| Peace,
| Johan
--
Johan,
Have you actually RAISED A CALL with MICROSOFT?
--
Eric Cárdenas
SQL Server support