Looks like this is the syntax. Can't test. Don't have any named instances around.

If you're using windows authentication

sqlcmd -S servername\instancename -E -A

If you're using SQL authentication

sqlcmd -S servername\instancename -U...

Off hand, I don't know. What does Books Online say? 😉

Connections via the DAC don't fire login triggers. From management studio, open a new query and specift admin: before the server name (admin:MyServerName) and use windows authentication. You must be...

Is the database set to autoclose?

Are there any databases on the server that are the target of a logshipping scenario (getting logs restored regularly)?

Is there a scheduled job that's freeing...

Is there a question here?

Paresh Randeria (8/1/2008)

---

We have real time OLTP application where data is continously written into the database. Very high Insert.

This database is full recovery and we are not talking Log back....

Could you be a bit more specific about the problem please?

Duplicate post. Direct replies to the following thread please.

http://www.sqlservercentral.com/Forums/Topic545117-149-1.aspx

Simon (8/1/2008)

---

Hi Gail, saw your reply to this thread, does this mismatch between the metadata and the physical allocation have any impact any the data resturned by any operations on...

1204 and 1205 write deadlock graphs and associated info into the SQL error log. If you aren't having deadlocks, you won't see anything written. I wouldn't usually suggest using both....

Adam Bean (7/31/2008)

---

I'd recommend making 1 data file per CPU (hyperthreading doesn't count, nor should be used anyways), preallocate a few gigs per data file, and enable the -T1118...

Both full and bulk-logged recovery models require log backups. If you don't have log backups, the transaction logs will grow without bound (as you've noticed). You can have a look...

Full recovery mode?

Any log backups running?

Any replication running?

Do you have a point-in-time recovery requirement for these databases?

If you run the following query, what does it say for the offending databases?

SELECT...

Because...

Don't forget to set the DB to simple recovery mode or schedule log backups.