Well first off store dates as dates not as strings,

So you would need to change AccessDate to DATETIME or add a column of the DATETIME data type.

They look at...

Yes, unless you have implicitly given access to read data to the public role, or the login has sysadmin rights.

Thats the way the GUI works and would be a change to the GUI which would be evaluated if you raised it as a Connect issue, but the likely hood...

What do you need help with? It is not very clear.

1st one, your connected to the default instance using a trusted connection

2nd one, your giving the wrong password for...

Its the way that the create script works, so your asking to change the behavour of SQL, so that would need to be raised as a connect issue and they...

andrew gothard (1/30/2013)

---

s it's a DEV box, try running this then retrying

DECLARE @DBName NVARCHAR(200);

SET @DBName = '<Enter your db name here>';

DECLARE @spid INT;

DECLARE IHateCursors CURSOR FOR

SELECT

spid

FROM

master.dbo.sysprocesses

WHERE...

Did you investigate what the SPIDs where doing which blocked you?

Did you try setting the DB into single_user mode?

If recovery dont matter then set recovery to simple and leave it in simple.

Once in simple issue a checkpoint in the DB, then shrink the file.

Taking offline detach attach can...

Probably will depend on your requirements, so I would speak to Dundas directly.

Take a look at the SQLAgentOperator, SQLAgentUser, SQLAgentReader roles in MSDB

No, Solarwinds at the time I was evaluating monitoring software wasn't robust or mature enough to monitor SQL.

While it now does Application monitoring where it can connect to an ODBC...

IIRC you can run 25 instances on 1 node, so that would be active / passive, if it is licensed accordingly

If you want to run 1 instance on Node1 and...

Poor Performing SQL Part 1 - http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

Poor Performing SQL Part 2 - http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

Also take a look at the Accidental DBA guide on the high CPU chapter (Link in my signature...

CREATE TRIGGER ... ON ...

AFTER INSERT

AS

EXEC MSDB.dbo.sp_send_dbmail ...., ...., ...., ....

Lookup database mail, configure it, and then put the right parameters into the sp_send_dbmail call that you need.

You could look at initialization from backup, instead of from snapshot.

http://msdn.microsoft.com/en-us/library/ms147834%28v=sql.100%29.aspx