CREATE DATABASE Branch - LOG ON MAXSIZE = UNLIMITED,

This option is recommended? to use  MAXSIZE = UNLIMITED,  for creating LOG file?
enrique_aeoAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kent DyerIT Security Analyst SeniorCommented:
There is a limitation of this..

http://connect.microsoft.com/SQLServer/feedback/details/175549/database-file-maxsize

The max size for log files is 2TB = 2048GB. If you look at the original output for the maxsizes of the log files in you will see that both report the same size = 2TB

From BOL

UNLIMITED
Specifies that the file grows until the disk is full. In SQL Server 2005, a log file specified with unlimited growth has a maximum size of 2 TB.
Thanks.

HTH,

Kent
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
enrique_aeoAuthor Commented:
is a good practice?
0
Kent DyerIT Security Analyst SeniorCommented:
There are different schools of thought for sizing database and setting log growth.  It depends on what you want to do and what environmental resources you have available and are not limited to: drives, servers, SAN, NAS, etc.  For example, if you want to grow your database by 1MB at a time, it would do database re-sizing more frequently than say 10% of the overall database size.  The trade-off for the 10% growth is that there would be more time taken in the re-size process and the time to do this can increase over time.  The impact to the customer (end-user experience) is usually quite minimal.  The other thing to keep in mind, with an enterprise database, it is good practice to keep your logs on separate drive spindles (yes, even on a SAN) for optimum database performance.

HTH,

Kent
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.