| |
|
Run your database
online
Programming
services available ...
|
 |
|
SQL hosting - Access database hosting online
with ASP and .NET services
|
SQL Server:
SQL Server 2000 running on the Windows
can support up to 32 CPU and up to 64GB
physical memory (RAM) on a computer!
How Fast Is Fast? SQL Server 2000
can handle 709,220 transactions per minute!
SQL Server 2000 has further established its
position as the fastest database in the
world. With a performance rating of 709,220
transactions per minute (tpmC) and
price/tpmC of $14.96 US, a 32-node Compaq
ProLiant DL760-900-256P system exceeded the
previous record, which was also held by SQL
Server 2000.
Another benchmark test demonstrated support
for 25,200 simulated concurrent users and
performed CRM transactions at the rate of
2,024 business processes per minute. These
results were achieved on a 24-processor
Unisys ES7000 database server and yielded
average response times between one and two
seconds.
How do I convert an .MDB to SQL
Server?
For Access 97: The Access Upsizing
Wizard Free download:
http://www.microsoft.com/accessdev/prodinfo/aut97dat.htm
The Access Upsizing Wizard
preserves database structure
including data, indexes, defaults,
and so on, and automatically converts
Access validation rules and defaults
to the appropriate SQL Server
equivalents. It also maintains table
relationships and referential
integrity after upsizing.
For Access 2000: (Upgrading to an .ADP
file) The upsizing wizard is built in
to the Access runtime. You can choose to
create an .MDB with SQL Server tables
linked, or to an .ADP file. Provides all
the functionality of the Access 97 upsizing
wizard.
The table below the book resources displays
the general SQL Server 97/2000
characteristics:
Some SQL book
resources:
|
| SQL Object |
Maximum
sizes/numbers |
| Connections per
client |
Maximum value of configured
connections |
| Batch size |
65,536 * Network Packet
Size |
| Bytes per short string
column |
8,000 |
| Bytes per text, ntext,or image
column |
2 GB-2 |
| Bytes per
index |
900 |
| Bytes per primary
key |
900 |
| Bytes per foreign
key |
900 |
| Bytes per
row |
8,060 |
| Clustered indexes per
table |
1 |
| Bytes in source text of a
stored procedure |
Lesser of batch size or 250
MB |
| Columns per
index |
16 |
| Columns per primary
key |
16 |
| Columns per foreign
key |
16 |
| Columns per base
table |
1,024 |
| Columns per INSERT
statement |
1,024 |
| Columns per SELECT
statement |
4,096 |
| Database
size |
1,048,516 TB |
| Databases per instance of SQL
Server |
32,767 |
| Filegroups per
database |
256 |
| File size
(data) |
32 TB |
| Files per
database |
32,767 |
| Identifier length (in
characters) |
128 |
| Nested stored procedure
levels |
32 |
| Locks per
connection |
Max. locks per
server |
| Nested
subqueries |
32 |
| Nested trigger
levels |
32 |
| Objects in a
database |
2,147,483,647 |
| Nonclustered indexes per
table |
249 |
| Parameters per stored
procedure |
1,024 |
| REFERENCES per
table |
253 |
| Rows per
table |
Limited by available
storage |
| Tables per
database |
Limited by number of objects in
a database |
| Tables per SELECT
statement |
256 |
| UNIQUE indexes or constraints
per table |
249 nonclustered and 1
clustered |
| Triggers per
table |
Limited by number of objects in
a database |
|
|
