Agree with all the above.

You should look upon log shrinking as a last resort and even then you want to make sure that there is a valid reason. Its not...

SQL stores logs for the engine and the agent.

The logs are generally stored in the LOG folder of the engines data root folder (eg c:\program files\microsoft sql server\mssql.1\mssql\log).

You can also...

jamesn 89076 (10/12/2010)

---

TheSQLGuru (10/12/2010)

---

A/A clusters are a good way to maximize hardware investment. One thing I advise my clients is to have a monitoring agent of some flavor trigger...

Markus (10/12/2010)

---

Microsoft pushes Clustering as the next best thing to sliced bread. In my experience we have had more downtime with clusters than with a regular server. Clusters...

Essentially if you have two servers and want to leverage the most out of them you would use an active/active (if one fails the instance fails over to the second...

You cant backup the secondary database. It is in RESTORE mode and cant be backed up or accessed!

Maybe i am coming in on this a bit late but this thread which i worked on gives you a good example:

A colleage just told me, that it doesnt need to be licensed for the first 30 days. So as long as you get the initial principal back online within 30...

You do not need a license for your mirroring server (assuming you dont run both servers instances for user access at the same time).

What that means is if you are...

So if i understand you, your OS is using 95% of your 48GB or 95% of what it is allocated?

The thing to keep in mind is that at 80-90% memory...

Krasavita (8/19/2010)

---

Here is the error:

Unable to start execution of step 1 (reason: line(1): Syntax error). The step failed. Unable to start execution of step 1 (reason: line(1): Syntax error)....

I agree with David.

If cost is a consideration then just lower the amountn available to SQL (it is quite resiliant).

However a word on adding memory, we have a cluster with...

Rem70Rem (8/16/2010)

---

Hi Adam,

Thanks for your reply. Currently I am running something similar every night to kill my connection. I would like to *** the table level to this....

This works to Kill users of a set database, sure you could reconfigure to do table lever:

CREATE PROCEDURE usp_killDBConnections @DBName varchar(50), @withmsg bit=1

AS

SET NOCOUNT ON

DECLARE @spidstr varchar(8000)

DECLARE @ConnKilled smallint

SET @ConnKilled=0

SET...

Agree with Ashish.

Try reconstructing guery to commit more regularly (run in smaller chunks). If possible you may want to consider restarting your instance and then running query straight away (before...