Consolidation question

I have to move a database from Server A to Server B. I have checked the space
and CPU utilization on both the servers. The database size is 5 GB and there
are 50 concurrent users.
Server A - source server
CPU utilization - <25 %
Available space - 80 Gb
Memory - 2 GB
Memory used by sqlserver.exe - 1800 MB
Memory configured for dynamic allocation by sql server upto 2GB
Server B - destination server
CPU utilization - <10 %
Available space - 80 Gb
Memory - 1795 MB
Memory used by sqlserver.exe - 1500 MB
Memory configured for dynamic allocation by sql server upto 1795 MB
How do I find out if the memory is going to be sufficient after the move? I
ma thinking of reducing the memory allocated to sql servers on both Server A
and Server B to just 1 GB and see the performance of both the servers. If
tehy perform OK at reduced memory then I will assume the memory on
destination Server B will be good enough for the new database. Any insight
will be highly appreciated. Thanks.sharman,
SQL Server uses as much space as it can in its address space unless it has
to give up memory to other processes. But this memory need is not doubled
when you bring another database and 50 users online. The impact on memory
is probably rather small. Certainly, I don't think that restricting memory
on the two servers will give you a meaningful measure for what will happen
when they are brought together on one server.
Of course, you are expecting CPU utilization to go up. Something else that
you should check on each server is the SQL Servers: Buffer Manager \ Page
Life Expectancy. If they are consistently under 300 seconds, that may
indicate that there is too little memory for the active buffer contents,
which will mean more I/O and CPU.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:96430D73-D40A-4961-A95C-00C7E2F0CD89@.microsoft.com...
>I have to move a database from Server A to Server B. I have checked the
>space
> and CPU utilization on both the servers. The database size is 5 GB and
> there
> are 50 concurrent users.
> Server A - source server
> CPU utilization - <25 %
> Available space - 80 Gb
> Memory - 2 GB
> Memory used by sqlserver.exe - 1800 MB
> Memory configured for dynamic allocation by sql server upto 2GB
> Server B - destination server
> CPU utilization - <10 %
> Available space - 80 Gb
> Memory - 1795 MB
> Memory used by sqlserver.exe - 1500 MB
> Memory configured for dynamic allocation by sql server upto 1795 MB
> How do I find out if the memory is going to be sufficient after the move?
> I
> ma thinking of reducing the memory allocated to sql servers on both Server
> A
> and Server B to just 1 GB and see the performance of both the servers. If
> tehy perform OK at reduced memory then I will assume the memory on
> destination Server B will be good enough for the new database. Any insight
> will be highly appreciated. Thanks.|||Hi Russell,
Thanks for the info. I did a quick check of Page Life Expectancy on both the
servers. These are the typical values that I found.
Sever to which the db will be moved = 33270 (average)
Server on which the db currently resides = varies between 282 to 378
"Russell Fields" wrote:
> sharman,
> SQL Server uses as much space as it can in its address space unless it has
> to give up memory to other processes. But this memory need is not doubled
> when you bring another database and 50 users online. The impact on memory
> is probably rather small. Certainly, I don't think that restricting memory
> on the two servers will give you a meaningful measure for what will happen
> when they are brought together on one server.
> Of course, you are expecting CPU utilization to go up. Something else that
> you should check on each server is the SQL Servers: Buffer Manager \ Page
> Life Expectancy. If they are consistently under 300 seconds, that may
> indicate that there is too little memory for the active buffer contents,
> which will mean more I/O and CPU.
> RLF
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:96430D73-D40A-4961-A95C-00C7E2F0CD89@.microsoft.com...
> >I have to move a database from Server A to Server B. I have checked the
> >space
> > and CPU utilization on both the servers. The database size is 5 GB and
> > there
> > are 50 concurrent users.
> >
> > Server A - source server
> > CPU utilization - <25 %
> > Available space - 80 Gb
> > Memory - 2 GB
> > Memory used by sqlserver.exe - 1800 MB
> > Memory configured for dynamic allocation by sql server upto 2GB
> >
> > Server B - destination server
> > CPU utilization - <10 %
> > Available space - 80 Gb
> > Memory - 1795 MB
> > Memory used by sqlserver.exe - 1500 MB
> > Memory configured for dynamic allocation by sql server upto 1795 MB
> >
> > How do I find out if the memory is going to be sufficient after the move?
> > I
> > ma thinking of reducing the memory allocated to sql servers on both Server
> > A
> > and Server B to just 1 GB and see the performance of both the servers. If
> > tehy perform OK at reduced memory then I will assume the memory on
> > destination Server B will be good enough for the new database. Any insight
> > will be highly appreciated. Thanks.
>
>|||Sharman,
It looks like you are on the low, but acceptable side of Page Life
Expectancy. However, reviewing your notes says that you are moving to the
server with a couple hundred megabytes less memory. So you may find
yourself experiencing some memory pressure issues when the memory load moves
machines.
It looks like you are fine with your CPU for the time being, but it would be
good to bump up your memory a bit, if you can.
You did not mention which version of OS and SQL Server you are running, but
those will make a difference in your memory options.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:A552585E-485D-4149-B797-A014B1E2BAAA@.microsoft.com...
> Hi Russell,
> Thanks for the info. I did a quick check of Page Life Expectancy on both
> the
> servers. These are the typical values that I found.
> Sever to which the db will be moved = 33270 (average)
> Server on which the db currently resides = varies between 282 to 378
> "Russell Fields" wrote:
>> sharman,
>> SQL Server uses as much space as it can in its address space unless it
>> has
>> to give up memory to other processes. But this memory need is not
>> doubled
>> when you bring another database and 50 users online. The impact on
>> memory
>> is probably rather small. Certainly, I don't think that restricting
>> memory
>> on the two servers will give you a meaningful measure for what will
>> happen
>> when they are brought together on one server.
>> Of course, you are expecting CPU utilization to go up. Something else
>> that
>> you should check on each server is the SQL Servers: Buffer Manager \ Page
>> Life Expectancy. If they are consistently under 300 seconds, that may
>> indicate that there is too little memory for the active buffer contents,
>> which will mean more I/O and CPU.
>> RLF
>> "sharman" <sharman@.discussions.microsoft.com> wrote in message
>> news:96430D73-D40A-4961-A95C-00C7E2F0CD89@.microsoft.com...
>> >I have to move a database from Server A to Server B. I have checked the
>> >space
>> > and CPU utilization on both the servers. The database size is 5 GB and
>> > there
>> > are 50 concurrent users.
>> >
>> > Server A - source server
>> > CPU utilization - <25 %
>> > Available space - 80 Gb
>> > Memory - 2 GB
>> > Memory used by sqlserver.exe - 1800 MB
>> > Memory configured for dynamic allocation by sql server upto 2GB
>> >
>> > Server B - destination server
>> > CPU utilization - <10 %
>> > Available space - 80 Gb
>> > Memory - 1795 MB
>> > Memory used by sqlserver.exe - 1500 MB
>> > Memory configured for dynamic allocation by sql server upto 1795 MB
>> >
>> > How do I find out if the memory is going to be sufficient after the
>> > move?
>> > I
>> > ma thinking of reducing the memory allocated to sql servers on both
>> > Server
>> > A
>> > and Server B to just 1 GB and see the performance of both the servers.
>> > If
>> > tehy perform OK at reduced memory then I will assume the memory on
>> > destination Server B will be good enough for the new database. Any
>> > insight
>> > will be highly appreciated. Thanks.
>>