Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005 ?From BOL
Maximum Capacity Specifications
Both SQL Server 2000 and 2005
Database Size 1,048,516 Terabytes
SQL Server 2000 MSDE
Database Size 2 GB
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005 ?
>
>|||This is a multi-part message in MIME format.
--010405010900060701050102
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
In addition to that, SQL Server 2005 Express Edition (which is the 2005
successor to MSDE) has a maximum DB size of 4GB (from
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx).
--
*mike hodgson*
http://sqlnerd.blogspot.com
Ben Nevarez wrote:
>From BOL
>Maximum Capacity Specifications
>Both SQL Server 2000 and 2005
>Database Size 1,048,516 Terabytes
>SQL Server 2000 MSDE
>Database Size 2 GB
>Ben Nevarez, MCDBA, OCP
>Database Administrator
>
>"Alan" wrote:
>
>>Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005 ?
>>
>>
--010405010900060701050102
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>In addition to that, SQL Server 2005 Express Edition (which is the
2005 successor to MSDE) has a maximum DB size of 4GB (from
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx</a>).</tt><br>">http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx">http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx</a>).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Ben Nevarez wrote:
<blockquote cite="mid1CE03E35-ACF5-4320-B704-7B0528159B35@.microsoft.com"
type="cite">
<pre wrap="">From BOL
Maximum Capacity Specifications
Both SQL Server 2000 and 2005
Database Size 1,048,516 Terabytes
SQL Server 2000 MSDE
Database Size 2 GB
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005 ?
</pre>
</blockquote>
</blockquote>
</body>
</html>
--010405010900060701050102--|||Using SQL 2000 MSDE, I was able to restore a 30GB DB.
"Alan" wrote:
> Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005 ?
>
>|||See the below URLS:
SQL 2005
http://www.yukonxml.com/Reference/default.aspx?t=Capacity
For SQL 2000 and older version see:-
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
Thanks
Hari
SQL Server MVP
"SQL ADMIRER" <SQL ADMIRER@.discussions.microsoft.com> wrote in message
news:92DE7187-E52A-4DD2-BEC0-E1CA39F4EF05@.microsoft.com...
> Using SQL 2000 MSDE, I was able to restore a 30GB DB.
> "Alan" wrote:
>> Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005
>> ?
>>
Showing posts with label size. Show all posts
Showing posts with label size. Show all posts
Wednesday, March 21, 2012
Database max size in 2000 and 2005
Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005 ?From BOL
Maximum Capacity Specifications
Both SQL Server 2000 and 2005
Database Size 1,048,516 Terabytes
SQL Server 2000 MSDE
Database Size 2 GB
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005
?
>
>|||In addition to that, SQL Server 2005 Express Edition (which is the 2005
successor to MSDE) has a maximum DB size of 4GB (from
http://www.microsoft.com/sql/prodin...e-features.mspx).
*mike hodgson*
http://sqlnerd.blogspot.com
Ben Nevarez wrote:
[vbcol=seagreen]
>From BOL
>Maximum Capacity Specifications
>Both SQL Server 2000 and 2005
>Database Size 1,048,516 Terabytes
>SQL Server 2000 MSDE
>Database Size 2 GB
>Ben Nevarez, MCDBA, OCP
>Database Administrator
>
>"Alan" wrote:
>
>|||Using SQL 2000 MSDE, I was able to restore a 30GB DB.
"Alan" wrote:
> Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005
?
>
>|||See the below URLS:
SQL 2005
http://www.yukonxml.com/Reference/d...aspx?t=Capacity
For SQL 2000 and older version see:-
http://msdn.microsoft.com/library/d...br />
8dbn.asp
Thanks
Hari
SQL Server MVP
"SQL ADMIRER" <SQL ADMIRER@.discussions.microsoft.com> wrote in message
news:92DE7187-E52A-4DD2-BEC0-E1CA39F4EF05@.microsoft.com...[vbcol=seagreen]
> Using SQL 2000 MSDE, I was able to restore a 30GB DB.
> "Alan" wrote:
>
Maximum Capacity Specifications
Both SQL Server 2000 and 2005
Database Size 1,048,516 Terabytes
SQL Server 2000 MSDE
Database Size 2 GB
Ben Nevarez, MCDBA, OCP
Database Administrator
"Alan" wrote:
> Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005
?
>
>|||In addition to that, SQL Server 2005 Express Edition (which is the 2005
successor to MSDE) has a maximum DB size of 4GB (from
http://www.microsoft.com/sql/prodin...e-features.mspx).
*mike hodgson*
http://sqlnerd.blogspot.com
Ben Nevarez wrote:
[vbcol=seagreen]
>From BOL
>Maximum Capacity Specifications
>Both SQL Server 2000 and 2005
>Database Size 1,048,516 Terabytes
>SQL Server 2000 MSDE
>Database Size 2 GB
>Ben Nevarez, MCDBA, OCP
>Database Administrator
>
>"Alan" wrote:
>
>|||Using SQL 2000 MSDE, I was able to restore a 30GB DB.
"Alan" wrote:
> Anyone knows what is the max database size in MSDE, SQL 2000 and SQL 2005
?
>
>|||See the below URLS:
SQL 2005
http://www.yukonxml.com/Reference/d...aspx?t=Capacity
For SQL 2000 and older version see:-
http://msdn.microsoft.com/library/d...br />
8dbn.asp
Thanks
Hari
SQL Server MVP
"SQL ADMIRER" <SQL ADMIRER@.discussions.microsoft.com> wrote in message
news:92DE7187-E52A-4DD2-BEC0-E1CA39F4EF05@.microsoft.com...[vbcol=seagreen]
> Using SQL 2000 MSDE, I was able to restore a 30GB DB.
> "Alan" wrote:
>
Wednesday, March 7, 2012
Database Maintenance Plan
Overview of my database: size - 45 GB, Full Recovery Mode, Log shipping ever 15 minutes; Full Backup nightly; Optimization and integrity checks on Sunday night.
The Database takes a transactional log every 15 minutes and ships it to our failover database. Usually these are small logs and are executed in matter of seconds.
On sunday night there is a problem. The optimization job (part of DB maintenance plan) runs for 3 hours and during this time the transactional log backup continues to runs and takes close to 4 hours of complete. When the tran log completes its close to a 30 GB file and this is causing problems with space and shipping. This also causes the failover server to be out of sync and at times we have to re setup log shipping.
Does anyone know if there is a way to get around this problem. Appreciate all help and comments.Its common to bulge Tlog when db maintenance plan perform DB optimization process and its better to pause Log shipping during this operation and take full backup once Maint.plan finishes the task and apply to standby server, then re-enable LS process.|||Thanks.
Is there a way to automate the pause of the TLog backup? I hate to be up at 3 in the morning to disable/enable the jobs manually.
The Database takes a transactional log every 15 minutes and ships it to our failover database. Usually these are small logs and are executed in matter of seconds.
On sunday night there is a problem. The optimization job (part of DB maintenance plan) runs for 3 hours and during this time the transactional log backup continues to runs and takes close to 4 hours of complete. When the tran log completes its close to a 30 GB file and this is causing problems with space and shipping. This also causes the failover server to be out of sync and at times we have to re setup log shipping.
Does anyone know if there is a way to get around this problem. Appreciate all help and comments.Its common to bulge Tlog when db maintenance plan perform DB optimization process and its better to pause Log shipping during this operation and take full backup once Maint.plan finishes the task and apply to standby server, then re-enable LS process.|||Thanks.
Is there a way to automate the pause of the TLog backup? I hate to be up at 3 in the morning to disable/enable the jobs manually.
Sunday, February 19, 2012
database logs
I am trying to reduce the physical size of a large database log. I have run several utilities - back up with the remove inactive entries from the transaction log checked, the DBCC shrinkfile utility (with a target size and a truncateonly option) and run DB maintenance to remove extra space. The properties of this log file show that it has reduced the size of the file, but the physical size of the file on the server still remains as big as it was.
Any suggestions on how to eliminate all the new free space I have created? I am looking to get the extra space on my server
Thanks.First check for any open transactions using dbcc opentran. Then follow the
steps in
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q272318
For reasons why the log can fill up or grow unexpectadly check out
INF: Causes of SQL Transaction Log Filling Up
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q110139
INF: Transaction Log Grows Unexpectedly or Becomes Full on SQL Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;317375
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Karen" <anonymous@.discussions.microsoft.com> wrote in message
news:34FB692C-3644-45A6-823F-628A5F4C3F18@.microsoft.com...
> I am trying to reduce the physical size of a large database log. I have
run several utilities - back up with the remove inactive entries from the
transaction log checked, the DBCC shrinkfile utility (with a target size and
a truncateonly option) and run DB maintenance to remove extra space. The
properties of this log file show that it has reduced the size of the file,
but the physical size of the file on the server still remains as big as it
was.
> Any suggestions on how to eliminate all the new free space I have created?
I am looking to get the extra space on my server.
> Thanks.
Any suggestions on how to eliminate all the new free space I have created? I am looking to get the extra space on my server
Thanks.First check for any open transactions using dbcc opentran. Then follow the
steps in
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q272318
For reasons why the log can fill up or grow unexpectadly check out
INF: Causes of SQL Transaction Log Filling Up
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q110139
INF: Transaction Log Grows Unexpectedly or Becomes Full on SQL Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;317375
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Karen" <anonymous@.discussions.microsoft.com> wrote in message
news:34FB692C-3644-45A6-823F-628A5F4C3F18@.microsoft.com...
> I am trying to reduce the physical size of a large database log. I have
run several utilities - back up with the remove inactive entries from the
transaction log checked, the DBCC shrinkfile utility (with a target size and
a truncateonly option) and run DB maintenance to remove extra space. The
properties of this log file show that it has reduced the size of the file,
but the physical size of the file on the server still remains as big as it
was.
> Any suggestions on how to eliminate all the new free space I have created?
I am looking to get the extra space on my server.
> Thanks.
database logs
I am trying to reduce the physical size of a large database log. I have run
several utilities - back up with the remove inactive entries from the trans
action log checked, the DBCC shrinkfile utility (with a target size and a tr
uncateonly option) and run
DB maintenance to remove extra space. The properties of this log file show
that it has reduced the size of the file, but the physical size of the file
on the server still remains as big as it was.
Any suggestions on how to eliminate all the new free space I have created?
I am looking to get the extra space on my server.
Thanks.First check for any open transactions using dbcc opentran. Then follow the
steps in
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/defaul...b;en-us;Q272318
For reasons why the log can fill up or grow unexpectadly check out
INF: Causes of SQL Transaction Log Filling Up
http://support.microsoft.com/defaul...b;en-us;Q110139
INF: Transaction Log Grows Unexpectedly or Becomes Full on SQL Server
http://support.microsoft.com/defaul...kb;EN-US;317375
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Karen" <anonymous@.discussions.microsoft.com> wrote in message
news:34FB692C-3644-45A6-823F-628A5F4C3F18@.microsoft.com...
run several utilities - back up with the remove inactive entries from the
transaction log checked, the DBCC shrinkfile utility (with a target size and
a truncateonly option) and run DB maintenance to remove extra space. The
properties of this log file show that it has reduced the size of the file,
but the physical size of the file on the server still remains as big as it
was.
I am looking to get the extra space on my server.
several utilities - back up with the remove inactive entries from the trans
action log checked, the DBCC shrinkfile utility (with a target size and a tr
uncateonly option) and run
DB maintenance to remove extra space. The properties of this log file show
that it has reduced the size of the file, but the physical size of the file
on the server still remains as big as it was.
Any suggestions on how to eliminate all the new free space I have created?
I am looking to get the extra space on my server.
Thanks.First check for any open transactions using dbcc opentran. Then follow the
steps in
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/defaul...b;en-us;Q272318
For reasons why the log can fill up or grow unexpectadly check out
INF: Causes of SQL Transaction Log Filling Up
http://support.microsoft.com/defaul...b;en-us;Q110139
INF: Transaction Log Grows Unexpectedly or Becomes Full on SQL Server
http://support.microsoft.com/defaul...kb;EN-US;317375
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Karen" <anonymous@.discussions.microsoft.com> wrote in message
news:34FB692C-3644-45A6-823F-628A5F4C3F18@.microsoft.com...
quote:
> I am trying to reduce the physical size of a large database log. I have
run several utilities - back up with the remove inactive entries from the
transaction log checked, the DBCC shrinkfile utility (with a target size and
a truncateonly option) and run DB maintenance to remove extra space. The
properties of this log file show that it has reduced the size of the file,
but the physical size of the file on the server still remains as big as it
was.
quote:
> Any suggestions on how to eliminate all the new free space I have created?
I am looking to get the extra space on my server.
quote:
> Thanks.
Friday, February 17, 2012
Database log size
hi
my database on remote server i cannot access directly.
i can access it only with query analyzer.
my log file size is 9mb but nothing in database. only few tables there so how i can reduce log file size with query.
thanks
Hi,
I used to do this using the sa privileges.
Google it for (Truncating SQL Log)
Let me know if you need further help.
Regards
||| Change the recovery model to simple. Set autoshrink to true, back up the database and it should reduce in size.
I don't want you to waste your time, here is the query,
BACKUP LOG databasename WITH TRUNCATE_ONLY
DBCC SHRINKFILE ('databaselog_log', 100) WITH NO_INFOMSGS
It will shrink the log to 100 MB
|||thanks dear
my problem solved with following
BACKUP LOG databasename WITH TRUNCATE_ONLY
DBCC SHRINKFILE ('databaselog_log', 2) WITH NO_INFOMSGS
DBCC SHRINKFILE(mydatabase)
database log file size problem!
Somehow my database log has (ldf file) has grown to over 60GB! and the
database it is associated with is only 32MB, how can I compress this file?
it seems to be getting larger by the hour and now disk space is running
out.. thanks!Hi
Look in books online about "recovery models". You probably have the DB set
to Full Recovery and are not making transaction log backups.
Regards
Mike
"Brian Henry" wrote:
> Somehow my database log has (ldf file) has grown to over 60GB! and the
> database it is associated with is only 32MB, how can I compress this file?
> it seems to be getting larger by the hour and now disk space is running
> out.. thanks!
>
>|||How to stop the transaction log of a SQL Server database from growing
unexpectedly
http://support.microsoft.com/?kbid=873235
AMB
"Brian Henry" wrote:
> Somehow my database log has (ldf file) has grown to over 60GB! and the
> database it is associated with is only 32MB, how can I compress this file?
> it seems to be getting larger by the hour and now disk space is running
> out.. thanks!
>
>
database it is associated with is only 32MB, how can I compress this file?
it seems to be getting larger by the hour and now disk space is running
out.. thanks!Hi
Look in books online about "recovery models". You probably have the DB set
to Full Recovery and are not making transaction log backups.
Regards
Mike
"Brian Henry" wrote:
> Somehow my database log has (ldf file) has grown to over 60GB! and the
> database it is associated with is only 32MB, how can I compress this file?
> it seems to be getting larger by the hour and now disk space is running
> out.. thanks!
>
>|||How to stop the transaction log of a SQL Server database from growing
unexpectedly
http://support.microsoft.com/?kbid=873235
AMB
"Brian Henry" wrote:
> Somehow my database log has (ldf file) has grown to over 60GB! and the
> database it is associated with is only 32MB, how can I compress this file?
> it seems to be getting larger by the hour and now disk space is running
> out.. thanks!
>
>
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,
Subscribe to:
Posts (Atom)