MSDE 2005 - Hard disk full, affects my database

Question

MSDE 2005 - Hard disk full, affects my database

Janaki-382435

Valued Member

Points: 64
More actions
November 14, 2006 at 6:20 am

#367995

Hi,
i had installed embedded MSDE which is of sql 2005 version. i had an application pointing to this server's DB. Everything was goin fine for a while. Suddenly my hard disk (where both my application and MSDE was running) ran out of disk space and stopped my application. later i cleaned my hard disk, then it had few GB free space. When i tried to start my application it failed with the old DB. so i point to new DB of same MSDE, then my app start and worked fine. But i wanted to use my old DB, so i tried pointing to that old DB adn start my app... it failed again with the following error.
------------------------------
Starting up database 'myDB'.
Starting up database 'myDB'.
Starting up database 'myDB'.
Starting up database 'myDB'.
.....
Starting up database 'myDB'.
Starting up database 'myDB'.
Recovery is writing a checkpoint in database 'myDB' (5). This is an informational message only. No user action is required.
Using 'xpstar90.dll' version '2005.90.2047' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
------------------------------
Not sure what to do now... i even made AutoCLose parameter false and tried... no luck...
Have u guys faced this problem before... i have no clue how to make it work.
pls do help me reg the same
Thanks in advance,
JL
November 17, 2006 at 8:00 am

This was removed by the editor as SPAM

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Venu Dukka Old Hand Points: 351 More actions · Answer 1

Hi,

I am just throwing some ideas and not sure they will work. Follow these steps only if your database is not marked suspect.

Idea # 1: If the oldDB is in full recovery model, do this:

1. Restart SQL Server instance

2. Detach oldDB

3. Reattach oldDB

Run you application

Idea # 2: If you can take a backup of oldDB do so and restore it. Run your app

Idea # 3: If #1 and #2 don't work and you can access oldDB, try importing all the data from oldDB to newDB.

Let me know if this helped.

Venu

Janaki-382435 Valued Member Points: 64 More actions · Answer 2

Hey,

Thanks so much for ur reply. Let me try out this and let u know. I have discarded my old setup... will have to do it from scratch now. Any way thanks for ur post.

JL