August 19, 2010 at 3:29 am
Hi All,
Low disk space issue, One of our collegue to shrink the database. every one week the same issue happend ? i suggested to add one more disk. but db is going to migrate from sql to oracle.
So they didn't allowed to add one more disk.
1. db file and log file were different location. Is it right or wrong?
if its wrong means what will happen?
2. how can i view the database properties thru query in sql 2000
3. How can i fix the above issue? if any body help me, i would be greatly appreciated
Thanks & Regards
Balaji.G
August 19, 2010 at 3:39 am
1. That's fine.
2. sp_helpdb
3. Don't shrink your database. If you need more space, add it. Are you performing regular maintentance on your indexes?
John
August 19, 2010 at 3:51 am
Thanks..
I have one more question like if i shrink a database. afterwards
what are the other steps to be followed?
Regards
Balaji.G
August 19, 2010 at 3:54 am
I won't go into why you shouldn't shrink your database - you can search this site and you'll find plenty of references. If you must do it, do it at the time of the smallest load on the database. Rebuild your indexes afterwards.
John
August 19, 2010 at 4:02 am
Thanks
Regards
Balaji.G
August 19, 2010 at 4:08 am
instead of shrinking your database regularly, you must redefine your full and log backup schedule.
You will definately see the difference.
if it still growing, then you need to find which query/transaction is filling the long.
----------
Ashish
August 19, 2010 at 4:15 am
ashish.kuriyal (8/19/2010)
instead of shrinking your database regularly, you must redefine your full and log backup schedule.You will definately see the difference.
if it still growing, then you need to find which query/transaction is filling the long.
Ashish
Since Balaji said he was shrinking his database, I took that as meaning it was the database file he is shrinking. If that is the case, backing up the database or log, while certainly a good practice, will not make any difference to this scenario. If it's the log file that he's shrinking then you're right - either the transaction log should be backed up regularly or the database should be set to Simple recovery mode in order to avoid unconfined log file growth.
John
August 19, 2010 at 5:01 am
Hi Balaji,
What is the Db size by the way? And by when are you planing to migrate to Oracle? More appropriate solution depends on these questions. Also I am growing curious about hardware of DB server.
- SAMJI
If you marry one they will fight with you, If you marry 2 they will fight for you 🙂
August 20, 2010 at 5:46 am
My database size is : 14GB
August 20, 2010 at 6:40 am
Hello John Mitchell-245523 & COOL_ICE,
If I am not wrong Balaji starting his carrer with SQL Server(It is very good).
0.I belive 14 GB Database is not that big Database size
1.take a fulbackup of the Database.
2.Shrink the Log file(If required).
Is it ok...he follows...this steps
August 20, 2010 at 6:44 am
i will suggest insetead of shrinking the log, change the DB to simple recovery.
----------
Ashish
August 20, 2010 at 6:47 am
1. Full database backups should indeed be done regularly, although they won't make any difference to this situation.
2. Whether to shrink the log depends on whether it is expected to grow to the same size again. If the database is in full recovery mode, and no log backups were being taken, then the log file is likely to have grown very large. In that case, once log backups have been set up, it will probably be appropriate to shrink the log file.
John
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply