February 13, 2005 at 10:48 pm
Hi!
I am about to create a data base tht stores information about my company's inventory. How ever this inventory is small in size but huge in numbers. I would like to know how much data can SQL database hold, as i am a bit confused on its data capacity. I would also like to inform u that the inventory can go upto millions of data. Thanx in Advance.
--UnOmE--
** Once i Thought I was Wrong, But i was mistaken!!!
February 13, 2005 at 10:57 pm
read the capacity specifications-SQL Server section of the BOL
My Blog:
February 14, 2005 at 11:52 pm
Hi,
Thanx for ur advise. It was really helpful. How ever it says to me 1,048,516 TB^3 . Does this means that it is three times 1,048,516. Pls advise.
Regards
Ansar
** Once I thought I was Wring, But i was mistaken !!!
February 15, 2005 at 2:07 am
No, Ansar,
The small 3 means the remark #3 under the table:
Database size | 1,048,516 TB3 | 1,048,516 TB3 |
Databases per instance of SQL Server | 32,767 | 32,767 |
Filegroups per database | 256 | 256 |
Files per database | 32,767 | 32,767 |
File size (data) | 32 TB | 32 TB |
File size (log) | 4 TB | 32 TB |
3 The size of a database cannot exceed 2 GB when using the SQL Server 2000 Desktop Engine or the Microsoft Data Engine (MSDE) 1.0.
And do you really need a database size over 1 million TB????
Bye
Gabor
February 15, 2005 at 4:47 am
Thanx a lot for ur advise. How ever i am about to programme a database that enters in a stock of mobiele phones in the ware house. And these mobile phones are being barcoded and entered. And some times it can go to more than a million. As it is my company that uses this. And we r into refurbishment. Hence we have to count even the smallest element and put in to consideration. My worry is that, will the data base accomodate such high amount of data.? Pls advise the best solution.
Regards
Ansar
February 15, 2005 at 8:05 am
No problem.
It will accomodate. It depends only on the hardware you are using.
We have for example some quite large SAP databases (over 400 GB each) where the biggest tables have over 20 millions of rows) and we have over 26.000 tables (and over 85.000 rows in the sysobjects table)
But 1 million rows is not too much. Once correctly indexed your transactions will run as it would be only 100 rows in that table. The only performance diffrence you will see is when you are making full table scans
Bye
Gabor
February 15, 2005 at 10:55 pm
Thanx again for your advise. I really appreciate it. How ever, regrding the indexing, i think u seem to be advising me to use primary index on all the tables for faster searches right!!! I would do that and i plan to use hash tables aswell for fast searches. Pls advise on any good methods....
regards
Ansar
February 16, 2005 at 1:02 am
To ba able to provide you with right advisis first I have to lnow the type of queries you want to execute against the database.
Primary key are of course important, but not the most important for your specific application need.
To be able to advise you first I would need to know your table structure sand your queries you plan to run against the database.
I don't know what you mean by hash table, but be aware if you want to manually maintain external tables to your main table, it could represent some additional level of effort and could be source of error if you introduce by mistake a wrong statement.
Bye
Gabor
February 18, 2005 at 3:11 am
Actually i am about to start programming in vb.net. My back end is SQL server. And Hashtables are just liek arrays, but i also has the index of the field that we r searchoing. How ever i would be in touch with u if i get stcuck in any of the queries. My only concern was thesize and capacity. And u solved that for me. Thax a lot pal.
Regards
Ansar
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply