A report user would still want to see not only what items sold, but what did not sell all in the same view. So doing a right join (sales events...

As far as Primary Key (without Clustered Index) is concerned you MAY have it on a GUID or an Identity column (mostly preferred). But if you ask Primary Key...

I would not advise a GUID as a primary key. They are 16bytes in size last time I checked, have no fixed order, and a int or big int could...

One approach you can take is create your own surrogate key for all record and keep the customer key as its own column.

"Policy Number would make a decent clustered index...

With OLAP your dimension tables are typically wide and short compared to your fact tables (tall and narrow). Typically we add everything to the dimension if the attribute is a...

You can use a case statement  along with the functions Grant alludes to determine the column  datatypes. I hope you only have to do this once per column / per...

Data type disparity on join conditions etc is not really an after thought I've seen over time, its more like a 'no thought.' You bring up an excellent point that...

Dont forget any secondary replicas if you are using High Availability.

• This reply was modified 3 years, 11 months ago by MMartin1.

It would default to varchar(30) , but still to wide for a...

I dread the day that machines will not need to depend on us.

That comes down to machine learning. Basically showing a computer a bunch of picture of humans' faces. Computer is programmed to recognize the patterns acrosss all those pictures so when...

THank you for that piece of information. However my comment centered specifially on the post about inserting into multiple tables from one source , and how that can be done...

I would not fixate on sticking to one set based statement as I would to transactions. Each loop in a cursor can be thought of as a transaction . Where...

I've approached this type of situation , assuming I am deleting from the target table thouasnds of records that still would not make up a majority of the rows, using...

I found Erland Sommarskog's articles on SQL Error Handling very helpful. They are very detailed, and very long, but gave me a lot of reassurance that I understood all...