Some time ago I noticed Adam Machanic had written a post titled The SQL Hall of Shame. In it, Adam notes there are features that Microsoft will introduce in SQL Server and then let die. These are the useless features that aren't widely used, or even useful for many projects. You can read his list, and agree or disagree.
I think there certainly are some features that were silly experiments and I wish they had been introduced as experimental, or beta, features early, allowing users to give feedback on whether they're useful and where they need refinement. I certainly think too many resources were initially wasted on items like MDW and Query Notifications, and far too little investment later. These days I think we'll see more early releases of items in Azure where users can experiment and provide feedback to help Microsoft decide if more investment is needed. At least, that's my hope.
Today I'm wondering if you think there are features in SQL Server that do need more attention. Those features you use, but appear forgotten and you'd hope they are improved in the next version.
For me, I certainly wish replication would get more attention, tooling, and resilience. I'm not sure if this needs an overhaul, like SQL Server 2005 was, or there just needs to be some reworking of the code, but in today's distributed world, we need a more reliable way to hook up portions of databases and move data around. Not ETL, not Availabilty Groups, a better replication architecture and implementation.
There might be other features you use or want, but let me know today. What's a not useless feature that you want improved.
The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music.
SQL Clone: Now supporting databases up to 64TB
Create copies of production databases and SQL backups in seconds and save up to 99% of disk space using SQL Clone. Redgate’s new tool removes much of the time and resource needed to create and manage database copies, allowing teams to work on local environments to develop, test and diagnose issues faster. Try it free
The industry standard for comparing and deploying SQL Server database schemas
Trusted by 71% of Fortune 100 companies, SQL Compare is the fastest way to compare changes, and create and deploy error-free scripts in minutes. Plus you can easily find and fix errors caused by database differences. Download your free trial
This article serves as a ‘first look’ at cloning databases with SQL Clone. It will review some of the database provisioning challenges that we seek to overcome, explain briefly how SQL Clone works, and then walk through a simple example of cloning a database. More »
SQL Server works well, and Microsoft does everything it can to keep it relevant and competitive: As with everything in real life, it doesn't don't always get it completely right, and Rob Sheldon continues his quest through the jungle of past features to rediscover and explore the ones that time forgot. Here, he comes across Lightweight Pooling, XML Indexes, Stretch Databases, SQL Variants, Transaction Savepoints and In-Memory OLTP. More »
In show #84 of the SQL Server Radio Hebrew Edition, Matan and I talked about how to calculate running totals in SQL... More »
Question of the Day
Today's Question (by Evgeny Garaev):
How many indexes can be created on a Memory-Optimized Table if you use SQL Server 2016?
Think you know the answer? Click here, and find out if you are right.
We keep track of your score to give you bragging rights against your peers.
This question is worth
1 point in this category: Memory-Optimized Tables.
We'd love to give you credit for your own question and answer.
To submit a QOTD, simply log in to the
Design and configure SQL Server instances and databases in support of high-throughput applications that are mission-critical and provide consistent response times in the face of variations in user numbers and query volumes. Learn to configure SQL Server and design your databases to support a given instance and workload.
Pick up your copy of this great book today at Amazon today.
Yesterday's Question of the Day
(by Steve Jones):
I am looking to add some documentation to my database by using extended properties. I want to add a property with these parameters:
Property Name: IsExternalAPI
Property Value: 1
to the dbo.SalesOrderHeader table. I decide to run sp_addextendedproperty with this code:
The problem with this code is that the level0type is invalid. Schema is the correct type here. Others are: assembly, contract, Event notification, filegroup, message type, partition, function, partition scheme, remote service binding, route, service, user, trigger, type, plan guide, and NULL.
Once this is fixed, the level1 values would be what is shown for the level0 values. The correct code is:
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.