DBCC CHECKDB: March 2012

Thursday, March 29, 2012

DBA guru advice - changes to production database

Hello -
I need to find out how to be able to change a production database, i.e.,
adding a column to a table that will necessitate changes to multiple stored
procedures, without shutting down the application that depends on the
database (or at least shutting it down for the least amount of time
possible). How are 24 X 7 production database changes normally made?
Can anyone explain the procedure to me and/or provide links to reading
material that explains how to do this?
Any help will be greatly appreciated. I am a programmer and these are
entirely new waters for me!
Sandy
Stuff like this is usually done through a documented process. You develop
the scripts in a dev environment and then apply them on a copy of production
in a test environment. If you are adding a NOT NULL column to a production
table, this can take a very long time, if you have many millions of rows.
You may have to XXX the column as NULL and then populate the table
iteratively. This, too, should be tested on a copy of prod first.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:19C65DEA-BF61-4B4D-88D9-67BA62C828A6@.microsoft.com...
Hello -
I need to find out how to be able to change a production database, i.e.,
adding a column to a table that will necessitate changes to multiple stored
procedures, without shutting down the application that depends on the
database (or at least shutting it down for the least amount of time
possible). How are 24 X 7 production database changes normally made?
Can anyone explain the procedure to me and/or provide links to reading
material that explains how to do this?
Any help will be greatly appreciated. I am a programmer and these are
entirely new waters for me!
Sandy
|||"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:19C65DEA-BF61-4B4D-88D9-67BA62C828A6@.microsoft.com...
> Hello -
> I need to find out how to be able to change a production database, i.e.,
> adding a column to a table that will necessitate changes to multiple
> stored
> procedures, without shutting down the application that depends on the
> database (or at least shutting it down for the least amount of time
> possible). How are 24 X 7 production database changes normally made?
> Can anyone explain the procedure to me and/or provide links to reading
> material that explains how to do this?
> Any help will be greatly appreciated. I am a programmer and these are
> entirely new waters for me!
> --
> Sandy
|||Thanks for your response, Tom.
Is the copy of the production database in the test environment generally on
a different server?
How do I then update the production server with the changes, after I work
with them on the test server?
I don't understand how I can run Alter Procedure and Alter Table scripts on
a 24 X 7 production server without mega problems, unless I shut down the
server for at least the time it takes for the scripts to run. Can you
clarify a little bit?
Sandy
"Tom Moreau" wrote:

> Stuff like this is usually done through a documented process. You develop
> the scripts in a dev environment and then apply them on a copy of production
> in a test environment. If you are adding a NOT NULL column to a production
> table, this can take a very long time, if you have many millions of rows.
> You may have to XXX the column as NULL and then populate the table
> iteratively. This, too, should be tested on a copy of prod first.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:19C65DEA-BF61-4B4D-88D9-67BA62C828A6@.microsoft.com...
> Hello -
> I need to find out how to be able to change a production database, i.e.,
> adding a column to a table that will necessitate changes to multiple stored
> procedures, without shutting down the application that depends on the
> database (or at least shutting it down for the least amount of time
> possible). How are 24 X 7 production database changes normally made?
> Can anyone explain the procedure to me and/or provide links to reading
> material that explains how to do this?
> Any help will be greatly appreciated. I am a programmer and these are
> entirely new waters for me!
> --
> Sandy
>
|||"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:19C65DEA-BF61-4B4D-88D9-67BA62C828A6@.microsoft.com...
> Hello -
> I need to find out how to be able to change a production database, i.e.,
> adding a column to a table that will necessitate changes to multiple
> stored
> procedures, without shutting down the application that depends on the
> database (or at least shutting it down for the least amount of time
> possible). How are 24 X 7 production database changes normally made?
"It depends".
Partly on the scale of the database, the changes to be made, and the
resources available.
Ok, that doesn't help much I know.
Adding a column:
Depends on if the column has defaults or not. If you add a column with
defaults, then you're almost certainly going to lock the table for some
amount of time you may find unacceptable.
Now, if your stored procedures and queries are written correctly, adding a
column to a table should not be an issue. In other words you don't do
"select *" any place.
Now, for the stored procs, generally I've had "luck" doing what I needed in
a batch. Worse case though, have a script that sets the database to single
user mode, executes your script and sets it back. But watch out for errors.
It can be "bad" to have 1/2 your stored procs update, but not the other 1/2.
;-)
Another option is if you have a replicated copy or log-shipped copy of the
database you can use, is move traffic there, make changes and move back.
The problem then is handling transactions that occurred in the meantime.

> Can anyone explain the procedure to me and/or provide links to reading
> material that explains how to do this?
I don't unfortunately. In my last job I did this sort of thing all the
time, but also knew the system pretty well (but still messed up a few times
;-)
Contact me if you need more advice.

> Any help will be greatly appreciated. I am a programmer and these are
> entirely new waters for me!
> --
> Sandy
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OErxvtacHHA.4984@.TK2MSFTNGP05.phx.gbl...
> Stuff like this is usually done through a documented process. You develop
> the scripts in a dev environment and then apply them on a copy of
> production
> in a test environment. If you are adding a NOT NULL column to a
> production
> table, this can take a very long time, if you have many millions of rows.
> You may have to XXX the column as NULL and then populate the table
> iteratively. This, too, should be tested on a copy of prod first.
Grr, Tom's right. I meant NOT NULL, not DEFAULT in my post.
And I'll also emphasize the point he made.. do this on a copy first if you
can.
Test out your procedure as much as possible.
And have a roll-back plan!

> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> .
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:19C65DEA-BF61-4B4D-88D9-67BA62C828A6@.microsoft.com...
> Hello -
> I need to find out how to be able to change a production database, i.e.,
> adding a column to a table that will necessitate changes to multiple
> stored
> procedures, without shutting down the application that depends on the
> database (or at least shutting it down for the least amount of time
> possible). How are 24 X 7 production database changes normally made?
> Can anyone explain the procedure to me and/or provide links to reading
> material that explains how to do this?
> Any help will be greatly appreciated. I am a programmer and these are
> entirely new waters for me!
> --
> Sandy
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Typically, you don't have a test/pre-prod database on the same physical
server. Rather, you have a separate box, of identical hardware (ideally).
This way, if your testing produces some undesirable effect, it's not
affecting production.
Whatever script you intend to run in prod - including an ALTER TABLE
script - would be run here. Once you are satisfied that it is working
properly, then run the same script in prod.
An ALTER PROC statement can be run in prod (after testing, of course). This
typically takes no time and if there is an error, the ALTER PROC fails and
you have the original proc.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:6B577153-11DD-4DB4-AA7C-3CDFCE9926A7@.microsoft.com...
Thanks for your response, Tom.
Is the copy of the production database in the test environment generally on
a different server?
How do I then update the production server with the changes, after I work
with them on the test server?
I don't understand how I can run Alter Procedure and Alter Table scripts on
a 24 X 7 production server without mega problems, unless I shut down the
server for at least the time it takes for the scripts to run. Can you
clarify a little bit?
Sandy
"Tom Moreau" wrote:

> Stuff like this is usually done through a documented process. You develop
> the scripts in a dev environment and then apply them on a copy of
> production
> in a test environment. If you are adding a NOT NULL column to a
> production
> table, this can take a very long time, if you have many millions of rows.
> You may have to XXX the column as NULL and then populate the table
> iteratively. This, too, should be tested on a copy of prod first.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:19C65DEA-BF61-4B4D-88D9-67BA62C828A6@.microsoft.com...
> Hello -
> I need to find out how to be able to change a production database, i.e.,
> adding a column to a table that will necessitate changes to multiple
> stored
> procedures, without shutting down the application that depends on the
> database (or at least shutting it down for the least amount of time
> possible). How are 24 X 7 production database changes normally made?
> Can anyone explain the procedure to me and/or provide links to reading
> material that explains how to do this?
> Any help will be greatly appreciated. I am a programmer and these are
> entirely new waters for me!
> --
> Sandy
>
|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OVRU8FbcHHA.4888@.TK2MSFTNGP02.phx.gbl...
> Typically, you don't have a test/pre-prod database on the same physical
> server. Rather, you have a separate box, of identical hardware (ideally).
> This way, if your testing produces some undesirable effect, it's not
> affecting production.
To expand upon this, we had a dev environment, a QA, and a prod. And
sometimes even setup a "staging" environment.
Dev code could be all over the place. QA typically mirrored Prod, or real
close to it. (We'd track differences).
Staging was used for major changes or ones we expected to be more difficult.
Typically we'd take a log-shipped copy of the Production environment. That
way we'd know we were dealing with up to date data AND the same amount of
data. (Dev, QA were typically far smaller data sets.)

> Whatever script you intend to run in prod - including an ALTER TABLE
> script - would be run here. Once you are satisfied that it is working
> properly, then run the same script in prod.
> An ALTER PROC statement can be run in prod (after testing, of course).
> This
> typically takes no time and if there is an error, the ALTER PROC fails and
> you have the original proc.
Ayup. Typically in my experience, the biggest problem was getting my ALTER
PROC statement to run.
Often it was blocked by 100s of calls to the existing one that had been made
before it.
We typically created a change plan.
In it we'd detail the changes to be made (and often why).
The plan to be followed.
The tests to make sure that it succeeded.
And very importantly, the "what if something goes wrong?" plan.
Sometimes that was trivial sometimes it was fairly complex.
If it was a single procedure and the "what if" was "it didn't get applied"
then we'd do nothing.
Or worse, it was applied, but we found out the new code syntactically was
correct, but was much slower than we could afford it to be, what would we do
then?
The big question really comes down to how long the alter table scripts will
run.
Another option (which does NOT work really in a replicated environment) is
create a NEW table with all the data, fields you want, and then rename the
old one and then the new one.
This can be useful in some cases, but not all.

> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> .
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:6B577153-11DD-4DB4-AA7C-3CDFCE9926A7@.microsoft.com...
> Thanks for your response, Tom.
> Is the copy of the production database in the test environment generally
> on
> a different server?
> How do I then update the production server with the changes, after I work
> with them on the test server?
> I don't understand how I can run Alter Procedure and Alter Table scripts
> on
> a 24 X 7 production server without mega problems, unless I shut down the
> server for at least the time it takes for the scripts to run. Can you
> clarify a little bit?
>
> --
> Sandy
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Thanks for responding, Greg -

>In other words you don't do "select *" any place.
What do you mean by the above?
What do you mean by: ". . . have a script that sets the database to single
user mode, executes your script and sets it back"?
Also, what is your best suggestion for a "rollback plan"?
Any help is greatly appreciated!
Sandy
"Greg D. Moore (Strider)" wrote:

> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:19C65DEA-BF61-4B4D-88D9-67BA62C828A6@.microsoft.com...
> "It depends".
> Partly on the scale of the database, the changes to be made, and the
> resources available.
> Ok, that doesn't help much I know.
> Adding a column:
> Depends on if the column has defaults or not. If you add a column with
> defaults, then you're almost certainly going to lock the table for some
> amount of time you may find unacceptable.
> Now, if your stored procedures and queries are written correctly, adding a
> column to a table should not be an issue. In other words you don't do
> "select *" any place.
> Now, for the stored procs, generally I've had "luck" doing what I needed in
> a batch. Worse case though, have a script that sets the database to single
> user mode, executes your script and sets it back. But watch out for errors.
> It can be "bad" to have 1/2 your stored procs update, but not the other 1/2.
> ;-)
>
> Another option is if you have a replicated copy or log-shipped copy of the
> database you can use, is move traffic there, make changes and move back.
> The problem then is handling transactions that occurred in the meantime.
>
> I don't unfortunately. In my last job I did this sort of thing all the
> time, but also knew the system pretty well (but still messed up a few times
> ;-)
> Contact me if you need more advice.
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
|||"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:A0393922-029D-4B8D-AAD9-D79F8547556A@.microsoft.com...
> Thanks for responding, Greg -
>
Anytime you do a select in production code, you want to explicitely provide
the columns you are selecting.
Some programmers, being lazy will say write a select as;
SELECT * FROM tablename where Foo='bar'
This is wrong on several levels:
1) It probably brings back too much data, which is slower and consumes
bandwidth, etc.
2) It assumes the order columns are returned is constant, which is
safe...99% of the time. But not 100%
3) It assumes the number of columns is fixed. So if you add a column to the
underlying table, the query now returns one more row, which the calling code
now has to deal with. If you specify columns you only need to update the
selects that need the extra column.

> What do you mean by the above?
> What do you mean by: ". . . have a script that sets the database to
> single
> user mode, executes your script and sets it back"?
ALTER DATABASE testing SET SINGLE_USER WITH ROLLBACK IMMEDIATE
<your scripts here>
ALTER DATABASE testing SET MULTI_USER
That simply assures no one else is doing anything while your scripts run.

> Also, what is your best suggestion for a "rollback plan"?
Planning :-)
Seriously, this is a fairly complex question and depends a lot on your
situation. It's not something I can answer too easily over a newsgroup.
But basically think about what can go wrong and how to mitigate the
problems.
Create a script to add your columns and update your stored procs.
Create a script to REMOVE your columns and restore your old stored procs.
Just in case.
Stuff like that.

> Any help is greatly appreciated!
> --
> Sandy
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
sql

DBA guide

Any good SQLServer DBA guides available online? Preferably
a downloadable pdf. Or online in HTML.

Thank you.Hi

The best resource is Books Online!
http://www.microsoft.com/sql/techin.../2000/books.asp

This threads may help:
http://tinyurl.com/2pn4h
http://tinyurl.com/yuebf

John
"C.O.Jones" <nospam.ple@.se> wrote in message
news:dpLBc.2436$xy4.21713054@.news-text.cableinet.net...
> Any good SQLServer DBA guides available online? Preferably
> a downloadable pdf. Or online in HTML.
> Thank you.

DBA Format

I am a developer who recently stepped in for our DBA when they (abruptly)
left and am not sure how to setup a deployment for one of our clients.
I think I could do a detach then have them attach or a backup then send them
the backup.
I would like to ask how a DBA would like to see what I am sending out.
Also, a pointer to the documentation would help.
Thanks for your help
LanceThe answer to your question depends a lot on what it actually is you're
deploying. A whole app, a database only, updates to an existing database,
...?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Lance Geeck" <lgeeck@.cox.net> wrote in message
news:N85xc.23665$aM1.8131@.fed1read02...
> I am a developer who recently stepped in for our DBA when they (abruptly)
> left and am not sure how to setup a deployment for one of our clients.
> I think I could do a detach then have them attach or a backup then send
them
> the backup.
> I would like to ask how a DBA would like to see what I am sending out.
> Also, a pointer to the documentation would help.
> Thanks for your help
> Lance
>|||Just a database. New installation.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:u$0ZJfNTEHA.3608@.TK2MSFTNGP11.phx.gbl...
> The answer to your question depends a lot on what it actually is you're
> deploying. A whole app, a database only, updates to an existing database,
> ...?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Lance Geeck" <lgeeck@.cox.net> wrote in message
> news:N85xc.23665$aM1.8131@.fed1read02...
> > I am a developer who recently stepped in for our DBA when they
(abruptly)
> > left and am not sure how to setup a deployment for one of our clients.
> >
> > I think I could do a detach then have them attach or a backup then send
> them
> > the backup.
> >
> > I would like to ask how a DBA would like to see what I am sending out.
> >
> > Also, a pointer to the documentation would help.
> >
> > Thanks for your help
> > Lance
> >
> >
>|||You could do a backup and send them the .BAK file, then they could restore
it. However, this has some dependencies, e.g. data folder locations, etc.
Simplest might be to detach the database, send the MDF/LDF file(s), then
re-attach.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Lance Geeck" <lgeeck@.cox.net> wrote in message
news:6k5xc.23713$aM1.9744@.fed1read02...
> Just a database. New installation.
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:u$0ZJfNTEHA.3608@.TK2MSFTNGP11.phx.gbl...
> > The answer to your question depends a lot on what it actually is you're
> > deploying. A whole app, a database only, updates to an existing
database,
> > ...?
> >
> > --
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
> >
> >
> > "Lance Geeck" <lgeeck@.cox.net> wrote in message
> > news:N85xc.23665$aM1.8131@.fed1read02...
> > > I am a developer who recently stepped in for our DBA when they
> (abruptly)
> > > left and am not sure how to setup a deployment for one of our clients.
> > >
> > > I think I could do a detach then have them attach or a backup then
send
> > them
> > > the backup.
> > >
> > > I would like to ask how a DBA would like to see what I am sending out.
> > >
> > > Also, a pointer to the documentation would help.
> > >
> > > Thanks for your help
> > > Lance
> > >
> > >
> >
> >
>|||Another thing you might consider doing is scripting out the database and the
objects it contains. You can do this by right-clicking a database in
Enterprise Manager, all tasks, generate SQL script, and follow the wizard.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Lance Geeck" <lgeeck@.cox.net> wrote in message
news:6k5xc.23713$aM1.9744@.fed1read02...
> Just a database. New installation.|||Wouldn't the ATTACH be a problem if it is in a different folder location?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OFs%23bjNTEHA.3700@.TK2MSFTNGP09.phx.gbl...
> You could do a backup and send them the .BAK file, then they could restore
> it. However, this has some dependencies, e.g. data folder locations, etc.
> Simplest might be to detach the database, send the MDF/LDF file(s), then
> re-attach.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Lance Geeck" <lgeeck@.cox.net> wrote in message
> news:6k5xc.23713$aM1.9744@.fed1read02...
> > Just a database. New installation.
> >
> > "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> > news:u$0ZJfNTEHA.3608@.TK2MSFTNGP11.phx.gbl...
> > > The answer to your question depends a lot on what it actually is
you're
> > > deploying. A whole app, a database only, updates to an existing
> database,
> > > ...?
> > >
> > > --
> > > http://www.aspfaq.com/
> > > (Reverse address to reply.)
> > >
> > >
> > >
> > >
> > > "Lance Geeck" <lgeeck@.cox.net> wrote in message
> > > news:N85xc.23665$aM1.8131@.fed1read02...
> > > > I am a developer who recently stepped in for our DBA when they
> > (abruptly)
> > > > left and am not sure how to setup a deployment for one of our
clients.
> > > >
> > > > I think I could do a detach then have them attach or a backup then
> send
> > > them
> > > > the backup.
> > > >
> > > > I would like to ask how a DBA would like to see what I am sending
out.
> > > >
> > > > Also, a pointer to the documentation would help.
> > > >
> > > > Thanks for your help
> > > > Lance
> > > >
> > > >
> > >
> > >
> >
> >
>|||Doesn't this miss the records in the database? I have about 1/2 million
rows I need to include in what I send them.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:uBSjakNTEHA.2372@.TK2MSFTNGP11.phx.gbl...
> Another thing you might consider doing is scripting out the database and
the
> objects it contains. You can do this by right-clicking a database in
> Enterprise Manager, all tasks, generate SQL script, and follow the wizard.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Lance Geeck" <lgeeck@.cox.net> wrote in message
> news:6k5xc.23713$aM1.9744@.fed1read02...
> > Just a database. New installation.
>|||you need to detach\reattach or Restore a backup using the "WITH MOVE" Option
if you need more info let me know
cheers,
Greg Jackson
PDX, Oregon|||Lance,
My preferred approach would be to backup/restore, but as Aaron said
there are dependencies and you will likely orphan any users in the
database. This can however be fixed by adding new logins to the
destination box and mapping orphaned users to the logins using
sp_change_users_login.
You will likely also need the WITH MOVE option of the RESTORE DATABASE
statement. You might also want to change the database owner to something
meaningful on the destination, I would recommend sa. Use
sp_changedbowner to do this.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Lance Geeck wrote:
> I am a developer who recently stepped in for our DBA when they (abruptly)
> left and am not sure how to setup a deployment for one of our clients.
> I think I could do a detach then have them attach or a backup then send them
> the backup.
> I would like to ask how a DBA would like to see what I am sending out.
> Also, a pointer to the documentation would help.
> Thanks for your help
> Lance
>

DBA Format

DBA for multiple servers

Is anybody has experience to DBA more than 100 SQl Servers at a time?
If so what are the main startegy and main challenges you had? what is
your best practice in terms of day to day admin and backup and
recovery?soalvajavab1@.yahoo.com wrote:
> Is anybody has experience to DBA more than 100 SQl Servers at a time?
> If so what are the main startegy and main challenges you had? what is
> your best practice in terms of day to day admin and backup and
> recovery?
>
I don't think that tasks are that much different when you have 5 or 100
SQL servers, so could you be a bit more specific in what you'd like to
know? From my point of view it's quite important that the backup jobs
works. I've written my own scripts that automatically backups up all
databases on a SQL server, so once these has been scheduled they just
notify me when they fails. You'd then also like to monitor the free
space on your disks on the server, but for that the company most likely
has a monitoring tool for that.
In terms of what more you'd like to do is a matter of personal
preference and company policy. E.g. I know that many people don't like
to have their databases set to autogrow, but I normally do that for most
databases. Currently I'm looking after approx. 1000 SQL server databases
and for me it works fine to have them set to autogrow. I've then created
a stored proc that runs every night on most of the servers and collect a
number of data for each database. This tells me when there has been
created new databases, when a database has been deleted, file growth,
backup file growth, recovery mode change etc. I then get an email every
morning with the changes.
Apart from the above, there are a number of database monitoring tools
available on the market. I haven't actually used any of them yet but I
think they can do some of what I've done myself (..and of course a lot
more...). Maybe somebody else has some experience on this?
Bottomline is that what you need to look for isn't a standard answer,
but pretty much depends on the setup and your company/company policy. I
also think that the DBA role can be quite different from one company to
another.
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||I think that with that number-- you'll just need to follow these guidelines:
a) use profiler on all machines
b) run index tuning wizard on your busiest databases
c) build poormon enterprise level performan aggregation tools
d) encourage people to use Reporting Services and Analysis Services in order
to leverage this mountain of data
<soalvajavab1@.yahoo.com> wrote in message
news:1177946795.389483.51580@.y80g2000hsf.googlegroups.com...
> Is anybody has experience to DBA more than 100 SQl Servers at a time?
> If so what are the main startegy and main challenges you had? what is
> your best practice in terms of day to day admin and backup and
> recovery?
>sql

DBA for multiple servers

Is anybody has experience to DBA more than 100 SQl Servers at a time?
If so what are the main startegy and main challenges you had? what is
your best practice in terms of day to day admin and backup and
recovery?soalvajavab1@.yahoo.com wrote:
> Is anybody has experience to DBA more than 100 SQl Servers at a time?
> If so what are the main startegy and main challenges you had? what is
> your best practice in terms of day to day admin and backup and
> recovery?
>
I don't think that tasks are that much different when you have 5 or 100
SQL servers, so could you be a bit more specific in what you'd like to
know? From my point of view it's quite important that the backup jobs
works. I've written my own scripts that automatically backups up all
databases on a SQL server, so once these has been scheduled they just
notify me when they fails. You'd then also like to monitor the free
space on your disks on the server, but for that the company most likely
has a monitoring tool for that.
In terms of what more you'd like to do is a matter of personal
preference and company policy. E.g. I know that many people don't like
to have their databases set to autogrow, but I normally do that for most
databases. Currently I'm looking after approx. 1000 SQL server databases
and for me it works fine to have them set to autogrow. I've then created
a stored proc that runs every night on most of the servers and collect a
number of data for each database. This tells me when there has been
created new databases, when a database has been deleted, file growth,
backup file growth, recovery mode change etc. I then get an email every
morning with the changes.
Apart from the above, there are a number of database monitoring tools
available on the market. I haven't actually used any of them yet but I
think they can do some of what I've done myself (..and of course a lot
more...). Maybe somebody else has some experience on this?
Bottomline is that what you need to look for isn't a standard answer,
but pretty much depends on the setup and your company/company policy. I
also think that the DBA role can be quite different from one company to
another.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||I think that with that number-- you'll just need to follow these guidelines:
a) use profiler on all machines
b) run index tuning wizard on your busiest databases
c) build poormon enterprise level performan aggregation tools
d) encourage people to use Reporting Services and Analysis Services in order
to leverage this mountain of data
<soalvajavab1@.yahoo.com> wrote in message
news:1177946795.389483.51580@.y80g2000hsf.googlegroups.com...
> Is anybody has experience to DBA more than 100 SQl Servers at a time?
> If so what are the main startegy and main challenges you had? what is
> your best practice in terms of day to day admin and backup and
> recovery?
>

DBA for multiple servers

Is anybody has experience to DBA more than 100 SQl Servers at a time?
If so what are the main startegy and main challenges you had? what is
your best practice in terms of day to day admin and backup and
recovery?
soalvajavab1@.yahoo.com wrote:
> Is anybody has experience to DBA more than 100 SQl Servers at a time?
> If so what are the main startegy and main challenges you had? what is
> your best practice in terms of day to day admin and backup and
> recovery?
>
I don't think that tasks are that much different when you have 5 or 100
SQL servers, so could you be a bit more specific in what you'd like to
know? From my point of view it's quite important that the backup jobs
works. I've written my own scripts that automatically backups up all
databases on a SQL server, so once these has been scheduled they just
notify me when they fails. You'd then also like to monitor the free
space on your disks on the server, but for that the company most likely
has a monitoring tool for that.
In terms of what more you'd like to do is a matter of personal
preference and company policy. E.g. I know that many people don't like
to have their databases set to autogrow, but I normally do that for most
databases. Currently I'm looking after approx. 1000 SQL server databases
and for me it works fine to have them set to autogrow. I've then created
a stored proc that runs every night on most of the servers and collect a
number of data for each database. This tells me when there has been
created new databases, when a database has been deleted, file growth,
backup file growth, recovery mode change etc. I then get an email every
morning with the changes.
Apart from the above, there are a number of database monitoring tools
available on the market. I haven't actually used any of them yet but I
think they can do some of what I've done myself (..and of course a lot
more...). Maybe somebody else has some experience on this?
Bottomline is that what you need to look for isn't a standard answer,
but pretty much depends on the setup and your company/company policy. I
also think that the DBA role can be quite different from one company to
another.
Regards
Steen Schlter Persson
Database Administrator / System Administrator
|||I think that with that number-- you'll just need to follow these guidelines:
a) use profiler on all machines
b) run index tuning wizard on your busiest databases
c) build poormon enterprise level performan aggregation tools
d) encourage people to use Reporting Services and Analysis Services in order
to leverage this mountain of data
<soalvajavab1@.yahoo.com> wrote in message
news:1177946795.389483.51580@.y80g2000hsf.googlegro ups.com...
> Is anybody has experience to DBA more than 100 SQl Servers at a time?
> If so what are the main startegy and main challenges you had? what is
> your best practice in terms of day to day admin and backup and
> recovery?
>

DBA First Date

Hi, I am going to start as the only DBA in a company, very nervous, since
there is no peer at the company and no transition from the job, could someone
told me when I start, what would be the initial steps to take for starting? I
read some article about daily activities on the job, since i used to be a
development dba, now into a produciton dba with 15-20 servers, how to get to
practice myself for this new job requirements?
For starters, try to keep in mind the most important things to the
organization:
-Backups. Make sure all your important databases are being backed up
regularly, and test the restores. Monitor and get very familiar with them.
-Maintenance plans. Make sure that appropriate maintenance windows are
taken for reindexing, updating stats, integrity checks etc.
-Setup perfmon counters that you can watch in real time from your
desktop machine. That way you'll often be aware of performance issues
before you get a phone call.
-Make sure your SQL boxes are regularly patched, ideally in a test
environment first.
-Make sure all your servers are on the latest service packs (assuming
you don't have any applications that would break with a new SP).
-Pick up an administration book to get familiar with all of the regular
routines a DBA has.
HTH,
Rubens
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
> Hi, I am going to start as the only DBA in a company, very nervous, since
> there is no peer at the company and no transition from the job, could
> someone
> told me when I start, what would be the initial steps to take for
> starting? I
> read some article about daily activities on the job, since i used to be a
> development dba, now into a produciton dba with 15-20 servers, how to get
> to
> practice myself for this new job requirements?
|||This role also require to hand reporting service, so anyone has
experience on handling both? thank you
On Mar 3, 5:25Xpm, "Rubens" <rubensr...@.hotmail.com> wrote:
> For starters, try to keep in mind the most important things to the
> organization:
> X X -Backups. XMake sure all your important databases are being backed up
> regularly, and test the restores. XMonitor and get very familiar with them.
> X X -Maintenance plans. XMake sure that appropriate maintenance windows are
> taken for reindexing, updating stats, integrity checks etc.
> X X -Setup perfmon counters that you can watch in real time from your
> desktop machine. XThat way you'll often be aware of performance issues
> before you get a phone call.
> X X -Make sure your SQL boxes are regularly patched, ideally in a test
> environment first.
> X X -Make sure all your servers are on the latest service packs (assuming
> you don't have any applications that would break with a new SP).
> X X -Pick up an administration book to get familiar with all of the regular
> routines a DBA has.
> HTH,
> Rubens
> "tulip" <tu...@.discussions.microsoft.com> wrote in message
> news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
>
>
> - Show quoted text -
|||when Setup perfmon counters that you can watch in real time from your
desktop machine. If there are about 20 servers, how do you monitor all of
them from my desktop? thank you
"Rubens" wrote:

> For starters, try to keep in mind the most important things to the
> organization:
> -Backups. Make sure all your important databases are being backed up
> regularly, and test the restores. Monitor and get very familiar with them.
> -Maintenance plans. Make sure that appropriate maintenance windows are
> taken for reindexing, updating stats, integrity checks etc.
> -Setup perfmon counters that you can watch in real time from your
> desktop machine. That way you'll often be aware of performance issues
> before you get a phone call.
> -Make sure your SQL boxes are regularly patched, ideally in a test
> environment first.
> -Make sure all your servers are on the latest service packs (assuming
> you don't have any applications that would break with a new SP).
> -Pick up an administration book to get familiar with all of the regular
> routines a DBA has.
> HTH,
> Rubens
> "tulip" <tulip@.discussions.microsoft.com> wrote in message
> news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
>
|||That's a bit of a tough one. I am lucky enough to have an additional
desktop machine aside from my laptop with a decent sized monitor. Even
then, I can only effectively see about 8 servers at a time. That being
said, you could still all add the servers (in blocks of 8), you'd just need
to scroll through them once in a while to see how they are doing. And if
someone called you with a performance issue, you could quickly flip over to
that particular one...
Rubens
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:7314E503-7223-47CD-B73F-19F6D3907216@.microsoft.com...[vbcol=seagreen]
> when Setup perfmon counters that you can watch in real time from your
> desktop machine. If there are about 20 servers, how do you monitor all of
> them from my desktop? thank you
> "Rubens" wrote:
|||Hi
[url]http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1 [/url]
--administaiting best practices
http://vyaskn.tripod.com/sql_server_security_best_practices.htm --security
best practices
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
> Hi, I am going to start as the only DBA in a company, very nervous, since
> there is no peer at the company and no transition from the job, could
> someone
> told me when I start, what would be the initial steps to take for
> starting? I
> read some article about daily activities on the job, since i used to be a
> development dba, now into a produciton dba with 15-20 servers, how to get
> to
> practice myself for this new job requirements?

DBA First Date

Hi, I am going to start as the only DBA in a company, very nervous, since
there is no peer at the company and no transition from the job, could someone
told me when I start, what would be the initial steps to take for starting? I
read some article about daily activities on the job, since i used to be a
development dba, now into a produciton dba with 15-20 servers, how to get to
practice myself for this new job requirements?For starters, try to keep in mind the most important things to the
organization:
-Backups. Make sure all your important databases are being backed up
regularly, and test the restores. Monitor and get very familiar with them.
-Maintenance plans. Make sure that appropriate maintenance windows are
taken for reindexing, updating stats, integrity checks etc.
-Setup perfmon counters that you can watch in real time from your
desktop machine. That way you'll often be aware of performance issues
before you get a phone call.
-Make sure your SQL boxes are regularly patched, ideally in a test
environment first.
-Make sure all your servers are on the latest service packs (assuming
you don't have any applications that would break with a new SP).
-Pick up an administration book to get familiar with all of the regular
routines a DBA has.
HTH,
Rubens
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
> Hi, I am going to start as the only DBA in a company, very nervous, since
> there is no peer at the company and no transition from the job, could
> someone
> told me when I start, what would be the initial steps to take for
> starting? I
> read some article about daily activities on the job, since i used to be a
> development dba, now into a produciton dba with 15-20 servers, how to get
> to
> practice myself for this new job requirements?|||This role also require to hand reporting service, so anyone has
experience on handling both? thank you
On Mar 3, 5:25=A0pm, "Rubens" <rubensr...@.hotmail.com> wrote:
> For starters, try to keep in mind the most important things to the
> organization:
> =A0 =A0 -Backups. =A0Make sure all your important databases are being back=ed up
> regularly, and test the restores. =A0Monitor and get very familiar with th=em.
> =A0 =A0 -Maintenance plans. =A0Make sure that appropriate maintenance wind=ows are
> taken for reindexing, updating stats, integrity checks etc.
> =A0 =A0 -Setup perfmon counters that you can watch in real time from your
> desktop machine. =A0That way you'll often be aware of performance issues
> before you get a phone call.
> =A0 =A0 -Make sure your SQL boxes are regularly patched, ideally in a test=
> environment first.
> =A0 =A0 -Make sure all your servers are on the latest service packs (assum=ing
> you don't have any applications that would break with a new SP).
> =A0 =A0 -Pick up an administration book to get familiar with all of the re=gular
> routines a DBA has.
> HTH,
> Rubens
> "tulip" <tu...@.discussions.microsoft.com> wrote in message
> news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
>
> > Hi, I am going to start as the only DBA in a company, very nervous, sinc=e
> > there is no peer at the company and no transition from the job, could
> > someone
> > told me when I start, what would be the initial steps to take for
> > starting? I
> > read some article about daily activities on the job, since i used to be =a
> > development dba, now into a produciton dba with 15-20 servers, how to ge=t
> > to
> > practice myself for this new job requirements... Hide quoted text -
> - Show quoted text -|||when Setup perfmon counters that you can watch in real time from your
desktop machine. If there are about 20 servers, how do you monitor all of
them from my desktop? thank you
"Rubens" wrote:
> For starters, try to keep in mind the most important things to the
> organization:
> -Backups. Make sure all your important databases are being backed up
> regularly, and test the restores. Monitor and get very familiar with them.
> -Maintenance plans. Make sure that appropriate maintenance windows are
> taken for reindexing, updating stats, integrity checks etc.
> -Setup perfmon counters that you can watch in real time from your
> desktop machine. That way you'll often be aware of performance issues
> before you get a phone call.
> -Make sure your SQL boxes are regularly patched, ideally in a test
> environment first.
> -Make sure all your servers are on the latest service packs (assuming
> you don't have any applications that would break with a new SP).
> -Pick up an administration book to get familiar with all of the regular
> routines a DBA has.
> HTH,
> Rubens
> "tulip" <tulip@.discussions.microsoft.com> wrote in message
> news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
> > Hi, I am going to start as the only DBA in a company, very nervous, since
> > there is no peer at the company and no transition from the job, could
> > someone
> > told me when I start, what would be the initial steps to take for
> > starting? I
> > read some article about daily activities on the job, since i used to be a
> > development dba, now into a produciton dba with 15-20 servers, how to get
> > to
> > practice myself for this new job requirements?
>|||That's a bit of a tough one. I am lucky enough to have an additional
desktop machine aside from my laptop with a decent sized monitor. Even
then, I can only effectively see about 8 servers at a time. That being
said, you could still all add the servers (in blocks of 8), you'd just need
to scroll through them once in a while to see how they are doing. And if
someone called you with a performance issue, you could quickly flip over to
that particular one...
Rubens
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:7314E503-7223-47CD-B73F-19F6D3907216@.microsoft.com...
> when Setup perfmon counters that you can watch in real time from your
> desktop machine. If there are about 20 servers, how do you monitor all of
> them from my desktop? thank you
> "Rubens" wrote:
>> For starters, try to keep in mind the most important things to the
>> organization:
>> -Backups. Make sure all your important databases are being backed up
>> regularly, and test the restores. Monitor and get very familiar with
>> them.
>> -Maintenance plans. Make sure that appropriate maintenance windows
>> are
>> taken for reindexing, updating stats, integrity checks etc.
>> -Setup perfmon counters that you can watch in real time from your
>> desktop machine. That way you'll often be aware of performance issues
>> before you get a phone call.
>> -Make sure your SQL boxes are regularly patched, ideally in a test
>> environment first.
>> -Make sure all your servers are on the latest service packs (assuming
>> you don't have any applications that would break with a new SP).
>> -Pick up an administration book to get familiar with all of the
>> regular
>> routines a DBA has.
>> HTH,
>> Rubens
>> "tulip" <tulip@.discussions.microsoft.com> wrote in message
>> news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
>> > Hi, I am going to start as the only DBA in a company, very nervous,
>> > since
>> > there is no peer at the company and no transition from the job, could
>> > someone
>> > told me when I start, what would be the initial steps to take for
>> > starting? I
>> > read some article about daily activities on the job, since i used to be
>> > a
>> > development dba, now into a produciton dba with 15-20 servers, how to
>> > get
>> > to
>> > practice myself for this new job requirements?
>>|||Hi
http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1
--administaiting best practices
http://vyaskn.tripod.com/sql_server_security_best_practices.htm --security
best practices
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:1AC1B73B-B186-4E55-A8BB-178FCE0BA8B6@.microsoft.com...
> Hi, I am going to start as the only DBA in a company, very nervous, since
> there is no peer at the company and no transition from the job, could
> someone
> told me when I start, what would be the initial steps to take for
> starting? I
> read some article about daily activities on the job, since i used to be a
> development dba, now into a produciton dba with 15-20 servers, how to get
> to
> practice myself for this new job requirements?

DBA dissappointed in sql server 2005

I've been looking at the beta2 release of yukon and I am beginning to be
dissappointed in the product from a DBA viewpoint. I realize that a lot of
improvements have been made in the programmers side of things, but I still
have to manage the sql servers and I do not see any improvements in my day to
day, week to week regular management task I have to perform. For instance:
1.) i do not see any option to tell a backup to compress the backup file as
it backsup a database. this would be a highly desired feature.
2.) there is no way to temporarily disable logins without changing the
persons password which is not desired.
3.) using dts to export a table from a "development" database to a "testing"
or "production" database will only move the table definition and data, but
not the underlying indexes or constraints.
4.) using dts to export a view will only create a table on the recieving
end, not a view.
5.) I have 75 seperate sql server boxes, some with multiple instance, all
with many many databases and scores of jobs. I need something that can show
me easily the status of all jobs across all the servers without manually
connecting to each individual sql server instance and then expanding down to
jobs. I want to select jobs and all jobs across all instance are shown sorted
by whatever I choose. Same way i want to select current processes and see the
same things.
the list goes on...
mayby others can enlighten me and point out some real benefits in the new
sql server from a dba point of view.Charles,
I think you'll have much better response in the SQL Server 2005 newsgroups
... please re-post there:
http://communities.microsoft.com/newsgroups/ICP/sqlserver2005/us/welcomePage.htm
"Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in message
news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> I've been looking at the beta2 release of yukon and I am beginning to be
> dissappointed in the product from a DBA viewpoint. I realize that a lot of
> improvements have been made in the programmers side of things, but I still
> have to manage the sql servers and I do not see any improvements in my day
to
> day, week to week regular management task I have to perform. For instance:
> 1.) i do not see any option to tell a backup to compress the backup file
as
> it backsup a database. this would be a highly desired feature.
> 2.) there is no way to temporarily disable logins without changing the
> persons password which is not desired.
> 3.) using dts to export a table from a "development" database to a
"testing"
> or "production" database will only move the table definition and data, but
> not the underlying indexes or constraints.
> 4.) using dts to export a view will only create a table on the recieving
> end, not a view.
> 5.) I have 75 seperate sql server boxes, some with multiple instance, all
> with many many databases and scores of jobs. I need something that can
show
> me easily the status of all jobs across all the servers without manually
> connecting to each individual sql server instance and then expanding down
to
> jobs. I want to select jobs and all jobs across all instance are shown
sorted
> by whatever I choose. Same way i want to select current processes and see
the
> same things.
> the list goes on...
> mayby others can enlighten me and point out some real benefits in the new
> sql server from a dba point of view.|||http://www.aspfaq.com/sql2005/show.asp?id=1
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in message
news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> I've been looking at the beta2 release of yukon and I am beginning to be
> dissappointed in the product from a DBA viewpoint. I realize that a lot of
> improvements have been made in the programmers side of things, but I still
> have to manage the sql servers and I do not see any improvements in my day
to
> day, week to week regular management task I have to perform. For instance:
> 1.) i do not see any option to tell a backup to compress the backup file
as
> it backsup a database. this would be a highly desired feature.
> 2.) there is no way to temporarily disable logins without changing the
> persons password which is not desired.
> 3.) using dts to export a table from a "development" database to a
"testing"
> or "production" database will only move the table definition and data, but
> not the underlying indexes or constraints.
> 4.) using dts to export a view will only create a table on the recieving
> end, not a view.
> 5.) I have 75 seperate sql server boxes, some with multiple instance, all
> with many many databases and scores of jobs. I need something that can
show
> me easily the status of all jobs across all the servers without manually
> connecting to each individual sql server instance and then expanding down
to
> jobs. I want to select jobs and all jobs across all instance are shown
sorted
> by whatever I choose. Same way i want to select current processes and see
the
> same things.
> the list goes on...
> mayby others can enlighten me and point out some real benefits in the new
> sql server from a dba point of view.|||You must have been disappointed in SQL Server 2000 as well then. 2, 3, 4 and
5 are already available in SQL Server 2000.
--
Jacco Schalkwijk
SQL Server MVP
"Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in message
news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> I've been looking at the beta2 release of yukon and I am beginning to be
> dissappointed in the product from a DBA viewpoint. I realize that a lot of
> improvements have been made in the programmers side of things, but I still
> have to manage the sql servers and I do not see any improvements in my day
> to
> day, week to week regular management task I have to perform. For instance:
> 1.) i do not see any option to tell a backup to compress the backup file
> as
> it backsup a database. this would be a highly desired feature.
> 2.) there is no way to temporarily disable logins without changing the
> persons password which is not desired.
> 3.) using dts to export a table from a "development" database to a
> "testing"
> or "production" database will only move the table definition and data, but
> not the underlying indexes or constraints.
> 4.) using dts to export a view will only create a table on the recieving
> end, not a view.
> 5.) I have 75 seperate sql server boxes, some with multiple instance, all
> with many many databases and scores of jobs. I need something that can
> show
> me easily the status of all jobs across all the servers without manually
> connecting to each individual sql server instance and then expanding down
> to
> jobs. I want to select jobs and all jobs across all instance are shown
> sorted
> by whatever I choose. Same way i want to select current processes and see
> the
> same things.
> the list goes on...
> mayby others can enlighten me and point out some real benefits in the new
> sql server from a dba point of view.|||Hi
Send your resqlwish@.microsoft.com
Yes, some of those features are nice, but
"Charles Pritt" wrote:
> I've been looking at the beta2 release of yukon and I am beginning to be
> dissappointed in the product from a DBA viewpoint. I realize that a lot of
> improvements have been made in the programmers side of things, but I still
> have to manage the sql servers and I do not see any improvements in my day to
> day, week to week regular management task I have to perform. For instance:
> 1.) i do not see any option to tell a backup to compress the backup file as
> it backsup a database. this would be a highly desired feature.
> 2.) there is no way to temporarily disable logins without changing the
> persons password which is not desired.
> 3.) using dts to export a table from a "development" database to a "testing"
> or "production" database will only move the table definition and data, but
> not the underlying indexes or constraints.
> 4.) using dts to export a view will only create a table on the recieving
> end, not a view.
> 5.) I have 75 seperate sql server boxes, some with multiple instance, all
> with many many databases and scores of jobs. I need something that can show
> me easily the status of all jobs across all the servers without manually
> connecting to each individual sql server instance and then expanding down to
> jobs. I want to select jobs and all jobs across all instance are shown sorted
> by whatever I choose. Same way i want to select current processes and see the
> same things.
> the list goes on...
> mayby others can enlighten me and point out some real benefits in the new
> sql server from a dba point of view.|||Charles,
Sounds as though you should have been at PASS 2004 last week. You could have
raised your concerns directly with MS managers there.
Chris Wood
Alberta Department of Energy
CANADA
"Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in message
news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> I've been looking at the beta2 release of yukon and I am beginning to be
> dissappointed in the product from a DBA viewpoint. I realize that a lot of
> improvements have been made in the programmers side of things, but I still
> have to manage the sql servers and I do not see any improvements in my day
to
> day, week to week regular management task I have to perform. For instance:
> 1.) i do not see any option to tell a backup to compress the backup file
as
> it backsup a database. this would be a highly desired feature.
> 2.) there is no way to temporarily disable logins without changing the
> persons password which is not desired.
> 3.) using dts to export a table from a "development" database to a
"testing"
> or "production" database will only move the table definition and data, but
> not the underlying indexes or constraints.
> 4.) using dts to export a view will only create a table on the recieving
> end, not a view.
> 5.) I have 75 seperate sql server boxes, some with multiple instance, all
> with many many databases and scores of jobs. I need something that can
show
> me easily the status of all jobs across all the servers without manually
> connecting to each individual sql server instance and then expanding down
to
> jobs. I want to select jobs and all jobs across all instance are shown
sorted
> by whatever I choose. Same way i want to select current processes and see
the
> same things.
> the list goes on...
> mayby others can enlighten me and point out some real benefits in the new
> sql server from a dba point of view.|||Please explain how number 2) already exist in current product.
For number 3 and 4) if you are referring to having the dts wizard export an
object and then selecting a specific table, I have not been able in the last
4 years to get this to work reliably. Mainly because there will always be
some user that has access to that object on the source side that doesn't
exist on the destination side and it fials because the specific users does
not exists on the destination. Also, I did not see the option to move a
"object" in the 2005 export wizard.
for number 5) if you are referring to having to register each individual sql
server and then clicking on each of the 75 sql servers one at a time and then
going down to mangement and then sql server agent and then jobs looking at
the list and then going to the next sql server agent and clicking on it and
then going to management. and so on... I agree with you ... they have it.
that is the way i do it now. I am referring to clicking on a icon that says
sql server and then clicking on a icon that says jobs and it list every sql
server and every job and its status. two clicks. a couple minutes to see all
jobs.
no i have not been dissappointed in sql server 2000, it is a far cry from
sql server 6.5 and sql server 7.0 but there are still things lacking. This is
my job. it all i do everyday, 7 days a week. manage more than 75 sql server,
jobs, users, backups, and quite a few sql server clusters. I'm just looking
for some improvement in the day to day task I perform.
"Jacco Schalkwijk" wrote:
> You must have been disappointed in SQL Server 2000 as well then. 2, 3, 4 and
> 5 are already available in SQL Server 2000.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in message
> news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> > I've been looking at the beta2 release of yukon and I am beginning to be
> > dissappointed in the product from a DBA viewpoint. I realize that a lot of
> > improvements have been made in the programmers side of things, but I still
> > have to manage the sql servers and I do not see any improvements in my day
> > to
> > day, week to week regular management task I have to perform. For instance:
> >
> > 1.) i do not see any option to tell a backup to compress the backup file
> > as
> > it backsup a database. this would be a highly desired feature.
> >
> > 2.) there is no way to temporarily disable logins without changing the
> > persons password which is not desired.
> >
> > 3.) using dts to export a table from a "development" database to a
> > "testing"
> > or "production" database will only move the table definition and data, but
> > not the underlying indexes or constraints.
> >
> > 4.) using dts to export a view will only create a table on the recieving
> > end, not a view.
> >
> > 5.) I have 75 seperate sql server boxes, some with multiple instance, all
> > with many many databases and scores of jobs. I need something that can
> > show
> > me easily the status of all jobs across all the servers without manually
> > connecting to each individual sql server instance and then expanding down
> > to
> > jobs. I want to select jobs and all jobs across all instance are shown
> > sorted
> > by whatever I choose. Same way i want to select current processes and see
> > the
> > same things.
> >
> > the list goes on...
> >
> > mayby others can enlighten me and point out some real benefits in the new
> > sql server from a dba point of view.
>
>|||I thought that the address was sqlwish@.microsoft.com
Keith
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:9E19AE0D-65B3-4006-BE6F-1F533EED69F4@.microsoft.com...
> Hi
> Send your resqlwish@.microsoft.com
> Yes, some of those features are nice, but
> "Charles Pritt" wrote:
> > I've been looking at the beta2 release of yukon and I am beginning to be
> > dissappointed in the product from a DBA viewpoint. I realize that a lot
of
> > improvements have been made in the programmers side of things, but I
still
> > have to manage the sql servers and I do not see any improvements in my
day to
> > day, week to week regular management task I have to perform. For
instance:
> >
> > 1.) i do not see any option to tell a backup to compress the backup file
as
> > it backsup a database. this would be a highly desired feature.
> >
> > 2.) there is no way to temporarily disable logins without changing the
> > persons password which is not desired.
> >
> > 3.) using dts to export a table from a "development" database to a
"testing"
> > or "production" database will only move the table definition and data,
but
> > not the underlying indexes or constraints.
> >
> > 4.) using dts to export a view will only create a table on the recieving
> > end, not a view.
> >
> > 5.) I have 75 seperate sql server boxes, some with multiple instance,
all
> > with many many databases and scores of jobs. I need something that can
show
> > me easily the status of all jobs across all the servers without manually
> > connecting to each individual sql server instance and then expanding
down to
> > jobs. I want to select jobs and all jobs across all instance are shown
sorted
> > by whatever I choose. Same way i want to select current processes and
see the
> > same things.
> >
> > the list goes on...
> >
> > mayby others can enlighten me and point out some real benefits in the
new
> > sql server from a dba point of view.|||I wish I could have been there, but like a lot of companies, my company
doesn't have money for that sort of thing. And I am the only sql server dba
so it is difficult to get away.
not meaning to be antogonistic, just wondering if everyday management task
that comprises 90% to 95% of my workload has improved.
thanks for the reply.
"Chris Wood" wrote:
> Charles,
> Sounds as though you should have been at PASS 2004 last week. You could have
> raised your concerns directly with MS managers there.
> Chris Wood
> Alberta Department of Energy
> CANADA
> "Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in message
> news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> > I've been looking at the beta2 release of yukon and I am beginning to be
> > dissappointed in the product from a DBA viewpoint. I realize that a lot of
> > improvements have been made in the programmers side of things, but I still
> > have to manage the sql servers and I do not see any improvements in my day
> to
> > day, week to week regular management task I have to perform. For instance:
> >
> > 1.) i do not see any option to tell a backup to compress the backup file
> as
> > it backsup a database. this would be a highly desired feature.
> >
> > 2.) there is no way to temporarily disable logins without changing the
> > persons password which is not desired.
> >
> > 3.) using dts to export a table from a "development" database to a
> "testing"
> > or "production" database will only move the table definition and data, but
> > not the underlying indexes or constraints.
> >
> > 4.) using dts to export a view will only create a table on the recieving
> > end, not a view.
> >
> > 5.) I have 75 seperate sql server boxes, some with multiple instance, all
> > with many many databases and scores of jobs. I need something that can
> show
> > me easily the status of all jobs across all the servers without manually
> > connecting to each individual sql server instance and then expanding down
> to
> > jobs. I want to select jobs and all jobs across all instance are shown
> sorted
> > by whatever I choose. Same way i want to select current processes and see
> the
> > same things.
> >
> > the list goes on...
> >
> > mayby others can enlighten me and point out some real benefits in the new
> > sql server from a dba point of view.
>
>|||There are other tools to manager db servers on an enterprise basis.
DBArtisan is one (note - I have no actual experience with this tool but it
was used by a fomer employer). My guess is that there are others.
"Charles Pritt" <CharlesPritt@.discussions.microsoft.com> wrote in message
news:DF22EB88-A335-4A9C-A1A4-5B548E77622E@.microsoft.com...
> I wish I could have been there, but like a lot of companies, my company
> doesn't have money for that sort of thing. And I am the only sql server
dba
> so it is difficult to get away.
> not meaning to be antogonistic, just wondering if everyday management task
> that comprises 90% to 95% of my workload has improved.
> thanks for the reply.
> "Chris Wood" wrote:
> > Charles,
> >
> > Sounds as though you should have been at PASS 2004 last week. You could
have
> > raised your concerns directly with MS managers there.
> >
> > Chris Wood
> > Alberta Department of Energy
> > CANADA
> >
> > "Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in
message
> > news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> > > I've been looking at the beta2 release of yukon and I am beginning to
be
> > > dissappointed in the product from a DBA viewpoint. I realize that a
lot of
> > > improvements have been made in the programmers side of things, but I
still
> > > have to manage the sql servers and I do not see any improvements in my
day
> > to
> > > day, week to week regular management task I have to perform. For
instance:
> > >
> > > 1.) i do not see any option to tell a backup to compress the backup
file
> > as
> > > it backsup a database. this would be a highly desired feature.
> > >
> > > 2.) there is no way to temporarily disable logins without changing the
> > > persons password which is not desired.
> > >
> > > 3.) using dts to export a table from a "development" database to a
> > "testing"
> > > or "production" database will only move the table definition and data,
but
> > > not the underlying indexes or constraints.
> > >
> > > 4.) using dts to export a view will only create a table on the
recieving
> > > end, not a view.
> > >
> > > 5.) I have 75 seperate sql server boxes, some with multiple instance,
all
> > > with many many databases and scores of jobs. I need something that can
> > show
> > > me easily the status of all jobs across all the servers without
manually
> > > connecting to each individual sql server instance and then expanding
down
> > to
> > > jobs. I want to select jobs and all jobs across all instance are shown
> > sorted
> > > by whatever I choose. Same way i want to select current processes and
see
> > the
> > > same things.
> > >
> > > the list goes on...
> > >
> > > mayby others can enlighten me and point out some real benefits in the
new
> > > sql server from a dba point of view.
> >
> >
> >|||Scott,
White Sands say this will be MS SQL ready later this year, at least at PASS
they said this.
Chris
"Scott Morris" <bogus@.bogus.com> wrote in message
news:%23LGfKYvqEHA.2696@.TK2MSFTNGP15.phx.gbl...
> There are other tools to manager db servers on an enterprise basis.
> DBArtisan is one (note - I have no actual experience with this tool but it
> was used by a fomer employer). My guess is that there are others.
> "Charles Pritt" <CharlesPritt@.discussions.microsoft.com> wrote in message
> news:DF22EB88-A335-4A9C-A1A4-5B548E77622E@.microsoft.com...
> > I wish I could have been there, but like a lot of companies, my company
> > doesn't have money for that sort of thing. And I am the only sql server
> dba
> > so it is difficult to get away.
> >
> > not meaning to be antogonistic, just wondering if everyday management
task
> > that comprises 90% to 95% of my workload has improved.
> >
> > thanks for the reply.
> >
> > "Chris Wood" wrote:
> >
> > > Charles,
> > >
> > > Sounds as though you should have been at PASS 2004 last week. You
could
> have
> > > raised your concerns directly with MS managers there.
> > >
> > > Chris Wood
> > > Alberta Department of Energy
> > > CANADA
> > >
> > > "Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in
> message
> > > news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> > > > I've been looking at the beta2 release of yukon and I am beginning
to
> be
> > > > dissappointed in the product from a DBA viewpoint. I realize that a
> lot of
> > > > improvements have been made in the programmers side of things, but I
> still
> > > > have to manage the sql servers and I do not see any improvements in
my
> day
> > > to
> > > > day, week to week regular management task I have to perform. For
> instance:
> > > >
> > > > 1.) i do not see any option to tell a backup to compress the backup
> file
> > > as
> > > > it backsup a database. this would be a highly desired feature.
> > > >
> > > > 2.) there is no way to temporarily disable logins without changing
the
> > > > persons password which is not desired.
> > > >
> > > > 3.) using dts to export a table from a "development" database to a
> > > "testing"
> > > > or "production" database will only move the table definition and
data,
> but
> > > > not the underlying indexes or constraints.
> > > >
> > > > 4.) using dts to export a view will only create a table on the
> recieving
> > > > end, not a view.
> > > >
> > > > 5.) I have 75 seperate sql server boxes, some with multiple
instance,
> all
> > > > with many many databases and scores of jobs. I need something that
can
> > > show
> > > > me easily the status of all jobs across all the servers without
> manually
> > > > connecting to each individual sql server instance and then expanding
> down
> > > to
> > > > jobs. I want to select jobs and all jobs across all instance are
shown
> > > sorted
> > > > by whatever I choose. Same way i want to select current processes
and
> see
> > > the
> > > > same things.
> > > >
> > > > the list goes on...
> > > >
> > > > mayby others can enlighten me and point out some real benefits in
the
> new
> > > > sql server from a dba point of view.
> > >
> > >
> > >
>|||I have DBArtisan. It is just a clone of sql enterprise manager. It allows the
administration of both sql server and oracle with the same tool.
thanks
"Scott Morris" wrote:
> There are other tools to manager db servers on an enterprise basis.
> DBArtisan is one (note - I have no actual experience with this tool but it
> was used by a fomer employer). My guess is that there are others.
> "Charles Pritt" <CharlesPritt@.discussions.microsoft.com> wrote in message
> news:DF22EB88-A335-4A9C-A1A4-5B548E77622E@.microsoft.com...
> > I wish I could have been there, but like a lot of companies, my company
> > doesn't have money for that sort of thing. And I am the only sql server
> dba
> > so it is difficult to get away.
> >
> > not meaning to be antogonistic, just wondering if everyday management task
> > that comprises 90% to 95% of my workload has improved.
> >
> > thanks for the reply.
> >
> > "Chris Wood" wrote:
> >
> > > Charles,
> > >
> > > Sounds as though you should have been at PASS 2004 last week. You could
> have
> > > raised your concerns directly with MS managers there.
> > >
> > > Chris Wood
> > > Alberta Department of Energy
> > > CANADA
> > >
> > > "Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in
> message
> > > news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> > > > I've been looking at the beta2 release of yukon and I am beginning to
> be
> > > > dissappointed in the product from a DBA viewpoint. I realize that a
> lot of
> > > > improvements have been made in the programmers side of things, but I
> still
> > > > have to manage the sql servers and I do not see any improvements in my
> day
> > > to
> > > > day, week to week regular management task I have to perform. For
> instance:
> > > >
> > > > 1.) i do not see any option to tell a backup to compress the backup
> file
> > > as
> > > > it backsup a database. this would be a highly desired feature.
> > > >
> > > > 2.) there is no way to temporarily disable logins without changing the
> > > > persons password which is not desired.
> > > >
> > > > 3.) using dts to export a table from a "development" database to a
> > > "testing"
> > > > or "production" database will only move the table definition and data,
> but
> > > > not the underlying indexes or constraints.
> > > >
> > > > 4.) using dts to export a view will only create a table on the
> recieving
> > > > end, not a view.
> > > >
> > > > 5.) I have 75 seperate sql server boxes, some with multiple instance,
> all
> > > > with many many databases and scores of jobs. I need something that can
> > > show
> > > > me easily the status of all jobs across all the servers without
> manually
> > > > connecting to each individual sql server instance and then expanding
> down
> > > to
> > > > jobs. I want to select jobs and all jobs across all instance are shown
> > > sorted
> > > > by whatever I choose. Same way i want to select current processes and
> see
> > > the
> > > > same things.
> > > >
> > > > the list goes on...
> > > >
> > > > mayby others can enlighten me and point out some real benefits in the
> new
> > > > sql server from a dba point of view.
> > >
> > >
> > >
>
>|||There are others. CA has a tool. BMC has a tool. These were found with a
simple google search on enterprise database management.
"Charles Pritt" <CharlesPritt@.discussions.microsoft.com> wrote in message
news:D11AAF30-DE80-41B0-9B18-28BDBCB2C654@.microsoft.com...
> I have DBArtisan. It is just a clone of sql enterprise manager. It allows
the
> administration of both sql server and oracle with the same tool.
> thanks
> "Scott Morris" wrote:
> > There are other tools to manager db servers on an enterprise basis.
> > DBArtisan is one (note - I have no actual experience with this tool but
it
> > was used by a fomer employer). My guess is that there are others.
> >
> > "Charles Pritt" <CharlesPritt@.discussions.microsoft.com> wrote in
message
> > news:DF22EB88-A335-4A9C-A1A4-5B548E77622E@.microsoft.com...
> > > I wish I could have been there, but like a lot of companies, my
company
> > > doesn't have money for that sort of thing. And I am the only sql
server
> > dba
> > > so it is difficult to get away.
> > >
> > > not meaning to be antogonistic, just wondering if everyday management
task
> > > that comprises 90% to 95% of my workload has improved.
> > >
> > > thanks for the reply.
> > >
> > > "Chris Wood" wrote:
> > >
> > > > Charles,
> > > >
> > > > Sounds as though you should have been at PASS 2004 last week. You
could
> > have
> > > > raised your concerns directly with MS managers there.
> > > >
> > > > Chris Wood
> > > > Alberta Department of Energy
> > > > CANADA
> > > >
> > > > "Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in
> > message
> > > > news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
> > > > > I've been looking at the beta2 release of yukon and I am beginning
to
> > be
> > > > > dissappointed in the product from a DBA viewpoint. I realize that
a
> > lot of
> > > > > improvements have been made in the programmers side of things, but
I
> > still
> > > > > have to manage the sql servers and I do not see any improvements
in my
> > day
> > > > to
> > > > > day, week to week regular management task I have to perform. For
> > instance:
> > > > >
> > > > > 1.) i do not see any option to tell a backup to compress the
backup
> > file
> > > > as
> > > > > it backsup a database. this would be a highly desired feature.
> > > > >
> > > > > 2.) there is no way to temporarily disable logins without changing
the
> > > > > persons password which is not desired.
> > > > >
> > > > > 3.) using dts to export a table from a "development" database to a
> > > > "testing"
> > > > > or "production" database will only move the table definition and
data,
> > but
> > > > > not the underlying indexes or constraints.
> > > > >
> > > > > 4.) using dts to export a view will only create a table on the
> > recieving
> > > > > end, not a view.
> > > > >
> > > > > 5.) I have 75 seperate sql server boxes, some with multiple
instance,
> > all
> > > > > with many many databases and scores of jobs. I need something that
can
> > > > show
> > > > > me easily the status of all jobs across all the servers without
> > manually
> > > > > connecting to each individual sql server instance and then
expanding
> > down
> > > > to
> > > > > jobs. I want to select jobs and all jobs across all instance are
shown
> > > > sorted
> > > > > by whatever I choose. Same way i want to select current processes
and
> > see
> > > > the
> > > > > same things.
> > > > >
> > > > > the list goes on...
> > > > >
> > > > > mayby others can enlighten me and point out some real benefits in
the
> > new
> > > > > sql server from a dba point of view.
> > > >
> > > >
> > > >
> >
> >
> >|||2) In Enterprise Manager, open the properties for the login and check "Deny
Access". Or use sp_denylogin. That's for NT logins only though. For SQL
logins things are indeed less simple, although if you have your users in
roles, you can simply remove the user from the role temporarily.
3 & 4) If you organise your users in roles, you won't have that issue. You
only have to make sure that the roles exists on both databases. Or you can
just choose not to copy object-level permissions (disable "Use default
option" in the DTS Export Wizard and click the "Options..." button.
5) See the topics "Multiserver administration" and "Automating
administrative tasks" in Books Online.
Btw, about 1: why do you need compressed backups? Tape drives have built-in
compression and if you back up to disk you can back up to a compressed
folder under most circumstances.
--
Jacco Schalkwijk
SQL Server MVP
"Charles Pritt" <CharlesPritt@.discussions.microsoft.com> wrote in message
news:56F4AFBA-6A89-4FF1-99A1-35358C02A57A@.microsoft.com...
> Please explain how number 2) already exist in current product.
> For number 3 and 4) if you are referring to having the dts wizard export
> an
> object and then selecting a specific table, I have not been able in the
> last
> 4 years to get this to work reliably. Mainly because there will always be
> some user that has access to that object on the source side that doesn't
> exist on the destination side and it fials because the specific users does
> not exists on the destination. Also, I did not see the option to move a
> "object" in the 2005 export wizard.
> for number 5) if you are referring to having to register each individual
> sql
> server and then clicking on each of the 75 sql servers one at a time and
> then
> going down to mangement and then sql server agent and then jobs looking at
> the list and then going to the next sql server agent and clicking on it
> and
> then going to management. and so on... I agree with you ... they have it.
> that is the way i do it now. I am referring to clicking on a icon that
> says
> sql server and then clicking on a icon that says jobs and it list every
> sql
> server and every job and its status. two clicks. a couple minutes to see
> all
> jobs.
> no i have not been dissappointed in sql server 2000, it is a far cry from
> sql server 6.5 and sql server 7.0 but there are still things lacking. This
> is
> my job. it all i do everyday, 7 days a week. manage more than 75 sql
> server,
> jobs, users, backups, and quite a few sql server clusters. I'm just
> looking
> for some improvement in the day to day task I perform.
> "Jacco Schalkwijk" wrote:
>> You must have been disappointed in SQL Server 2000 as well then. 2, 3, 4
>> and
>> 5 are already available in SQL Server 2000.
>> --
>> Jacco Schalkwijk
>> SQL Server MVP
>>
>> "Charles Pritt" <Charles Pritt@.discussions.microsoft.com> wrote in
>> message
>> news:0255B038-53EE-43C9-A64E-BEB4D45EAFE0@.microsoft.com...
>> > I've been looking at the beta2 release of yukon and I am beginning to
>> > be
>> > dissappointed in the product from a DBA viewpoint. I realize that a lot
>> > of
>> > improvements have been made in the programmers side of things, but I
>> > still
>> > have to manage the sql servers and I do not see any improvements in my
>> > day
>> > to
>> > day, week to week regular management task I have to perform. For
>> > instance:
>> >
>> > 1.) i do not see any option to tell a backup to compress the backup
>> > file
>> > as
>> > it backsup a database. this would be a highly desired feature.
>> >
>> > 2.) there is no way to temporarily disable logins without changing the
>> > persons password which is not desired.
>> >
>> > 3.) using dts to export a table from a "development" database to a
>> > "testing"
>> > or "production" database will only move the table definition and data,
>> > but
>> > not the underlying indexes or constraints.
>> >
>> > 4.) using dts to export a view will only create a table on the
>> > recieving
>> > end, not a view.
>> >
>> > 5.) I have 75 seperate sql server boxes, some with multiple instance,
>> > all
>> > with many many databases and scores of jobs. I need something that can
>> > show
>> > me easily the status of all jobs across all the servers without
>> > manually
>> > connecting to each individual sql server instance and then expanding
>> > down
>> > to
>> > jobs. I want to select jobs and all jobs across all instance are shown
>> > sorted
>> > by whatever I choose. Same way i want to select current processes and
>> > see
>> > the
>> > same things.
>> >
>> > the list goes on...
>> >
>> > mayby others can enlighten me and point out some real benefits in the
>> > new
>> > sql server from a dba point of view.
>>sql

Thursday, March 29, 2012

DBA guru advice - changes to production database

DBA guide

DBA Format

DBA Format

DBA Format

DBA for multiple servers

DBA for multiple servers

DBA for multiple servers

DBA First Date

DBA First Date

DBA dissappointed in sql server 2005

DBCC CHECKDB

Blog Archive

About Me