Paul White NZ (4/6/2010)

---

Marts (4/5/2010)

---

On our current setup without any modifications, I could move the logs and/or the tempdb to the system drive (raid 1), away from the data files....

Jeff Moden (4/5/2010)

---

Stop. It's a waste of time to do...

Marts, I HIGHLY recommend that you try to convince your company to hire a performance tuning professional for a day or two to give your system a review and recommend...

Paul White NZ (4/5/2010)

---

TheSQLGuru (4/5/2010)

---

NOTE: I am not 100% sure specifying an object ID in the DMV gets it to read JUST that object and I don't have time to...

Unless you have a BUNCH of spindles, many smaller files will actually be SLOWER due to head thrashing on the disk drives. Not a good solution there. How...

gmamata7 (4/3/2010)

---

Hi,

We have MOSS 2007 SP1 databases in SQL Server 2005 and I'm trying find the Index Fragmentation for the Content database of size 10 GB using below query:

SELECT database_id,object_id,...

george sibbald (4/2/2010)

---

sorry Chad getting completely off subject but I know these companies pick up on internet entries so I will post this here:

Hyperbac - please don't move away from...

I mentioned that at 1117 yesterday. 😎

I would look at SSIS, import wizard or some other BULK INSERT mechanism if you have a lot of data to feed into sql server.

Since you are returning 48000 out of 50000 rows, how about just forcing a table scan on everything?

Allow me to step outside the box here and ask why you don't 'sumarize' the data in the .NET application before it ever hits the database. Then just insert...

1) give yourself a BIG tlog to start before doing the shrink so it doesn't have to grow.

2) script and drop ALL indexes if you are deleting 85% of the...

I don't understand this talk about numbers since the OP clearly stated "... a code with numbers and characters". Can't put those characters in an int, bigint, numeric, decimal,...

I only mentioned the index cleanup investigation because the OP stated concern about having so many indexes on the table.

I disagree with your statement that not many can...

1) maybe response time is poor because your server is weak or poorly configured. how much RAM? how many CPUs?

2) what query or queries are you running...