How big can a database be in a sql 2000 and in SQL 7.0? Is it 6 gig the
largest size!
No, try 1,048,516 TERABYTES. That's the figure in Books Online... Now,
where are we going to find a disk big enough to test that limit?
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
> How big can a database be in a sql 2000 and in SQL 7.0? Is it 6 gig the
> largest size!
|||MS posts white papers detailing DBs as big as 10TB. But in general even
with exceptional hardware anything bigger than 500GB takes careful planning
and a significant change in mind set. Of course a poorly designed 20GB DB
could also be a handful.
Oh if only my DBs were 6GB again...those where the days...
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
> How big can a database be in a sql 2000 and in SQL 7.0? Is it 6 gig the
> largest size!
|||Thanks guys, that is what I thought but their are people out here that only
work on access db! RAY so if I look at the white papers for sql 2000 I will
find this information
"Ray" wrote:
> MS posts white papers detailing DBs as big as 10TB. But in general even
> with exceptional hardware anything bigger than 500GB takes careful planning
> and a significant change in mind set. Of course a poorly designed 20GB DB
> could also be a handful.
> Oh if only my DBs were 6GB again...those where the days...
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
>
>
|||MSAccess has its place but it's not designed or intended to be a enterprise
class database. Calling it a workgroup class database is pushing it.
Here's the classic MS whitepaper on how to build a 10TB database.
http://www.emulex.com/products/white/fc/humangenome.pdf
I also ran across this basic comparison.
http://www.mssqlcity.com/Articles/Co...QLvsAccess.htm
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:1252C739-5BD1-44FF-B4C2-34792C999AB0@.microsoft.com...[vbcol=seagreen]
> Thanks guys, that is what I thought but their are people out here that
> only
> work on access db! RAY so if I look at the white papers for sql 2000 I
> will
> find this information
> "Ray" wrote:
Showing posts with label gig. Show all posts
Showing posts with label gig. Show all posts
Monday, March 12, 2012
How big is big
How big can a database be in a sql 2000 and in SQL 7.0' Is it 6 gig the
largest size!No, try 1,048,516 TERABYTES. That's the figure in Books Online... Now,
where are we going to find a disk big enough to test that limit?
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
> How big can a database be in a sql 2000 and in SQL 7.0' Is it 6 gig the
> largest size!|||MS posts white papers detailing DBs as big as 10TB. But in general even
with exceptional hardware anything bigger than 500GB takes careful planning
and a significant change in mind set. Of course a poorly designed 20GB DB
could also be a handful.
Oh if only my DBs were 6GB again...those where the days...
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
> How big can a database be in a sql 2000 and in SQL 7.0' Is it 6 gig the
> largest size!|||Thanks guys, that is what I thought but their are people out here that only
work on access db! RAY so if I look at the white papers for sql 2000 I will
find this information
"Ray" wrote:
> MS posts white papers detailing DBs as big as 10TB. But in general even
> with exceptional hardware anything bigger than 500GB takes careful plannin
g
> and a significant change in mind set. Of course a poorly designed 20GB DB
> could also be a handful.
> Oh if only my DBs were 6GB again...those where the days...
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
>
>|||MSAccess has its place but it's not designed or intended to be a enterprise
class database. Calling it a workgroup class database is pushing it.
Here's the classic MS whitepaper on how to build a 10TB database.
http://www.emulex.com/products/white/fc/humangenome.pdf
I also ran across this basic comparison.
http://www.mssqlcity.com/Articles/C...SQLvsAccess.htm
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:1252C739-5BD1-44FF-B4C2-34792C999AB0@.microsoft.com...[vbcol=seagreen]
> Thanks guys, that is what I thought but their are people out here that
> only
> work on access db! RAY so if I look at the white papers for sql 2000 I
> will
> find this information
> "Ray" wrote:
>
largest size!No, try 1,048,516 TERABYTES. That's the figure in Books Online... Now,
where are we going to find a disk big enough to test that limit?
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
> How big can a database be in a sql 2000 and in SQL 7.0' Is it 6 gig the
> largest size!|||MS posts white papers detailing DBs as big as 10TB. But in general even
with exceptional hardware anything bigger than 500GB takes careful planning
and a significant change in mind set. Of course a poorly designed 20GB DB
could also be a handful.
Oh if only my DBs were 6GB again...those where the days...
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
> How big can a database be in a sql 2000 and in SQL 7.0' Is it 6 gig the
> largest size!|||Thanks guys, that is what I thought but their are people out here that only
work on access db! RAY so if I look at the white papers for sql 2000 I will
find this information
"Ray" wrote:
> MS posts white papers detailing DBs as big as 10TB. But in general even
> with exceptional hardware anything bigger than 500GB takes careful plannin
g
> and a significant change in mind set. Of course a poorly designed 20GB DB
> could also be a handful.
> Oh if only my DBs were 6GB again...those where the days...
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:FA13B9D5-5DED-48A5-99C7-5A27B35BBF9B@.microsoft.com...
>
>|||MSAccess has its place but it's not designed or intended to be a enterprise
class database. Calling it a workgroup class database is pushing it.
Here's the classic MS whitepaper on how to build a 10TB database.
http://www.emulex.com/products/white/fc/humangenome.pdf
I also ran across this basic comparison.
http://www.mssqlcity.com/Articles/C...SQLvsAccess.htm
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:1252C739-5BD1-44FF-B4C2-34792C999AB0@.microsoft.com...[vbcol=seagreen]
> Thanks guys, that is what I thought but their are people out here that
> only
> work on access db! RAY so if I look at the white papers for sql 2000 I
> will
> find this information
> "Ray" wrote:
>
Friday, March 9, 2012
How are extensions with no Filter handled?
I can't find the answer to this anywhere. I have a 16+ Gig table with
an image column that is full-text indexed based on the usual extension
column. Some of the extensions are not the standard ones with the
basic filters. For these extensions I do not want to be indexed with
the full-text search. How does SQL Server handle these...does it
ignore them or use the text filter? Could this slow down the
population of the index if it does not have a filter for that
extension? Any ideas of how to better manage this are greatly
appreciated. Thanks!
Tim Cochrane
t.cochrane@.inetppc.com
Tim,
For those file extensions that you do not want to FT Index, or are not FT
Indexed, you should see the following entry in the application event log for
those file types:
Event Type: SQLFTHNDLR
Event Source: Information
Event Category: None
Event ID: 2001
Date: 8/24/2005
Time: 4:05:35 PM
User: N/A
Computer: JTKWIN2003
Description:
One or more documents stored in image columns with extension 'doc' did not
get full-text indexed because loading the filter failed with error '0x1'.
Replace 'doc' for your file extension. You may also try setting the "file
extension" column value to NULL (if the column is nullable) or to ' '
(space) if it is not, and run a Full Population to compare against your
normal Full Population with this column populated to get some idea of the
performance difference.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"utcochra" <t.cochrane@.inetppc.com> wrote in message
news:1131116166.002651.286560@.g14g2000cwa.googlegr oups.com...
>I can't find the answer to this anywhere. I have a 16+ Gig table with
> an image column that is full-text indexed based on the usual extension
> column. Some of the extensions are not the standard ones with the
> basic filters. For these extensions I do not want to be indexed with
> the full-text search. How does SQL Server handle these...does it
> ignore them or use the text filter? Could this slow down the
> population of the index if it does not have a filter for that
> extension? Any ideas of how to better manage this are greatly
> appreciated. Thanks!
> Tim Cochrane
> t.cochrane@.inetppc.com
>
an image column that is full-text indexed based on the usual extension
column. Some of the extensions are not the standard ones with the
basic filters. For these extensions I do not want to be indexed with
the full-text search. How does SQL Server handle these...does it
ignore them or use the text filter? Could this slow down the
population of the index if it does not have a filter for that
extension? Any ideas of how to better manage this are greatly
appreciated. Thanks!
Tim Cochrane
t.cochrane@.inetppc.com
Tim,
For those file extensions that you do not want to FT Index, or are not FT
Indexed, you should see the following entry in the application event log for
those file types:
Event Type: SQLFTHNDLR
Event Source: Information
Event Category: None
Event ID: 2001
Date: 8/24/2005
Time: 4:05:35 PM
User: N/A
Computer: JTKWIN2003
Description:
One or more documents stored in image columns with extension 'doc' did not
get full-text indexed because loading the filter failed with error '0x1'.
Replace 'doc' for your file extension. You may also try setting the "file
extension" column value to NULL (if the column is nullable) or to ' '
(space) if it is not, and run a Full Population to compare against your
normal Full Population with this column populated to get some idea of the
performance difference.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"utcochra" <t.cochrane@.inetppc.com> wrote in message
news:1131116166.002651.286560@.g14g2000cwa.googlegr oups.com...
>I can't find the answer to this anywhere. I have a 16+ Gig table with
> an image column that is full-text indexed based on the usual extension
> column. Some of the extensions are not the standard ones with the
> basic filters. For these extensions I do not want to be indexed with
> the full-text search. How does SQL Server handle these...does it
> ignore them or use the text filter? Could this slow down the
> population of the index if it does not have a filter for that
> extension? Any ideas of how to better manage this are greatly
> appreciated. Thanks!
> Tim Cochrane
> t.cochrane@.inetppc.com
>
Subscribe to:
Posts (Atom)