THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Greg Low (The Bit Bucket: IDisposable)

Ramblings of Greg Low (SQL Server MVP, MCM and Microsoft RD) - SQL Down Under

Auto-Injection of Enterprise Edition Features

This blog has moved! You can find this content at the following new location:

Published Friday, June 3, 2016 1:34 PM by Greg Low

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Cody said:

That's a good catch and sounds like something they just didn't think about.

June 2, 2016 9:38 PM

TiborKaraszi said:

Wow! Good catch.

June 3, 2016 3:00 AM

Brent Ozar said:

Greg, you are one of the most diligent and detail-oriented guys I know. Good catch, and you should totally put in a Connect item for this.

June 3, 2016 7:23 AM

Greg Low said:

Thanks Brent

June 3, 2016 11:37 PM

Tim McKay said:

Thanks for the post.

We / I have always just conceptualized the Dev edition as Enterprise, but way less cost for development.

From an application development thinking we have always built new databases and the schemas with DDL.  It would seem a best practice as the logical implementation doesn't break with a physical implementation dependency.  The application is doing application things and the database is doing database things.

June 4, 2016 11:28 AM

Kevin Fries said:

This is silly but it had me intrigued.

"The history table is created as a rowstore table. PAGE compression is applied if possible, otherwise the history table will be uncompressed. For example, some table configurations, such as SPARSE columns, do not allow compression."

I wouldn't be surprised if that shows up for an answer on any connect item opened.

June 4, 2016 8:56 PM

Leave a Comment


This Blog



No tags have been created or used yet.


Privacy Statement