Showing posts with label limit. Show all posts
Showing posts with label limit. Show all posts

Friday, February 17, 2012

database log file size

I want to ask what are the impacts if I limit the file size to certain MBs and will it report (File is full) or overwrite old data when the file reachs the assigned size?

you have to configure an alert (several MB) before log gets full.

when the log gets full no change in the database shall be committed.

|||

but is it true that SQL Server will be faster if the allocated size for the log file was larger?

|||

Jassim,

Perhaps you are referring to an auto grow capability of data and log files. By default database files are created with auto grow option. Each time a file reaches it's full capacity it gets resized, by the specified amount (either fixed size or percentage). This operation has some negative impact on the database performance, so in general it should be avoided. The autogrow functionality is primarly useful in systems that are not closely monitored by an adminstrator, for example embedded applications.

So if you set the initial log size to be bigger, you avoid growing the log file on demand. You can monitor for the auto grow of log and data files using SQL Profiler by selecting Log File Auto Grow and Data File Auto Grow events.

Hope that helps.

Regards,

database log file size

I want to ask what are the impacts if I limit the file size to certain MBs and will it report (File is full) or overwrite old data when the file reachs the assigned size?

you have to configure an alert (several MB) before log gets full.

when the log gets full no change in the database shall be committed.

|||

but is it true that SQL Server will be faster if the allocated size for the log file was larger?

|||

Jassim,

Perhaps you are referring to an auto grow capability of data and log files. By default database files are created with auto grow option. Each time a file reaches it's full capacity it gets resized, by the specified amount (either fixed size or percentage). This operation has some negative impact on the database performance, so in general it should be avoided. The autogrow functionality is primarly useful in systems that are not closely monitored by an adminstrator, for example embedded applications.

So if you set the initial log size to be bigger, you avoid growing the log file on demand. You can monitor for the auto grow of log and data files using SQL Profiler by selecting Log File Auto Grow and Data File Auto Grow events.

Hope that helps.

Regards,

Tuesday, February 14, 2012

Database limit?

Is there a limit to the number of databases that a MSDE instance can support?
AlwaysLearning
Not in number only in size (2GB)
HTH, Jens Smeyer
https://www.sqlserver2005.de
"AlwaysLearning" <AlwaysLearning@.discussions.microsoft.com> schrieb im
Newsbeitrag news:585A5332-B8E9-48CF-A6A8-848603A00B4F@.microsoft.com...
> Is there a limit to the number of databases that a MSDE instance can
> support?
> --
> AlwaysLearning

Database Limit

I have heard the answer before, but I do not remember and I cannot find it
on Microsoft's website. Is the 2 GB limit per database or per server? Can
I have multiple databases reach 2 GB on one MSDE server, or is the maximum
for all databases on the server 2 GB?
Thank you,
Marc
Marc,
The limit is per database.
Regards
Lars Broberg
Elbe-Data AB
http://www.elbe-data.se
Remove "nothing." when replying to private e-mail!
Marc Meltzer wrote:
> I have heard the answer before, but I do not remember and I cannot find it
> on Microsoft's website. Is the 2 GB limit per database or per server? Can
> I have multiple databases reach 2 GB on one MSDE server, or is the maximum
> for all databases on the server 2 GB?
> Thank you,
> Marc
>
|||hi Marc,
Marc Meltzer wrote:
> I have heard the answer before, but I do not remember and I cannot
> find it on Microsoft's website. Is the 2 GB limit per database or
> per server? Can I have multiple databases reach 2 GB on one MSDE
> server, or is the maximum for all databases on the server 2 GB?
the limit is per database, and regarding the datafiles only...
you can have multiple databases reaching 2gb per data files on the same
instance..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||It's 2GB per database. The limit applies to the size of the data files, not
log files.
This is covered in one of the footnotes from
http://msdn.microsoft.com/library/?u...sp?frame=true:
3 The data portion of a database cannot exceed 2 GB in size when using the
SQL Server 2000 Desktop Engine (MSDE 2000) or the Microsoft Data Engine
(MSDE) 1.0. The total size of the database, including log files, can exceed
2 GB provided the sum of the sizes of the data files remains 2 GB or lower.
Alan Brewer [MSFT]
Content Architect, SQL Server Documentation Team
SQL Server Developer Center: http://msdn.microsoft.com/sql
SQL Server TechCenter: http://technet.microsoft.com/sql/
This posting is provided "AS IS" with no warranties, and confers no rights.