How does this approach perform when competing against something like...

where

d1.WeekDay = coalesce(@Weekday, d1.WeekDay)

does your method produce a better query plan? Does your version make a index seek on Weekday...

How does this approach perform when competing against something like...

where

d1.WeekDay = coalesce(@Weekday, d1.WeekDay)

does your method produce a better query plan? Does your version make a index seek on Weekday...

How does this approach perform when competing against something like...

where

d1.WeekDay = coalesce(@Weekday, d1.WeekDay)

does your method produce a better query plan? Does your version make a index seek on Weekday...

Good Article Nakul,

But it would have benefited immensely from a paragraph on fault tolerance.

Microsoft's msdn page refers to it explicitly...

http://msdn.microsoft.com/en-gb/library/ms189788.aspx

As table rows increase the chance of the "Birthday Paradox" increases...

Good Article Nakul,

But it would have benefited immensely from a paragraph on fault tolerance.

Microsoft's msdn page refers to it explicitly...

http://msdn.microsoft.com/en-gb/library/ms189788.aspx

As table rows increase the chance of the "Birthday Paradox" increases...

Good Article Nakul,

But it would have benefited immensely from a paragraph on fault tolerance.

Microsoft's msdn page refers to it explicitly...

http://msdn.microsoft.com/en-gb/library/ms189788.aspx

As table rows increase the chance of the "Birthday Paradox" increases...

Nice article, thank you.

So we can make a dynamic in clause for a standard query. But we can't for the pivot clause.

Why Microsoft, why?

Thanks for the feedback Mark,

I can look at my article a thousand times and not spot the typos. I just don't have an eye for it like others do.

Thanks again,

Gary

Hi,

Thanks for all your comments and feedback.

I guess that DAX is still new and that not everyone is immediately aware of its existence. I will perhaps include more back ground...

Hi,

Thanks for all your comments and feedback.

I guess that DAX is still new and that not everyone is immediately aware of its existence. I will perhaps include more back ground...

Hi,

Thanks for all your comments and feedback.

I guess that DAX is still new and that not everyone is immediately aware of its existence. I will perhaps include more back ground...

Great Article Perry,

Is it possible to achieve the same result using ORacle VM VirtuaBox instead of VM ware?

Thanks,

Gary

Hi Suresh,

Good article!

Is it really necessary to include the database name in all object references? I've always included schema.object but not database name as it's impossible to deploy the same...

To the plan cache guru's

Is it really necessary to include the database name in all object references? I've always included schema.object but not database name as it's impossible to deploy...

Great article Adam.

Regarding cross server merging. Isn't it best to use a ETL tool for ETL tasks, making use of in-memory caching, instead of a linked server?

Regarding checksum comparisons how...