The basic approach is to record the behavior of your queries in 2008. Get the execution times, resources used, and, for really interesting queries, the execution plan. Then do the...

The page latches could be from slow disk, or memory issues, or stuff like that, sure. But, it could also be from scans where seeks would work better because bad...

No certifications at all and my salary is more than adequate. I also seriously doubt I would be paid more if I had an MCSE or almost any other cert...

Kulgan_ (8/27/2014)

---

Hi,

In addition... when You do the "select *" DB still have to grab all the data from disk... If columnstore index would include all columns then in theory this...

ChrisM@Work (8/26/2014)

---

Grant Fritchey (8/26/2014)

---

Nice Chris, you took away my two comments, on the RIGHT JOIN getting turned into an INNER JOIN and that awful string manipulation against a column. Those...

You can't do this through the backup and restore process, no. You'd have to build some type of data migration. That's possible, just a lot of work.

Nice Chris, you took away my two comments, on the RIGHT JOIN getting turned into an INNER JOIN and that awful string manipulation against a column. Those were my two...

ramana3327 (8/25/2014)

---

Hi All,

Thanks for the replies.

I read that for migration we can schedule log backup or differential backup to reduce the downtime. Anyone did this? I need the downtime as...

If it only takes one minute to rebuild your indexes, we're talking very small data sets. It sounds like you have a growth limit placed on your log file or...

I'd suggest monitoring the backup process and see what the wait statistics are while the backups are running. Understanding why the backups might be waiting on anything will let you...

There is no downgrade path. It's just a question of migrating your data structures and data down to the older version. Personally, I wouldn't do it.

If you're seeing performance issues,...

1 or 3. But you should do the backups even if you do #3. The backups should just be how you protect yourself.

Nope. Access doesn't use Transact SQL and the full T-SQL stack supported by SQL Server.

There's no instant or magic way to build this kind of knowledge. It takes a long time. I'd add getting a copy of the book T-SQL Querying Fundamentals by Itzik...

Side-by-side is absolutely the best and safest. I've never really seen any major issues during upgrades, but if you had any, the ability to instantly just bring the old server...