Hi. I have a maintenece plan on my development server that rebuilds
indexes and updates statistics of a certian database that undergoes a
lot of updates of data daily; it also truncates the log file and backs
up the database.
Now, is there any way to script it to deploy it to client computers,
either as is or within a setup routine with names and paths inserted on
the fly?Oh. This is about SQL Server 2005|||Eh? Deploy it to client computers?
What do you mean by "it?"
The maintenance plan?
The database(s) that you back up?
What do you mean by "client computer?"
Desktops?
Servers running SQL Server?
To me, a client computer means a desktop or notebook. These computers do
not have SQL Server installed and they should not need a maintenance plan or
a database deployed to it.
I am guessing that many people are confused by your question. If you can
better explan what you want to do perhaps someone will be able to provide an
answer.
--
Keith Kratochvil
<realgeek@.gmail.com> wrote in message
news:1160060522.143749.302550@.i42g2000cwa.googlegroups.com...
> Hi. I have a maintenece plan on my development server that rebuilds
> indexes and updates statistics of a certian database that undergoes a
> lot of updates of data daily; it also truncates the log file and backs
> up the database.
> Now, is there any way to script it to deploy it to client computers,
> either as is or within a setup routine with names and paths inserted on
> the fly?
>|||> What do you mean by "client computer?"
> Desktops?
> Servers running SQL Server?
> To me, a client computer means a desktop or notebook. These computers do
> not have SQL Server installed and they should not need a maintenance plan or
> a database deployed to it.
>
By it, I mean a maintenance plan, by client computer, I mean client
server, e.g. the place where the application is deployed.
I have an installation script that restores database to a chosen
location from backup provided with installation (the db initially has a
lot of data so I chose that over scripting it), creates and maps logins
etc; I wanted to add maintenance plan creation script to it but I found
no way to script maintenance plan from Management Studio|||realgeek@.gmail.com wrote:
> By it, I mean a maintenance plan, by client computer, I mean client
> server, e.g. the place where the application is deployed.
> I have an installation script that restores database to a chosen
> location from backup provided with installation (the db initially has a
> lot of data so I chose that over scripting it), creates and maps logins
> etc; I wanted to add maintenance plan creation script to it but I found
> no way to script maintenance plan from Management Studio
>
I think you would be better off NOT using Maintenance Plans in this
manner. Write your own sprocs to do backups, DBCC checks, reindexing,
etc, and deploy those sprocs instead. Much easier to manage and debug
than Maintenance Plans.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I agree 100%
--
Keith Kratochvil
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:452B9819.8060707@.realsqlguy.com...
> realgeek@.gmail.com wrote:
>> By it, I mean a maintenance plan, by client computer, I mean client
>> server, e.g. the place where the application is deployed.
>> I have an installation script that restores database to a chosen
>> location from backup provided with installation (the db initially has a
>> lot of data so I chose that over scripting it), creates and maps logins
>> etc; I wanted to add maintenance plan creation script to it but I found
>> no way to script maintenance plan from Management Studio
> I think you would be better off NOT using Maintenance Plans in this
> manner. Write your own sprocs to do backups, DBCC checks, reindexing,
> etc, and deploy those sprocs instead. Much easier to manage and debug
> than Maintenance Plans.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment