Managing Multiple Servers

14 Jul 2006 10:35 PM

Brian Shannon

I am using sql server 2000 at 3 seperate properties. Each property is
treated as it's own but many times I am required to perform a combined
analysis. I am not a DBA nor do we have a DBA but I am fairly knowledgable
at how to get around. Each server runs the same version of a 3rd party
casino package.

I am looking for someone to point me in a good direction on how to manage
multiple sql servers for data analysis and help with best practices.
Currently we don't have a data warehouse but I have been learning on the
subjects of datawhare houses, analysis services and data mining.

Is using a linked server something that would be good to research?

I have a user database attached to each database that helps me manage task
on the third party DB. One thing that bugs me is when we open a new
property I have to duplicate already created objects such as functions and
stored procedures to the new property. When a change is made I have to
replicate it to each property as well as when a new object is created. We
are growing and looking at acquring new properties and would like to learn
the methods for managing multiple databases at different site locations
before it bites me.

Thanks.

14 Jul 2006 11:01 PM

Arnie Rowland

It will be money well spend to bring in a skilled consultant this early in
the process. There are some design flaws, that if caught early will be easy
to 'repair', but if put off until later can be horrendously expensive. NOTE:
I'm not saying that you have design flaws, but they do tend to unknowingly
'creep' into projects that organically 'evolve'.

A good source control regimen is worth all of the aggravation encountered as
you get used to the required discipline. With source control, it becomes
easier to know what objects are in the next 'upgrade' that need to be pushed
out to the servers. It's also easier to create a 'start-up' package of the
objects that have to be installed locally at each location.

There are third party tools that will help create deployment packages so
that you can automate a lot of the work.

You have to start thinking s little like a 'software' manufacturer. You
create objects that have to be tested, and tested, and tested, and then
deployed. How do you deploy (and upgrade) to all of your 'customers'? How do
you keep tabs on what versions each 'customer' is running?

--
Arnie Rowland
"To be successful, your heart must accompany your knowledge."

Show quote

"Brian Shannon" <brian.shan***@diamondjo.com> wrote in message
news:eL4zGa5pGHA.3288@TK2MSFTNGP03.phx.gbl...
>I am using sql server 2000 at 3 seperate properties. Each property is
>treated as it's own but many times I am required to perform a combined
>analysis. I am not a DBA nor do we have a DBA but I am fairly knowledgable
>at how to get around. Each server runs the same version of a 3rd party
>casino package.
>
> I am looking for someone to point me in a good direction on how to manage
> multiple sql servers for data analysis and help with best practices.
> Currently we don't have a data warehouse but I have been learning on the
> subjects of datawhare houses, analysis services and data mining.
>
> Is using a linked server something that would be good to research?
>
> I have a user database attached to each database that helps me manage task
> on the third party DB. One thing that bugs me is when we open a new
> property I have to duplicate already created objects such as functions and
> stored procedures to the new property. When a change is made I have to
> replicate it to each property as well as when a new object is created. We
> are growing and looking at acquring new properties and would like to learn
> the methods for managing multiple databases at different site locations
> before it bites me.
>
> Thanks.
>