But in short: you need to evaluate your server environment and then set the
memory and then test & monitor.
You may need to plan on checking things over time and tweaking as needed.
Basically there are a number of things to take into account like:
1) is this server only running SQL server?
2) How much ram is installed?
3) What are the average and maximum number of client connections?
4) How large is your database?
5) Do you have a problem with performance now?
6) What are you trying to improve?
The min and max are what SQL server sees as *possible*
The "running" is what you are using.
25600 is "about" 50 megs of ram... what amount is installed on the server?
50 megs means that someone has set this for you at some point. The default
is about 16 megs.
User connections should be set based on what you need.
Many of these values are static, if you ask for too much you will just waste
ram and hurt performance.
Like I said; hit the books, without knowing a bunch about your site I could
give you bad advice. And besides *you* want to
Know how to tune your system now don't you?
It's not that it's that hard. It's just that the "right answer" depends on
things that only you know.
-----Original Message-----
From: radiusnt-request@iea-software.com
[mailto:radiusnt-request@iea-software.com]On Behalf Of Danny Sinang
Sent: Thursday, April 20, 2000 11:58 PM
To: radiusnt@iea-software.com
Subject: Re: [RadiusNT] SQL Server and RadiusNT
Hi Denny,
My SQL Server 6.5 Memory settings are :
Min 2800
Max 1048576
Running 25600
Current 25600
Will SQL Server automatically use up more memory as needed ? Or do I need to
regularly increase the Current setting ?
And what other settings did you alter / increase ? What is your "User
Connections" setting ?
- Danny
----- Original Message -----
From: Denny Figuerres <dennyf@inreach.com>
To: <radiusnt@iea-software.com>
Sent: Friday, April 21, 2000 2:18 PM
Subject: RE: [RadiusNT] SQL Server and RadiusNT
> Open Enterprise Manager
>
> Right click on the icon for your server and select "Configure"
>
> That opens up a dialog with 4 tabs, click on the one labeled
"Configuration"
>
> Look at the list of settings... on of them about half way down is "Memory"
> Read the description... the number is a value in "Pages" of 2048 bytes
or
> 2K.
>
> This is a static limit, you have to stop and start the service after
making
> a change.
>
> This is also one of the things that has been improved with SQL 7 - in
> version 7 it's dynamic
> So you don't have to set it manually in version 7.
>
> Depending on your system requirements of course :- )
>
> Check out some good books on running SQL server before tweaking things...
> If you can still get it there is a two-book set from MS Press on SQL
server
> 6.5 along with a trial copy on CD so that you can setup a learning system
to
> play with.
>
>
>
> -----Original Message-----
> From: radiusnt-request@iea-software.com
> [mailto:radiusnt-request@iea-software.com]On Behalf Of Danny Sinang
> Sent: Thursday, April 20, 2000 6:48 PM
> To: radiusnt@iea-software.com
> Subject: Re: [RadiusNT] SQL Server and RadiusNT
>
> Hi Denny,
>
> I'm just starting to use SQL Server 6.5 and Emerald.
>
> Where do I check how much RAM SQL Server uses ?
>
> - Danny Sinang
>
> ----- Original Message -----
> From: Denny Figuerres <dennyf@inreach.com>
> To: <radiusnt@iea-software.com>
> Sent: Friday, April 21, 2000 2:58 AM
> Subject: RE: [RadiusNT] SQL Server and RadiusNT
>
>
> > What changed?
> >
> > You may not need to move it depending on what the conditions are.
> >
> > For example:
> >
> > RAM, many folks setup a server with say 128 megs of ram, when your calls
> > table is small and your number of terminal servers is small that's ok.
> > But if you have more calls records to manage you may just need more ram
> for
> > SQL Server to run well.
> >
> > If you have not done so checkout information on how to use performance
> > monitor to view things like:
> > Cache hit ratio, number of writes, number of reads, number of
transactions
> > and other stats.
> >
> > Unless you a) have huge numbers of users or b) have a weak server (IE:
old
> > Pentium 100, no raid hardware etc...) you do *have* to split them.
> >
> > Well in fact there are some arguments why you should (can we say build a
> > more robust system here )
> >
> > But if you are just running low on ram well...
> >
> > In my exp. 128 megs is only enough ram to test SQL server or run a few
> > hundred accounts.
> > 256 megs or more is 100% better.
> > Depending on what that box is running NT may need 64 megs just to build
a
> > good "working set" in ram.
> > Also if you have not changed the default setting SQL server only gets
> about
> > 16 megs of ram which is *WAY* to low
> > For any real call logging.
> >
> > When if first used RadiusNT I've ran logging for 20,000 + accounts on
128
> > megs by just killing all the "extra" junk and tuning SQL servers ram.
> > That ran fine for quite a while and the performance began to drag when
the
> > calls table grew to over 2 million records. Even then it was "OK"
> > So at that point you need to either trim the table or have more ram.
> >
> > That box by the way was (as I recall):
> > PII 400
> > 128 Megs
> > Adaptec ARO-1130 Raid Port
> > 6 4.5 Gig Ultra SCSI Disks in a Raid 5 config with one hot spare.
> >
> > No Web, Mail,Print, fileshare or other services on that box ...
> > Just NT,SQL and RadiusNT.
> >
> > PS: that load was *Accounting* records no authentication was on that
box.
> >
> >
> > -----Original Message-----
> > From: radiusnt-request@iea-software.com
> > [mailto:radiusnt-request@iea-software.com]On Behalf Of
> majordomo@essex1.com
> > Sent: Thursday, April 20, 2000 10:48 AM
> > To: radiusnt@iea-software.com
> > Subject: [RadiusNT] SQL Server and RadiusNT
> >
> > I am running RadiusNT Enterprise and SQL 6.5 on the same server at this
> > time. The system has handled remarkably well in the past, but it is
> > starting to show degredation in performance. I am planning to move the
> > radius database over to a new dedicated SQL server and wanted to know
the
> > advantages/disadvantages of separating my Radius and SQL server. Note
> that
> > the existing SQL is dedicated to Radius.
> >
> > TIA,
> > Tom
> > tep@essex1.com
> >
> >
> > For more information about this list (including removal) go to:
> > http://www.iea-software.com/support/maillists/liststart
> >
> >
> > For more information about this list (including removal) go to:
> > http://www.iea-software.com/support/maillists/liststart
>
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
>
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart