|
Try this, I've
used it in the past when I hit the 2GB max.�
Provided to me from ISS Tech. osql -E -d realsecuredb -i .\iss_truncatetables.sql iss_truncatetables.sql ------------------start-------------------------- Use RealSecureDB � truncate table observances � truncate table sensordataavp � truncate table sensordataresponse � truncate table sensordataupdates � truncate table sdavprejected � truncate table sdresponserejected � truncate table sdupdatesrejected � truncate table sensordatarejected � --alter table sensordataavp
drop constraint� SDAVP_PK � --alter table sensordataresponse
drop constraint� SDResponse_PK � --alter table sensordataupdates
drop constraint� SDUpdates_PK � � alter table sensordataavp drop constraint� SenData_SDAVP_FK alter table sensordataresponse drop
constraint� SenData_SDResp_FK alter table sensordataupdates drop
constraint� SenData_SDUpd_FK truncate table sensordata � ALTER TABLE SensorDataAVP �������
ADD CONSTRAINT SenData_SDAVP_FK �������������� FOREIGN KEY (SensorDataID) ����������������������������� REFERENCES SensorData � � � �ALTER TABLE SensorDataResponse �������
ADD CONSTRAINT SenData_SDResp_FK �������������� FOREIGN KEY (SensorDataID) ����������������������������� REFERENCES SensorData � � � �ALTER TABLE SensorDataUpdates �������
ADD CONSTRAINT SenData_SDUpd_FK �������������� FOREIGN KEY (SensorDataID) ����������������������������� REFERENCES SensorData Go ------------end--------------- -----Original Message----- Here
is a procedure that might help you. If you have filled up your MSDE database,
you may find that nothing works, so there is a chance that you will have to
re-install the product to recover. Having
said that, here are some OSQL commands that might get you out of your bind. For
the future, make sure that you right click on the database in the SiteProtector
sensor tab and turn on the automatic database maintenance options that were
added in Service Pack 3. This will help ensure that you don't get into this
position again... First,
shut down all the SiteProtector services. Then, the next step is to
attempt to give yourself a little more space to work with
C:\osql -E -Q "ALTER DATABASE RealSecureDB MODIFY FILE
(NAME='SiteProtector site database primary data file', SIZE=2048MB)" Then
you want to find the earliest date that your data is so that you can start
purging the data one day at a time to free up more space. C:\osql -E -d RealSecureDB -Q
"SELECT MIN(ObservanceTime) FROM Observances (NOLOCK)" Once
you have the earliest date, try purging one day at a time to free up some
memory.
C:\osql -E -d RealSecureDB -Q "exec iss_PurgeSD '2003-10-14'" C:\osql
-E -d RealSecureDB -Q "exec iss_PurgeObs '2003-10-14'" To
find out how much space you have free in the database, use the following
command: C:\>osql -E -d RealSecureDB -Q
"exec sp_spaceused" If you
can't purge because you still don't have enough space, you can also try
truncating the following tables to get at least enough space to try to purge
one day at a time: C:\>osql -E -d RealSecureDB -Q
"truncate table SensorDataUpdates" And if
you don't mind losing all the details behind all of your event data, you can
try the following, but this should be used as a last resort if the above
doesn't work: C:\>osql -E -d RealSecureDB -Q
"truncate table SensorDataAVP" Once
you have approximately 100MB free, you should be able to start SiteProtector up
and run the automatic database maintenance mentioned above. Those automated
procedures should get your system back to a healthy state. As I stated at the
biginning, this may not work, MSDE generally does not recover well when it gets
full, so there may be nothing left to try except a re-install. I hope this
helps. Matthew =======================================================
|
Title: Message
- [ISSForum] MSDE Fabio A. Bicudo Duarte
- [ISSForum] MSDE Gu1tarb0y
- RE: [ISSForum] MSDE Ward, Matthew (ISSAtlanta)
- O'Flynn, Derek
