Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
pelegk2
Aged Yak Warrior
723 Posts |
Posted - 2007-01-28 : 02:41:45
|
1)when does actually the log file of sql server grows?(remark : under propperties->options->Recovery the state is "full").2)when i have space available==0 in the DB but i still have space on the HD from where the 0 space comes?thnaks in advancepelegIsrael -the best place to live in aftr heaven 9but no one wan't to go there so fast -:) |
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2007-01-28 : 06:41:03
|
1)Whenever you manipulate the data in the table with either UPDATE or DELETE (TRUNCATE) statement.Or when you do a ALTER TABLE statement.2)Learn about file content in Books Online.SQL Server allocates filespace for the database. The data information do or do not occupy the entire allocated space on the file on disk. If it does, the "space remaining" is 0, when the file is fully used. Now it is time for SQL Server to check the settings for the database for how (if at all) to increase the file space for the database.Peter LarssonHelsingborg, Sweden |
 |
|
pelegk2
Aged Yak Warrior
723 Posts |
Posted - 2007-01-28 : 06:56:10
|
1)i assume insert syntax also included?2)so what is actually my sqlserver state?that it has alloctaed all space on disk and cant do further?currntly the setting is set to growing in 100mb each time -is it ok or better to define % ?thjnaks in advancepelegIsrael -the best place to live in aftr heaven 9but no one wan't to go there so fast -:) |
 |
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2007-01-28 : 09:42:07
|
1)Yes, INSERTs also affect the size of the database and/or log file. Peter LarssonHelsingborg, Sweden |
 |
|
pelegk2
Aged Yak Warrior
723 Posts |
Posted - 2007-01-29 : 09:59:17
|
what abot Q2?Israel -the best place to live in aftr heaven 9but no one wan't to go there so fast -:) |
 |
|
Kristen
Test
22859 Posts |
Posted - 2007-01-29 : 10:06:28
|
"it has alloctaed all space on disk and cant do further?"The database will be offline or somesuch status when it NEXT attempts to extend the database and finds there is not enough disk space."currntly the setting is set to growing in 100mb each time -is it ok or better to define %"IMHO "MB" is better. Extending the database is a very resource intensive task (SQL 2000 any way) and doing it by 500MB or 1GB+ at a time is likely to cause timeouts etc. on a busy database.Better still is to pro-actively extend the database in quiet time in anticipation of it becoming full (or size it "right" from the outset if possible)Kristen |
 |
|
harsh_athalye
Master Smack Fu Yak Hacker
5581 Posts |
Posted - 2007-01-29 : 10:08:56
|
General consideration while setting Autogrow option is to minimize the allocation overhead (reduce disk IO) while not reserving disk space unnecessarily - may it be absolute value or in terms of percentage.Harsh AthalyeIndia."The IMPOSSIBLE is often UNTRIED" |
 |
|
Kristen
Test
22859 Posts |
Posted - 2007-01-29 : 10:17:36
|
Point of pedantry:We optimise the physical disk file (i.e. at the O/S level) periodically. I thought this would get rid of any fragmentation.however, I saw something the other day about a table of linked-file-bits-and-pieces. Is defragmenting enough, or is there something in the System tables that is getting hit harder if there are numerous database extensions?Kristen |
 |
|
|
|
|