Niko Neugebauer
My feedback
-
31 votesNiko Neugebauer
shared this idea
·
-
802 votesunplanned ·
AdminSQL Database feature voting forum admins
(Product Owner, Microsoft Azure)
responded
This is not currently planned at this time. Will keep this item open for voting and comments.
Niko Neugebauer
supported this idea
·
-
931 votesunplanned ·AdminSQL Database feature voting forum admins
(Product Owner, Microsoft Azure)
responded
Not planned at this time. Will keep this item open for future review.
Niko Neugebauer
supported this idea
·
-
1 voteNiko Neugebauer
shared this idea
·
-
9 votesNiko Neugebauer
supported this idea
·
-
225 votes
Upvotes: 127
<=-=Jun 23 2015 8:37AM=-=>I’m the first to post a useful comment. This must make me special.
Seriously though, this would be an excellent solution to having to create a new “scratchdb” to hold my interim ETL data. This would be a major plus in simplifying design of a high performance app.
<=-=Jul 3 2015 5:04AM=-=>In 2014, memory optimized tables, and delayed durability can be used help mitigate these Issues. However neither of this are always completely viable solutions. Brent’s proposed solution is likely the simplest way to achieve this with the least amount of unwanted impact. It is important to note that other platforms implement similar functionality as well. Notably Oracle.
<=-=Nov 29 2016 3:58PM=-=>There are so many good things about this suggestion. I am amazed that SQL does not have the capability to turn off logging for certain tables that you define as no…
Niko Neugebauer
supported this idea
·
-
295 votes
Upvotes: 42
Niko Neugebauer
supported this idea
·
-
272 votesNiko Neugebauer
supported this idea
·
-
432 votesNiko Neugebauer
supported this idea
·
-
112 votesNiko Neugebauer
commented
More details on the suggestion can be found at my blog - http://www.nikoport.com/2019/01/05/optimise-for-analytics-should-be-a-database-configuration-option/
Niko Neugebauer
shared this idea
·
-
4 votesNiko Neugebauer
supported this idea
·
-
14 votes
Upvotes: 33
<=-=Sep 12 2017 1:42AM=-=>From an ISV perspective, adding this capability would add value to the development process for newer versions where feature flags are in use in the application layer controlling access to new experimental features.
Niko Neugebauer
supported this idea
·
-
34 votesNiko Neugebauer
supported this idea
·
-
21 votesNiko Neugebauer
supported this idea
·
-
14 votes
Upvotes: 1
Niko Neugebauer
supported this idea
·
-
1 vote
Upvotes: 2
<=-=Dec 27 2016 3:57PM=-=>Hi,
Thank you very much for your feedback! We are aware of the issue that column store index and transaction replication don’t work together. We will consider to add the support in future version of SQL Server. Please keep following our blogs or announcement to get the latest update!Regards,
<=-=Dec 27 2016 3:57PM=-=>
XiaochenHi,
Thank you very much for your feedback! We are aware of the issue that column store index and transaction replication don’t work together. We will consider to add the support in future version of SQL Server. Please keep following our blogs or announcement to get the latest update!Regards,
<=-=Jun 12 2017 4:12PM=-=>
XiaochenKerido: what is your scenario where you need to replicate CCI? Assuming you are looking to scale out a DW workload? Have you consdered AlwaysOn with mutliple Read-enabled replicas?
Thanks
SunilNiko Neugebauer
supported this idea
·
-
1 vote
Upvotes: 1
Niko Neugebauer
supported this idea
·
-
105 votesNiko Neugebauer
supported this idea
·
-
307 votes
Upvotes: 8
<=-=Mar 5 2017 2:42PM=-=>Thanks for this idea. This is a valid requirement and I hope that it will get more votes. Currently we cannot confirm when it will be added, but it is in our backlog.
<=-=May 22 2017 5:03AM=-=>would like it very much, particularly since you already have the CONCAT / GREATEST() a variable number of paramenters and does something with it…
<=-=Jun 5 2017 12:31PM=-=>GREATEST / LEAST functions would be fantastic addition.
<=-=Nov 14 2017 3:42PM=-=>The workarounds using CROSS APPLY or CASE expressions are difficult to manage and read. I’d love to see these implemented.
Niko Neugebauer
supported this idea
·
-
158 votesNiko Neugebauer
supported this idea
·
Hi Matteo,
the point in this request is ALLOW updating the statistics on the secondary in the future.
My blog post was exactly on how to do this now (but rather on smaller tables).
I have previously spoken with the PMs responsible for the respective features (Sourab, Joe) and even Engineering Manager (Gjorgji) and all of them thought that it would be an interesting feature to consider.
Best regards,
Niko