Databases > 100 G

100GB is not considered very large these days. No worry!
Linchi

quote:

---

>--Original Message--
>Hi Guys,
> We are planning on making a dataware house in our
>company. The size is approximately 200 to 400 G. We have
>to make a recommendation for a database server. I would
>love to say "Sql Server". But frankly I'm not very
>confident at this point. How many people on this board
>have databases larger than 100 G. Is it feasible to do
>this on Sql Server ? I dont want to say Sql Server and
>have to eat my words later. Any facts are welcome from
>live installations > 100 G.
>Thanks,
>Jack
>.
>

---

I agree with Linchi, 100GB isn't large these days.
Andrew J. Kelly SQL MVP
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:1520a01c3c40d$c3c2ac40$a601280a@.phx
.gbl...[QUOTE]
> 100GB is not considered very large these days. No worry!
> Linchi
>|||I built a 250 GB database on SQL 7.0 back in 1999 on a 4 CPU box and it ran
very well. Now, I have another database on SQL 2000 that's roughly the same
size on an 8 CPU box. The CPU's are barely doing anything and any problems
we've had have been due to the vendor-supplied software. A 100 GB database
these days is no sweat.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:#7WAW7ExDHA.2116@.TK2MSFTNGP11.phx.gbl...
I agree with Linchi, 100GB isn't large these days.
Andrew J. Kelly SQL MVP
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:1520a01c3c40d$c3c2ac40$a601280a@.phx
.gbl...[QUOTE]
> 100GB is not considered very large these days. No worry!
> Linchi
>

Database would not auto grow

SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?
If you increase the size of the data file manually with "alter database
modify file" command, does the file grow and consume the 18GB of free disk
space?
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
> SQL Server 2000 running on Windows NT4 Server, Database Data File on a
disk
> with a single NTFS Partition of 100Gb.
> We have a database with the data file set to auto grow by 7% with
> unrestricted file growth.
> At the point that it reached 32Gb it ceased to auto grow, updates, inserts
> were failing. There is 18GB free on the disk on which the associated data
> file resides.
> In the end we just associated another data file with the database because
we
> couldn't work out what was going on.
> Anyone have any suggestions ?
>
|||Check SQL Server error log to see if the 'auto grow' is resulting in any
errors. Can you post those errors here, if you see any?
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?
|||Hello
This could be because the amount of space that autogrow needs to grow the
file by is large enough that the request times out while the newly
allocated portion of the file is still being zeroed out. Change the 7% to
500MB (from database file properties window in Enterprise Manager) and
check if autogrow works again.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Database would not auto grow

SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?If you increase the size of the data file manually with "alter database
modify file" command, does the file grow and consume the 18GB of free disk
space?
--
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
> SQL Server 2000 running on Windows NT4 Server, Database Data File on a
disk
> with a single NTFS Partition of 100Gb.
> We have a database with the data file set to auto grow by 7% with
> unrestricted file growth.
> At the point that it reached 32Gb it ceased to auto grow, updates, inserts
> were failing. There is 18GB free on the disk on which the associated data
> file resides.
> In the end we just associated another data file with the database because
we
> couldn't work out what was going on.
> Anyone have any suggestions ?
>|||Check SQL Server error log to see if the 'auto grow' is resulting in any
errors. Can you post those errors here, if you see any?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?|||Hello
This could be because the amount of space that autogrow needs to grow the
file by is large enough that the request times out while the newly
allocated portion of the file is still being zeroed out. Change the 7% to
500MB (from database file properties window in Enterprise Manager) and
check if autogrow works again.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Database would not auto grow

SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?If you increase the size of the data file manually with "alter database
modify file" command, does the file grow and consume the 18GB of free disk
space?
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
> SQL Server 2000 running on Windows NT4 Server, Database Data File on a
disk
> with a single NTFS Partition of 100Gb.
> We have a database with the data file set to auto grow by 7% with
> unrestricted file growth.
> At the point that it reached 32Gb it ceased to auto grow, updates, inserts
> were failing. There is 18GB free on the disk on which the associated data
> file resides.
> In the end we just associated another data file with the database because
we
> couldn't work out what was going on.
> Anyone have any suggestions ?
>|||Check SQL Server error log to see if the 'auto grow' is resulting in any
errors. Can you post those errors here, if you see any?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?|||Hello
This could be because the amount of space that autogrow needs to grow the
file by is large enough that the request times out while the newly
allocated portion of the file is still being zeroed out. Change the 7% to
500MB (from database file properties window in Enterprise Manager) and
check if autogrow works again.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.