Building New SQL Server

Hello all,
I am hoping some can spend a minute to educate me a little here.
We are looking at building a SQL server for our Network applications. This
would be WSUS, our inventorying solution, our helpdesk software and a number
of other network based support applications(used only by the IT department).
Is there any problem with running a number of application specific databses
on a SQL server if those apps really arent overally intensive? I dont think
there is, but I may be wrong.
Also, what about running a few app based databases on a SQL server that is
running an ERP solution?
On top of that what about hosting an ERP solution for about maybe 50-60 full
time users on a SQL server that is already running another databse for an
HR/Payroll based application that is used by maybe five peole? If the server
is spec'ed appropriately?
We are faced with the dilemma of implementing a new SQL server for an HR
app, this server would not be pushed at all, infact it would probably idle
98% of the time even with these users on and working. Im a trying to
determine whether or not it would be feasible to run some other applications
on the same SQL server without effecting performance or the existing database
environment and actually utilise the hardware.
I have little knowledge of SQL aside from installing it and setting up
databases, users and permissions.
Thanks
Hi
What you are wanting to do is certainly possible, hopefully you are not
going to need multiple instances, although you would need to consider the
security implications of using a single instance.
You would have to monitor usage to make sure nothing is doing anything to
stress the server to the detriment of the other applications, you may want to
look at what MOM could offer your to do this. You may want to consider
MSDE/SQL Express for the smaller applications if you have alternate servers
or only need local databases.
John
"a_user" wrote:

> Hello all,
> I am hoping some can spend a minute to educate me a little here.
> We are looking at building a SQL server for our Network applications. This
> would be WSUS, our inventorying solution, our helpdesk software and a number
> of other network based support applications(used only by the IT department).
> Is there any problem with running a number of application specific databses
> on a SQL server if those apps really arent overally intensive? I dont think
> there is, but I may be wrong.
> Also, what about running a few app based databases on a SQL server that is
> running an ERP solution?
> On top of that what about hosting an ERP solution for about maybe 50-60 full
> time users on a SQL server that is already running another databse for an
> HR/Payroll based application that is used by maybe five peole? If the server
> is spec'ed appropriately?
> We are faced with the dilemma of implementing a new SQL server for an HR
> app, this server would not be pushed at all, infact it would probably idle
> 98% of the time even with these users on and working. Im a trying to
> determine whether or not it would be feasible to run some other applications
> on the same SQL server without effecting performance or the existing database
> environment and actually utilise the hardware.
> I have little knowledge of SQL aside from installing it and setting up
> databases, users and permissions.
> Thanks
|||Hi John,
Thanks for the info. Using MSDE or localized single instance database
engines is what I am trying to get away from. Currently we have five
different applications all using msde as a local database engine, I would
rather have every application use a different database but on a SQL server.
It allows us to offload this processing from the services servers,
centralizes our databases, eases in recovery or restoration and especially if
scaling out to a larger box or more distributed boxes in the future as we add
servers.
I guess from a performance standpoint there is not much else to do aside
from monitoring the impact of additional databases on the server I just
wanted to ensure that databases for totally different applications could
reside on the same SQL server with impacting each other.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> What you are wanting to do is certainly possible, hopefully you are not
> going to need multiple instances, although you would need to consider the
> security implications of using a single instance.
> You would have to monitor usage to make sure nothing is doing anything to
> stress the server to the detriment of the other applications, you may want to
> look at what MOM could offer your to do this. You may want to consider
> MSDE/SQL Express for the smaller applications if you have alternate servers
> or only need local databases.
>
> John
> "a_user" wrote: