| Author |
Topic |
|
SQLCode
Posting Yak Master
143 Posts |
 Posted - 2004-05-03 : 10:58:04
|
| We have one database that shows that it is still starting in the SQL Server Logs. this is non ending. Why does it take for ever to start up that DB? I checked the properties of this DB and it says 0 MB available. It is just over a gig in size and is set to auto grow and server also has a lot of space on it. Why would it say 0 mb available?Any ideas? TIA |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-05-03 : 11:26:59
|
| SOunds like the database is corrupt.Could also be that it doesn't realise it needs to grow - I had that a few times with v7, the database just stayed there until it was manually increased in size. Hasn't happened for a while so I suspect that's not the problem.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
SQLCode
Posting Yak Master
143 Posts |
Posted - 2004-05-03 : 11:31:26
|
| Thanks Nigel, I will try that and see how that goes. |
|
|
|
SQLCode
Posting Yak Master
143 Posts |
Posted - 2004-05-03 : 12:23:36
|
| After checking more details I found out that it is this way on the online prod server also. No one has complained anything so far. If I leave it like that and if the DB is more of read than write, would it be as serious as crashing the server ?My question is what happens if I leave it like this ?TIA |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-03 : 12:52:41
|
| It took a couple of hours to startup one database about a year ago. The database crashed in the middle of very long job. Of course, it had to rollback and rollforward changes in order to bring it up. That's probably what it is doing for you as well. You can check the Application Log to find out how far along it is. It should give a percentage.Tara |
|
|
|
SQLCode
Posting Yak Master
143 Posts |
Posted - 2004-05-04 : 10:53:09
|
| The database is not a suspect and I also increased the sizes of both data file and log files( to almost double).It still says 0. MB available and in SQL server logs, it is still starting up this DB. It has been a few days and eventhough it did not crash our servers, I'd like to know what else to do to fix the problem ASAP.Please help with any suggestions.TIA. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-04 : 12:44:57
|
| What does the Application Log in Event Viewer show for this database?Tara |
|
|
|
SQLCode
Posting Yak Master
143 Posts |
Posted - 2004-05-04 : 13:04:52
|
| unfortunately I am still not able to see the app log. I do not have admin access to the box. I am trying hard to get to log at least. I thought I should prep other things meanwhile.Thanks a bunch for reading and for all your help. I will post it when I get any more info. |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-05-04 : 21:22:37
|
| In your maintenance window, would it be able to stop and start SQL Server? Have you ran a query in Query Analyzer to see if you can query this database? You mentioned that users weren't complaining. I can't imagine this is the case if it's really starting. My users would be hunting.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
SQLCode
Posting Yak Master
143 Posts |
Posted - 2004-05-05 : 09:12:27
|
| That is the part that I do not understand Derrick. SQL service has been stopped and started couple times. Every other database starts up within a sec or so. Just this one says starting database for ever. And to answer your question, I can query from it from analyzer, SQLEM. I did not insert or update anything on it (I am not allowed to, business perspective). Also, it does not have many users and may not be highly used DB.Like Tara said, I eventually got to the application log. At least I could not find anything that said that there was a problem with this database. Some routine errors and warnings.I do not know what else to look at.I increased the size of the data and log files. It still shows 0 MB available on the properties of this DB. Strange thing is the log file shows 1 MB no matter how much I increase it to.(?)It is restored from an online DB which is on different server. That source DB, which I do not have much access to is also the same way. 0 MB available.Of course I did not increase size or do anything with the online server. Could not even check any app logs on the online server. My guess is the problem is on that online server and just got propagated when it was restored with the dts scheduled job.Any more suggestions, help is appreciated.Thanks for all the help and advice. |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-05-05 : 14:44:55
|
| This sounds crazy, but I would try restoring the database somewhere with a single file restore only.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
SQLCode
Posting Yak Master
143 Posts |
Posted - 2004-05-14 : 14:12:06
|
| Thanks for all the good suggestions. We had some of the ids changed with just one letter prefix to the old ids. Which we were not aware of till recently. Hence the jobs were hanging. It did not give any errors for me to look at. It just gave warnings of Id not existing.Like Tara said earlier, it was jobs that was hanging-up/not completing and probably why the DBs showed 0.0 MB available.(refer to post http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=35117). I appreciate all your help. Both issues are resolved. |
|
|
|
|
SQL Log - Starting DB ??