serverand SQL Server EM. In a Production SQL Server environnmet:
1- How do you create a baseline for performance tuning?
2- How do you refresh Dev box from a large Production DB? 3- what's
the few main scripts you schedule or use everyday in sybase?
4- what's the main commnads to startup, shoudown and check thesql
server DB?
5- What's the main sp_ procs you use everyday?
6- How do you find and tune top 10 bad sqls?
7- what's the best forums to post questions and get quick answers?
8- what's the best 3 third party tools for sql server?
9- any sybase - oracle equivalent cheat sheet exist in internet
orbook?
10- what's the top 3 books you recommended?Many thanks for your time
and help"Frank" <soal6570@.yahoo.com> wrote in message
news:42601b2.0404031906.10ec61d0@.posting.google.co m...
> I come from Oracle DBA background and I know a little about SQL
> serverand SQL Server EM. In a Production SQL Server environnmet:
> 1- How do you create a baseline for performance tuning?
> 2- How do you refresh Dev box from a large Production DB? 3- what's
> the few main scripts you schedule or use everyday in sybase?
> 4- what's the main commnads to startup, shoudown and check thesql
> server DB?
> 5- What's the main sp_ procs you use everyday?
> 6- How do you find and tune top 10 bad sqls?
>
> 7- what's the best forums to post questions and get quick answers?
> 8- what's the best 3 third party tools for sql server?
> 9- any sybase - oracle equivalent cheat sheet exist in internet
> orbook?
>
> 10- what's the top 3 books you recommended?Many thanks for your time
> and help
You mention Sybase several times - are you working with Sybase or with
Microsoft SQL Server? Assuming you're using Microsoft's product, then here
are some quick answers:
1. Use a test database, make changes, test them, and use Profiler to see
what the difference is.
2. Backup/restore is easiest, but log shipping or replication might be
better if you have very large databases, and you want to copy the changes
incrementally or with a short delay.
3. That depends a lot on the environment, but backups and maintenance plans
are the obvious ones.
4. Start/stop with the NET START/STOP command, through Enterprise Manager,
or use any interface (eg. WMI) that can manipulate Windows services. I don't
know what you mean by 'check' the server, but see the DBCC commands in Books
Online, and also look at maintenance plans.
5. Too many to mention, but sp_who2 and sp_lock are very useful.
6. Use Profiler, and filter on query duration to find long-running
statements. Profiler can also display the execution plan.
7. Here, or the microsoft.public.sqlserver.* groups - there are groups for
specific areas such as .security, .xml, .replication etc.
8. That depends on what you want to do - the tools that come with the
product can do most things.
9. Assuming you mean Microsoft SQL Server, then here is one:
http://www.microsoft.com/resources/...art2/c0761.mspx
10. Books Online, Books Online and Books Online...
Simon|||Thanks a lot for answers. It was great specially the link you sent me.
Just few more questions:
1- What is the best practice for sizing a new Database and
configuration parameters? Any link for that or just a quick comment
from you? Do we have something like init.ora here?
2- I heard that you can write custom-scripts for admin and put them in
master database and access them for all db. Is that the way you can
cutom monitor the db? Can you send me a small example?
3- What is the top 5 troubleshooting and monitoring needs to be done
as a daily basis?
"Simon Hayes" <sql@.hayes.ch> wrote in message news:<40700624$1_3@.news.bluewin.ch>...
> "Frank" <soal6570@.yahoo.com> wrote in message
> news:42601b2.0404031906.10ec61d0@.posting.google.co m...
> > I come from Oracle DBA background and I know a little about SQL
> > serverand SQL Server EM. In a Production SQL Server environnmet:
> > 1- How do you create a baseline for performance tuning?
> > 2- How do you refresh Dev box from a large Production DB? 3- what's
> > the few main scripts you schedule or use everyday in sybase?
> > 4- what's the main commnads to startup, shoudown and check thesql
> > server DB?
> > 5- What's the main sp_ procs you use everyday?
> > 6- How do you find and tune top 10 bad sqls?
> > 7- what's the best forums to post questions and get quick answers?
> > 8- what's the best 3 third party tools for sql server?
> > 9- any sybase - oracle equivalent cheat sheet exist in internet
> > orbook?
> > 10- what's the top 3 books you recommended?Many thanks for your time
> > and help
> You mention Sybase several times - are you working with Sybase or with
> Microsoft SQL Server? Assuming you're using Microsoft's product, then here
> are some quick answers:
> 1. Use a test database, make changes, test them, and use Profiler to see
> what the difference is.
> 2. Backup/restore is easiest, but log shipping or replication might be
> better if you have very large databases, and you want to copy the changes
> incrementally or with a short delay.
> 3. That depends a lot on the environment, but backups and maintenance plans
> are the obvious ones.
> 4. Start/stop with the NET START/STOP command, through Enterprise Manager,
> or use any interface (eg. WMI) that can manipulate Windows services. I don't
> know what you mean by 'check' the server, but see the DBCC commands in Books
> Online, and also look at maintenance plans.
> 5. Too many to mention, but sp_who2 and sp_lock are very useful.
> 6. Use Profiler, and filter on query duration to find long-running
> statements. Profiler can also display the execution plan.
> 7. Here, or the microsoft.public.sqlserver.* groups - there are groups for
> specific areas such as .security, .xml, .replication etc.
> 8. That depends on what you want to do - the tools that come with the
> product can do most things.
> 9. Assuming you mean Microsoft SQL Server, then here is one:
> http://www.microsoft.com/resources/...art2/c0761.mspx
> 10. Books Online, Books Online and Books Online...
> Simon|||"Frank" <soal6570@.yahoo.com> wrote in message
news:42601b2.0404060339.d638dbd@.posting.google.com ...
> Thanks a lot for answers. It was great specially the link you sent me.
> Just few more questions:
> 1- What is the best practice for sizing a new Database and
> configuration parameters? Any link for that or just a quick comment
> from you? Do we have something like init.ora here?
> 2- I heard that you can write custom-scripts for admin and put them in
> master database and access them for all db. Is that the way you can
> cutom monitor the db? Can you send me a small example?
>
> 3- What is the top 5 troubleshooting and monitoring needs to be done
> as a daily basis?
<snip
1. As regards sizing, some of the big hardware vendors have sizing guides
for their own hardware, and Books Online has a section on estimating table
sizes. As for init.ora, the general MSSQL approach is that the database
server should be left to manage itself as much as possible - you can change
server-wide settings with sp_configure, but it's not something you should do
unless you really need to. One exception is memory, because MSSQL will take
all the memory on the box by default, so if you have other apps on the
server, you may need to limit how much memory MSSQL should use.
2. This is possible, but it's not really advised - Microsoft doesn't support
it. Which doesn't mean that no one does it, of course - see here for more
information:
http://www.winnetmag.com/Article/Ar...1044/41044.html
3. That depends very much on your enivronment, but monitoring backups,
maintenance jobs and failed logins are one task, as is dealing with
databases where the transaction log fills up. You can set alerts on most
conditions to get a notification and/or automatically run a script in
response.
Simon
No comments:
Post a Comment