Probably best to stick to standard replication; this has better performance overall than using...

Yeah,...

Hi Jeff, I managed (I think) to read my way through not only the update to an excellent article but the subsidiary commentary and the code fallout. Now I...

Is there a reason you're avoiding dynamic SQL? That seems to be the easiest solution.

If you go through sys.objects, that will give you a list of objects by type...

Some great advice from Tom! 🙂

In general, I've found that the language or notation or convention in which you do your modelling is less important than the process and...

Check the default language for the SQL Server login...

I can think of several ways to do this.

The first is to reflect the design into SSAS, and let the cube handle the security. While I'm only an SSAS...

I had a "near real time" dashboard that was grabbing data every ten seconds. Now that was insane! 😀

I'd agree with the earlier posts about just doing the...

I like the idea of unknown versus undefined at source. I stay away from using zero (although I have done so in the past), as zero is often a...

You may need a time dimension (it's a bit of a modellers choice, and I'd probably err with just storing the time as part of the fact).

I would also suggest...

I think in most ways you've answered your own question. Another name for "facts" is "measures" (this is the name that SSAS uses.)

Personally, I would pull them out and...

As a general rule, I go with "don't store different things in the same container". Your case is a little confusing, as I don't know how the data is...

Is there a reason why you don't have an employee dimension? That way...

40gb of tempdb isn't a lot (even if it's on SSD). For even a relatively small DW (say, a couple of TB in size), I generally aim for around...

It's a good start, but I would recommend you investigate the "merge" command. I'd also suggest that writing joins as "cross joins" (rather than "inner joins") where there is...