AlwaysOn is a great idea IN CONCEPT.  If someone suggests this to you, do yourself a favor and take Brent Ozar's quiz (link below).  Brent is one of my favorite...

Hey Sean,

A few thoughts...columnstore indexes are all about performance.  They are great in a warehouse context (or even OLTP context - see link below) where we need to...

Just an opinion on this...for me, this is getting a bit complex.  I wonder if there is a simpler way to accomplish what you are needing.  Have you thought about...

First, a word of caution.  In some contexts, using sub-reports can introduce significant performance degradation. I have found that it's better to use 1 query and group results in a...

Not sure if I understand what you are trying to accomplish, but have you thought about the execution log?  It's in the report server database (dbo.ExecutionLog3).  

Here is a...

Hey Roxanne,

The MCSA is a great start. It's 2 exams. I have been working a ton with SQL Server since SQL Server 2005. I recommend...

Just curious...why wouldn't you just have a calendar table that went so far into the future that you would never have a problem with a missing value?

You all are quick!
If someone hasn't already shown the correct answer, check this out.  It's not complete because I'm out of time, but it's a start.

First, I'd...

tough with set-based logic...thinking about it.

would be easy with CLR.

I personally prefer to use a stage table with a GUID column to stage all data before they load into the warehouse.  This way I can identify bad data, keep it staged,...

Hey Neil,

Sure would be nice to see the actual parameter data (labels and values) as well as some of the procedure code, but I understand you can't provide that.

Hi,

What are you doing to avoid SQL Injection?

Hi Kavita,

Your question doesn't fully cover all that you are trying to accomplish.  Before addressing the question, I have a question for you (since you are interested in SSIS package). ...