I've made up my case scenario.

The index take around 450 megs.

I've build up a specific query to make sure an index seek occurs (which was confirmed by the plan).

Upon check,...

True, index seek.

Wouldn't have been quicker to slipstream the service pack and performing both the upgrade and the service pack at the same time?

http://blogs.msdn.com/b/petersad/archive/2009/02/25/sql-server-2008-creating-a-merged-slisptream-drop.aspx

Thank you Gila,

I will need to update that part of the sniffing issue...

Hello,

I've test your data and I've the same results as you on my SS2k8 R2 RTM.

I can easily explain the estimated ~20 rows.

For the 268 estimated rows it seems that...

I'm mostly done with the white paper from: http://msdn.microsoft.com/en-us/library/dd535534%28SQL.100%29.aspx

and I've found with colmodctr what I need to go on.

johnitech.itech (2/6/2012)

---

See this link below

http://connect.microsoft.com/SQLServer/feedback/details/668354/no-statistics-management-options-fit-nightly-load-large-etl-system-scenario%5B/quote%5D

Thank you for the link, I've met the threshold they refer to in my test example.

What's interesting however is this link:

http://msdn.microsoft.com/en-us/library/dd535534%28SQL.100%29.aspx

I've also added trace flag 205 and started the profiler to gather missed information, nothing is triggered after the initial update.

(except when the plan is first run, statistics get updated...

Wasn't aware of this one, could be handy one day or...

jasona.work (1/27/2012)

---

Megistal (1/27/2012)

---

First nice article!

Second, must I understand that the only way in SQL 2008 and Up to break the log chain is to switch to simple recovery model?

Pre-SQL Server...

Peggy, the file extension is only for your convenience. Default full backup are .bak, transaction log are .trn but you can defined them as you wish.

First nice article!

Second, must I understand that the only way in SQL 2008 and Up to break the log chain is to switch to simple recovery model?

Pre-SQL Server 2008, there...

As Evil Kraig F said it will be quite hardware dependent.

To my eyes it would be around: time to backup the table + time to send that over the network...

Thank you for your time. I'll call it off for now, unable to reproduce it (and unable to have the exact same scenario)

At that time too many things were different,...

Thks

I should have copy the error but SQL gave back something like "Exceeded transaction size" which make me wonder what limit I've reached for a transaction.

I had enough room for...