Andy Steinke
My feedback
-
1,166 votes
This is something that we’ve had on our radar for some time, but haven’t been able to get it prioritized. Will definitely consider for future releases.
An error occurred while saving the comment Andy Steinke
supported this idea
·
-
296 votes
Thank you for filing this feedback item. We will evaluate this for the next major release of SQL Server.
Andy Steinke
supported this idea
·
-
66 votes
Thanks for your suggestion. We are looking into this scenario for a future release. 7350424
An error occurred while saving the comment Andy Steinke
commented
This would still be very useful! We can use extended properties to create standard descriptions for fields that can be leveraged across multiple tools. Thanks!
Andy Steinke
supported this idea
·
An error occurred while saving the comment Andy Steinke
commented
This can aid in situations where SQL Server extended properties have been used to provide similar exposure to metadata.
-
18 votesAndy Steinke
supported this idea
·
-
89 votesAndy Steinke
supported this idea
·
-
19 votes
Upvotes: 1
Andy Steinke
supported this idea
·
-
64 votesunder review · 5 comments · Azure Synapse Analytics » SQL/Table Structure · Flag idea as inappropriate… · Admin →Andy Steinke
supported this idea
·
I feel like the System 36/38/AS400 has had this for about as long as I've been alive (if we include the skunkworks time developing S/36)...Not every database is a wonderfully elegant overengineered with perfect integrity masterpiece.
Third party options in my past have been far less than performant, often requiring scanning a full backup and the scanning it again to retrieve the table. Is this really something that needs to be left to partners or can it be considered somewhat core functionality? In the real world, "restore full database" is not the base unit of restore. Thanks!