SQL Server is going to take all the memory you give it. 2gb out of 16gb is probably just fine, but if you feel it's not, or there seem to...

maruthipuligandla (8/9/2011)

---

Hi,

Thanks for the reply..

Can you please let me know how to overcome this, i want to know from your practises because you are SQL DBA..

Also you suggested me to...

We're trying, but we're not there, so we can't...

You can't overcome all the disadvantages. The primary problem is not using this datatype as the primary key. The primary problem is using this data type as the clustered index....

Lowell (8/9/2011)

---

on the other hand, I know of DBA's who have never used the DMV's at all.

Subjective Adapts covered the DBCC commands pretty well.

I dunno, would you say that...

A server-side trace is the best mechanism you have for doing this. They are not very resource intensive at all. In fact, it has a very light foot print as...

I get why compression could be said to reduce the DBAs workload. I'm just trying to figure out how encryption does that.

srinath.vanama (8/9/2011)

---

IN SQL Server 2008.

1) Backup encryption is possible.

2) Data compression and Resource governor.

3) Installation improvements. Disk images and service pack uninstall options.

4) TDE(transparent Data Encryption) Ability to encrypt entire...

It sounds like they were trying to get you talk about blocking which is caused when a resource is locked by one user, preventing the next user from accessing it.

Or,...

Without seeing the query and the execution plan, it's hard to tell you why it's taking a long time.

One point worth noting, when you tell it to return the TOP...

Out of time for what? Is this about you learning or about an emergency at work, or are we filling in for an interview?

For a great start on DMVs, I'd...

How to reduce the workload? Shoot the users? No, probably not.

You actually can't "reduce" the workload. What you can do is make the workload more efficient through design, construction &...

Anytime we're in Bradford, I have a pub selected. The only bad thing...

I suspect some of the databases probably have different drive or file configurations. You can't just replace these. You'll need to use a MOVE operation.

Have you tried to start the service? You can do that through the Management Studio interface or by opening the SQL Server Configuration Manager. You can even use netstart commands...