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

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/new...elcomePage.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 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...[vbcol=seagreen]
> Hi
> Send your resqlwish@.microsoft.com
> Yes, some of those features are nice, but
> "Charles Pritt" wrote:
of[vbcol=seagreen]
still[vbcol=seagreen]
day to[vbcol=seagreen]
instance:[vbcol=seagreen]
as[vbcol=seagreen]
"testing"[vbcol=seagreen]
but[vbcol=seagreen]
all[vbcol=seagreen]
show[vbcol=seagreen]
down to[vbcol=seagreen]
sorted[vbcol=seagreen]
see the[vbcol=seagreen]
new[vbcol=seagreen]
|||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...
> to
> as
> "testing"
> show
> to
> sorted
> the
>
>
|||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[vbcol=seagreen]
> 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:
have[vbcol=seagreen]
message[vbcol=seagreen]
be[vbcol=seagreen]
lot of[vbcol=seagreen]
still[vbcol=seagreen]
day[vbcol=seagreen]
instance:[vbcol=seagreen]
file[vbcol=seagreen]
but[vbcol=seagreen]
recieving[vbcol=seagreen]
all[vbcol=seagreen]
manually[vbcol=seagreen]
down[vbcol=seagreen]
see[vbcol=seagreen]
new[vbcol=seagreen]

DBA Dilemma

We have a little dilemma with our DBA staff regarding reporting services and
using a general account, we call RSAdmin, for executing stored procs in the
background and bringing back the results via Reporting Services.
Our DBA is suggesting that we stay away from a general account like this
because of the implicit security that is associated with it. Our argument to
them is that if we start granting by individual, then that will make their
job even that much more complex and the maintenance on that is a nightmare
with people moving and quitting, etc..
Has anyone experience issues like this and how did you go about resolving
them.
Any answer is GREATLY appreciated and Thanks in advance.
wnfisbaI do not ever use the account of the person running the report. I have a
generic account say Reports (I run in mixed mode). This account is only used
for reports and is readonly. When I have a stored procedure it gives this
account execute permissions. This is very clean and is definitely not a
security hole. What user sees what is controled by who is given rights to
what report. So I control that at the Report Server.
Another advantage of this is that this allows connection pooling. Connection
pooling requires the connection to be exactly the same. If the connection is
for a different user then there will be a new connection created (or perhaps
multiple connections) per user running a report. Connection pooling both
puts less strain on the database server and it improves your performance.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"wnfisba" <wnfisba@.discussions.microsoft.com> wrote in message
news:C576900D-1F8B-4DA6-B3EE-7F1642B034B4@.microsoft.com...
> We have a little dilemma with our DBA staff regarding reporting services
> and
> using a general account, we call RSAdmin, for executing stored procs in
> the
> background and bringing back the results via Reporting Services.
> Our DBA is suggesting that we stay away from a general account like this
> because of the implicit security that is associated with it. Our argument
> to
> them is that if we start granting by individual, then that will make their
> job even that much more complex and the maintenance on that is a nightmare
> with people moving and quitting, etc..
> Has anyone experience issues like this and how did you go about resolving
> them.
> Any answer is GREATLY appreciated and Thanks in advance.
> wnfisba

DBA Contract without Local Admin priveleges

O what a place to be

I started this Contract as an (Interim) for a new DBA role, for an application support Company last month & all was going well.

The User Application is run via Citrix against multiple Hosted Sybase ASA Databases.

I introduced SQL 2005 with Reporting Services as a mixed Data Mart Remote Query via ODBC Linked Servers setup.

Because they had never had a DBA before the Data I was able to pull from over thirty seperate databases into one and present via Reporting Services has blown them away.

And then one day the Senior Support Analyst told me he had put the main most important Sybase Database on a completely seperate domain he had created(with no Trust between the two) , because he was unable to secure the existing domain against unauhorized remote internet intrusion & Viruses.

(I never liked the idea that hosted customers were domain\users on the Corporate network)

To add insult to injury he then told me to install & maintain another SQL Box on the new domain, OK so far.

I logged into the supoposed new box via citrix & then remote desktop, and to my disbelief he had the desktop locked down - no access to control panel or anything - he asked me why i needed access - I told him - he asked me why I need to have reboot priveleges - I told him.

So now he's installed 2005 himself in the vain hope I can work without Local Admin privelages or need to unlock the Desktop - he certainly won't give me Domain Admin.

I Just cannot believe I'm unable to persuade him to Unlock the Desktop & have even threatened to walk out unless he lets me do my Job.

He probably does'nt like me but there can be absolutely no question about my abilities or accessing data that i should'nt.

He's basically read a Deny by Default article and expects me to start of as a user with a locked desktop and then request & justify escalating my security from there.

Is this possible ?

Good Grief :eek: Any ideas what I should do ?

Thanks

GW& have even threatened to walk out unless he lets me do my Job.

I say do that! :p

Or tell him that if the server needs a reboot then he has to do it - point out to him that if the server goes down (day or night) he will have to remote connect to work and sort it out - rather than having one of his capable "drones" doing it. Tell him to expect to be on-call 24/7/365 (that is assuming that he wants his customers server to be online 99.9% of the time)

If he's so uppity about security then maybe you should suggest signing some disclaimer saying that you're not going to prat about with the server or any sensitive data in contains?

You can't do your job without the access, period.

Alternatively, simply tell him to "[expletive] off" when he asks you anything about that server :D|||I would just pester him with emails (cc'd to appropriate folks) that you need various tasks done on the server. Be good and vague about the actual details. For example: "Please be sure that daily backups are taken of these databases." If he is worth dealing with, he will figure out SQL Agent quickly enough. If not, well, just sit back and laugh as he does the backups manually. Escalate as necessary (Make sure the backups are not on the same physical disk as the database).

Once he has all that squared away, if you are not satisfied, hit him up with profiler trace requests. This should be accompanied by a stream of SQL scripts that are "tweaks to existing code".

Polish the whole thing off with requests to load data from various sources (implementation details left to him, of course).

And of course, most importantly, sprinkle liberally with thanks, and politeness.|||Ahh, the old scaremongering tactics - hadn't even crossed my mind!|||Who is your manager? They should be fighting this battle with/for you. If you where hired to do a job and are unable to it will reflect badly on the whole chain.

Alternatively I think goergev's first approach is best. Getting into a p_ssing contest with a Senior employee when you are new is not a wise path.

Changing culture is never an easy task. Good luck.|||MMMmmmmm tehe - U Monkeys !!

Such a shame though this is going to slow my dev progress to a crawl & I take pride in my work.

I'm happy as a contractor and would'nt take a permie role anyway - hope the new DBA likes his new life.

I just wonder how he's (Senior Support Analyst) gonna secure his brave new world when he's not capable of purging the existing one.

Dunno loads about Citrix & Network Security best practices but Is it common to let Customers on to the Corporate Domain as Users, Is Citrix really that secure ?.

I figure he's set himself up as Domain Admins and does'nt want to share his power with the rest of IT.

GW|||I figure he's set himself up as Domain Admins and does'nt want to share his power with the rest of IT.
bingo! :)

If he's willing to take all the power, then he's gotta be willing to take all the responsibility that comes with it too.|||Sorry, I mis-understood your message of "interim for a New DBA role". I saw that as "contract for hire".

I am a contractor too so I understand the "no permies" feeling. But I will ask you the question. What were you hired to do? Write reports or prepare the way for a new DBA or both. Since you are a contractor you can be even bolder in dealing with culture. Tell them there is a helpful way and a non-helpful way to do things. Right now he, and by extension the company, is in a non-helpful mode.

As a contractor I would much rather come into a company where the previous contractors where helpful themselves because it makes my experience better.|||Sorry Bartron Maybe I was'nt quite Clear.

The company had never had a DBA before - they hired one but had to wait 3 Months for him to start - Thus I got the contract for 3 months to fill in.

(they have a 5 strong IT Application Support Dept with strong links to the Application Developers in the holding company)

The new DBA has since turned down the job & the Co. are now actively seeking someone else.

My Brief was simple "Consider us a Greenfield site and start from scratch doing what you think is Best - we need reports on all these seperate Sybase databases".

So I recommended and implemented a SQL 2005 Data Mart with reporting Services.

GW|||Sounds like a great approach to their original intent.

Good luck dealing with the new agenda. :-) Seems like "doing what you think is best" should give you some leverage. Of course they can always ignore it. Their peril.|||... expects me to start of as a user with a locked desktop and then request & justify escalating my security from there.

Seems pretty standard at face-value. I'm don't need domain or local admin on any of our production sql server boxes to do my job. It would help and it sure would be nice, but I don't need it. On the same token, our network engineers understand and take on responsibility for the server itself. This includes restarting it on my request, staying current with patches and feeding me requested wmi indicators.

The problem arises when someone is locking you down just because they can. If they still give you grief after you have clearly justified your requirements, take it to your contract admin and draw a picture for them of how this person is directly hindering your ability to perform.|||Thanks to everyone for your support.

Looks like I'm just gonna have to leave em with a less developed and less stable product.

Thanks Teddy for clarifying it is possible to be a DBA without Local Administrator security.
(Do they allow you to access the control panel or event logs ?)

Just seems ridiculous to me considering I'm the only DBA here & I recommended, designed & wrote the Bl**dy thing.

It's not even an OLTP it's a sodding homemade Data Mart.

The only thing on this new network for the next few months is one of the 30 Sybase DB's - I have Domain Admins to the current network.

:eek: A Contractors Life is not an easy one.

GW|||Thanks Teddy for clarifying it is possible to be a DBA without Local Administrator security.
(Do they allow you to access the control panel or event logs ?)


No, yes.

I'm in a highly responsive environment though so this works fine. If I OMGJUSTNEED to perform administrative tasks, I can tap an engineer and either guide them or have them over my shoulder as I do whatever it is I need to do. I get whatever general filesystem access I request and I can requisition whatever additional logging I need including exposing log files, setting up wmi logging or asking for a new package to be designed for one of our third-party performance monitoring applications.

If engineering wasn't as responsive as they are, I would be able to justify administrative rights on our servers. If you're in one of those "job security through obscurity" environments where one person is guarding the keys to the proverbial kingdom with their life, then you might want to go ahead and push for those admin rights.