Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

In the Database Properties (Tran

Status
Not open for further replies.

JayKusch

MIS
Oct 30, 2001
3,199
US
In the Database Properties (Transaction Log Tab)
You are able to set the Automatically grow file
to grow in megabytes.

Is there a T-SQL command to set this say to 1000MB?
Thanks

J. Kusch
 
Look at Alter database command in Books online at the FILEGROWTH parameter.
 
We deal in Las Vegas sytle slot machine games for Indian Casinos. Our game play is extremely high in some of the sites. The techs in the field are noticing that we are having the reels of the machines spinning continuously and not returning the outcome to the player in the normal 3 second fashion. They feel it is because the TLog is being extended several times during the couse of the day. Not good for our players. They want that "Instant" 3 second gratification. So one of their fixes is to set the TLog to 1GB, since we have plenty of room and see what happens.

Unfortunatley, I am not working with the techs, at this point in time, so I am just the information funnel. In fact, the question poised, "How to set the TLog to a GB" was posted by a tech who used by workstation to log the question to the forum instead of asking me directly. As SQLSister stated, it was just an easy alter DB command. Guess its time to lock down the station when I leave - lol.

Thanks again for all the info. Have a great day!
Thanks

J. Kusch
 
There is a difference between setting the TLog size to 1GB and setting growth to 1GB. I'm not questioning the need to set the log to a large size, only if it is prudent to set the growth factor that big. Growing a file isn't instantaneous. Growing a file by 1GB may take several seconds longer than growing it by 100 MB. Transactions will be stopped while the file grows.

In a transaction processing environment, it is best to set the transaction file large to start and then perform frequent transaction backups to maintain the size so the file doesn't need to grow at all. Log backups will have less impact on processing than log file growth. If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top