Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 How to calculate hardware for SQL Server 2k?

Author  Topic 

LSorarrain
Starting Member

6 Posts

Posted - 2005-02-08 : 13:43:24
Hi!

How to calculate the correct hardware for SQL Server 2000?

for example, the space of disk is calculated with some formulates?, the amount of memory is calculated with some formulates?

thanks for respond!

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2005-02-08 : 14:02:32
emm what calculations are you talking about?
sql server takes all of the memory it can by default. you can change this it's in properties.
place on disk depends on the size of the db.

Go with the flow & have fun! Else fight the flow
Go to Top of Page

LSorarrain
Starting Member

6 Posts

Posted - 2005-02-08 : 14:14:38
The question is for preparing a new server.

A server with 512MB of ram is different that with 1024GB.
Which the amount of memory depends?

The logic is that the calculate contemplates amount of processes, amount of users, etc.

Is but clear the question?
You have patience with my english, please.
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2005-02-08 : 14:18:26
nope. the only thig differnet will be that the 512 ram will be slower under pressure than 1 Gb RAM.
someone correct me if i'm wrong here...

Go with the flow & have fun! Else fight the flow
Go to Top of Page

MichaelP
Jedi Yak

2489 Posts

Posted - 2005-02-08 : 14:27:08
Your english is a bit rough, but I think we understand what you are saying.
As far as the hardware, I'm not sure there's any real forumla. What you need to figure out is how big your database is going to be, is it going to have a high number of users or low number, are you going to be doing mostly reads or mostly writes, etc.

Personally, I'd say get as much RAM as you can afford I'd say 512MB is a minimum, and 1GB would be nice. SQL Server will try to use as much RAM as possible so that it performs as fast as possible.

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>
Go to Top of Page

LSorarrain
Starting Member

6 Posts

Posted - 2005-02-08 : 14:46:17
"Your english is a bit rough, but I think we understand what you are saying." jejejeejejejj that ok! i write in spanish?

ok....

We will join two servers, who today operate separated, in a new Server.

Server 1: 4 processors PIII and 2.5GB ram
Server 2: 2 processors PII and 1GB ram

New Server: 2 processors Xeon and 1GB ram

I think that him lack memory.
I think, also that the disc space affects the total of memory to have.
Like calculating the amount of ram correctly? In oracle there is one formulates, in SQL Server?

thx!
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2005-02-08 : 14:51:38
definitly put more ram. at least 2 gig. otherwise it will ne slow compared to the old ones...
i know of no such formula.

Go with the flow & have fun! Else fight the flow
Go to Top of Page

LSorarrain
Starting Member

6 Posts

Posted - 2005-02-08 : 16:14:51
I know that the server must have 2GB, but, like justifying it?
only with my word?
nonserious createible to request ram to request.
it is understood my problem?

thanks for your time!
Go to Top of Page

LSorarrain
Starting Member

6 Posts

Posted - 2005-02-08 : 16:34:29
I found this......



(Books/adminsql.chm)

Memory Used by SQL Server Objects Specifications
This table lists the amount of memory used by different objects in Microsoft® SQL Server™. The information in this table does not pertain to Microsoft® SQL Server 2000™ Windows® CE Edition.


Object Size for Object SQL Server 7.0
Lock: 96 bytes
Open database: 2,880 bytes
Open object (1): 276 bytes
User connection: 12 KB + (3 * Network Packet Size) (3).

Object Size for SQL Server 2000
Lock: 64 bytes plus 32 bytes per owner.
Open database: 3924 bytes plus 1640 bytes per file and 336 bytes per filegroup.

Open object (1): 256 bytes plus 1724 bytes per index opened on the object(2).

User connection: 12 KB + (3 * Network Packet Size) (3).


(1) Open objects include all tables, views, stored procedures, extended stored procedures, triggers, rules, defaults, and constraints.
(2) Indexes can be opened on tables or views.
(3) Network Packet Size is the size of the tabular data scheme (TDS) packets used to communicate between applications and the relational database engine. The default packet size is 4 KB, and is controlled by the network packet size configuration option

Agur!
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2005-02-08 : 20:01:12
You might want to look at the Microsoft Press SQL Server Performance Tuning Manual. It has a lot of formulas for sizing a server, doing capacity planning, etc. Some of the charts and formulas are great planning, monitoring tools.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2005-02-09 : 07:50:25
this might help you:
http://www.sql-server-performance.com/rc_hardware_planning.asp

Go with the flow & have fun! Else fight the flow
Go to Top of Page

LSorarrain
Starting Member

6 Posts

Posted - 2005-02-09 : 08:29:46
derrickleggett, spirit1, thanks for your answers.
Go to Top of Page
   

- Advertisement -