I will say it again - the problem you are...

I also would recommend looking at SQL Server 2008 and filestreams.

What you have is called an np-complete or np-hard problem. It is also referenced as the bin packing problem.

Hugo has a great article on this exact issue at: http://sqlblog.com/blogs/hugo_kornelis/archive/2007/11/30/bin-packing-part-1-setting-a-baseline.aspx

I...

Scheduling a shrink of your transaction logs every week is a mistake you really don't want to make. Review the article I link to in my signature which explains...

SELECT MIN(CASE WHEN PeriodId = 1 THEN PeriodEnd END) AS Period1,

MIN(CASE WHEN PeriodId = 2 THEN PeriodEnd END) AS Period2,

...

Be careful - you might be surprised when you use something like:

SELECT 1.Email, 2.Everything, 3.Else

Ahh, glad that it settled down for you.

george sibbald (5/19/2009)

---

If you detach\move\attach you lose the ability to easily back out so detach\copy\attach is safer.

I usually go the backup\restore method but thats really just a personal preference...

Now, you need to identify what queries are causing the CPU's to spike and fix them. It definitely sounds like you have an underpowered system that could benefit from...

You should set the max memory to no more than 4GB (4096MB). This will leave 2GB of memory to the OS.

You can also set the lock pages in memory...

If you have not set lock pages in memory, and you have not set the maximum memory - then you could be seeing issues.

Once again - SQL Server should not...

balbirsinghsodhi (5/19/2009)

---

Thanks guys,

Yes, it's 64 bit machine.

I am thinking of creating two virtual files. One will be the default on c drive and other will be on D drive and...

SQL Server will use as much memory as you have configured. If you have not set a maximum, it will use as much memory as is available on that...

You are causing...

A couple of things you could look at instead of using a specific index hint would be to use a query hint or plan guide.

Try using the OPTIMIZE FOR statement...