One additional driver for installing SPs and HFs.

When seeking support for SQL Server from Microsoft (or indeed for any piece of software from any vendor), usually the first thing you...

Not only is it possible, I think the notion of having tempdb on its own separate disk \ array \ controller is suggested as one step you can take towards...

First step, get a working Master database.

Take your installation media and run setup again with the following switches:-

setup.exe /qn INSTANCENAME=”MSSQLSERVER” REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=”mypassword”

where mypassword is the sa password.

INSTANCENAME=”MSSQLSERVER” for a...

Be careful with SQL Mail, some interesting gotchas with it.

My favourite is the way that certain Windows patches (usually IE ones) lose the default MAPI handler setting after a reboot.

If...

That's puzzling, I thought that would be all you would need to do.

So after restarting the server, if you look in the SQL Server log for the named instance, you...

Hmm ok so on your firewall you are allowing TCP 1433, and TCP xxxx (the high level port you manually assigned to your non-default instance).

Can you try allowing UDP 1434...

Idera SQL Diagnostic Manager is a good product which is very much geared towards what you are trying to do.

Don't know what your budget is, but this is a good...

I think you need to set this for whichever IP Address SQL Server is actually using.

Looking at the configuration I have in front of me on my PC, I just...

Hmm try this...

Look in the SQL Server 2005 Configuration Manager.

Under Network configuration, Protocols for (instance name).

Look at the properties for TCP\IP and look on the IPAddresses tab.

If TCP Dynamic Ports...

I stand corrected - thank you SA.

On SQL Server 2000 you needed to be a SysAdmin to run profiler, but this is no longer the case on 2005 & 2008.

I...

Two words, Management Buy-In.

To change all that you are going to need to convince some senior people in your organisation.

I'm pretty sure that you cannot give your developers the ability to use profiler without also giving them SysAdmin rights.

Could be any number of things but I suppose that the two most obvious might be:-

*Account locked out because of too many incorrect login attempts.

*SQL Server authentication changed from Mixed...

Are you seeing any error messages being returned?

Are you aware of any changes to the server that have been made recently?

Yup just for auto-shrink and auto-grow.

Sorry I may have misread the question, this report won't show information on manually initiated shrink or growth operations.