I'm actually not worried about...

The basics are easy:

Run the Upgrade Advisor

Fix any issues

Migrate the logins

Backup the databases on the old server

Restore the databases on the new server

Run DBCC checks (a little paranoia goes a...

Based on that thread, please run...

Gianluca Sartori (5/3/2010)

---

I don't see how tempdb reads can grow its data file(s).

At least, I'm not aware of any way this could happen, but I could be flat wrong.

Can...

GilaMonster (5/3/2010)

---

Grant Fritchey (5/3/2010)

---

GilaMonster (5/3/2010)

---

Why? SQL won't recompile when a different...

GilaMonster (5/3/2010)

---

Why? SQL won't recompile when a different branch is taken....

Also, having four completely different queries inside the IF statement pretty much guarantees you're likely to see recompiles. If you need to set up this kind of IF clause, then...

Gianluca Sartori (5/3/2010)

---

I don't know if SQL 2008 R2 has changed something in connection limits for Express Edition.

The only thing I'm sure of is database size, that changed from...

ankur003 (5/3/2010)

---

I just tested some SPs and found that after using NOLOCK the execution time of the queries reduced from 35 to 31 secs approx.... Now this is very tempting......

Greg Edwards-268690 (5/3/2010)

---

I'd recommend taking a closer look at 2010 before recommending...

Sounds like a permissions issue. That would be the main difference. But without details on exactly what error you're getting, it's hard to say beyond that.

Total agreement. You'll get enough of what you need in order to build out your initial system with Express. If you hit limits, mostly likely in connections, you take the...

Since this is asking for opinion...

I think NOLOCK is probably the single most dangerous hint available. It's seductive and attractive and doesn't appear to cause a single problem. But the...

Here's an article just on how to handle errors within TSQL code:

http://www.simple-talk.com/sql/t-sql-programming/sql-server-error-handling-workbench/%5B/url%5D

The general approach is to identify what's running slow and then look at the execution plan to understand what it's doing. It's a rather large topic. Entire books have been...