Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

SQL Server

Microsoft SQL Server powers your entire data estate by supporting structured and unstructured data sources. It builds on previous versions of SQL Server, which have been industry leading for four years in a row and a leader in TPC-E. It scales to petabytes of data and allows customers to process big data through PolyBase using T-SQL over any data. SQL Server has also been the least vulnerable database during the last seven years. SQL Server brings data insights with business intelligence capabilities that provide analytics at a fraction of the cost on any device along with advanced analytics with support for R and Python.


More details about SQL Server are available in the SQL Server documentation.
If you have a technical issue, please open a post on the developer forums through Microsoft Q&A or Stack Overflow

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add MSBuild predefined Targets for "BeforeSqlBuild" and "BeforePublish" to SSDT SQL Server Database Projects

    Sometimes, especially when working with SQLCLR objects, it is useful to manipulate the DLL / assembly and/or the generated deployment DDL T-SQL prior to the publishing process taking over. MSBuild allows for easily overriding Targets, but for some reason the SSDT workflow (found in C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets ) doesn't have any predefined Targets that are a natural fit for this.

    For example, it's difficult to sign SQLCLR assemblies with a certificate due to the assembly being converted into string format for inclusion in the Create and/or incremental publish script before the PostBuild event executes. This was ok due to signing…

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make Latin1_General_(100)_CI_AS the default collation for US English

    This description is identical with:
    https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=357973

    When installing SQL Server you need to select a server collation. However, Setup permits you to go with a default. This may seem convenient, but it often backlashes, because the default is unsuitable for a number of reasons.

    A real-world case: I was contacted by a guy who was fearing for his job, if he could not get some speed out of his database. The query he show me was a simple lookup the PK. The problem was that the application (using Java in Websphere) worked with Unicode, but the table had varchar keys.…

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 10

    <=-=Aug 6 2008 10:15AM=-=>

    Hello,

    Thank you for sharing your ideas. As you say this one is somewhat less revolutionary than not having a default collation at all; you’re also right that the major obstacle in doing it is a back-compat. That being said the idea is still being discussed. I will keep you informed on the results of the discussion.

    Thanks,
    Krzysztof Kozielczyk

    <=-=Aug 6 2008 12:07PM=-=>

    I would be intrigued to know, what exactly is this backwards compatibility issue about? The only I can think of is existing scripts for unattended install, but I would expect such scripts to require modifications for new versions of SQL Server anyway. Is there something I have overlooked. I would appreaciate if you could details this, either here, or via private note over email.

    <=-=Mar 17 2011 11:24AM=-=>

    Hello Erland,

    Thank you for submitting this suggestion, but we’re trying to…

  3. Enable SQL Agent Proxies to run T-SQL Job Steps

    It is not possible to run a T-SQL job step under a SQL Agent Proxy. This has an impact on how security is managed since one undesirable answer is to grant more rights than originally specified.

    If the cumbersome workaround below is used, it makes the deployment of the job more complex. It is possible to run the T-SQL through Operating System or Powershell steps. Often this means deploying a script to the file system that can be run. As follows:

    SQLCMD -Q"EXEC StoredProcedure" -E -S Servername
    SQLCMD -i \someplace\script.sql -S sqlserverinstance -E

    However, this approach is not symmetrical in…

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 86

    <=-=Dec 27 2010 12:13PM=-=>

    Hello Russell

    Thank you for proposing a new DCR for SQL Agent. We are always looking forward for the customer feedback. We will consider your proposal in one of our future releases.

    Thank you
    Alex Grach

    <=-=Jan 25 2011 5:04PM=-=>

    This functionality seems essential. Why won’t there be a SQL Agent Proxy? In many scenarios there is a Service Account under which all things run and that service account is normally a domain account – which may or may not have permissions to run SQLCMD or Powershell etc.

    <=-=Jan 25 2011 5:08PM=-=>

    Besides, if we run SQLCMD and the Sproc or Query errors out, the job agent steps still are marked successful. There is not robust error handling mechanism using SQLCMD from the Job Agent

    <=-=Mar 23 2011 1:23PM=-=>

    Although it is possible to “simulate a proxy” by granting impersonation rights to a proxy…

  4. ALTER COLUMN IDENTITY

    Provide an ALTER COLUMN syntax to add or remove the IDENTITY property of a column. This will allow an IDENTITY to be changed without dropping and recreating the table.

    This is not only a convenience but is actually important for some scenarios:
    1. Suppose the SELECT INTO was used to create the table. SELECT INTO is fast, but subsequently recreating the table just to setup the IDENTITY negates a lot of SELECT INTO's speed.


    1. If the table is involved in replication, it is not possible to drop and recreate it.

    A similar suggestion in Microsoft Connect involves the ability to…

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 27

    <=-=Jan 28 2008 6:27PM=-=>

    Hello

    Thank you for your feedback. The ability to modify the identity property of an existing column will certainly benefit the scenarios you’ve described. We’ll look into ways of enabling these scenarios in a future release of SQL Server.

    SQL Server Engine Team

    <=-=Jan 28 2008 6:28PM=-=>

    Hello

    Thank you for your feedback. The ability to modify the identity property of an existing column will certainly benefit the scenarios you’ve described. We’ll look into ways of enabling these scenarios in a future release of SQL Server.

    SQL Server Engine Team

    <=-=Jan 1 2011 2:09PM=-=>

    Any update on this? It seems pretty ridiculous that the only way of changing a column to be an identity column is either to add a new column and drop the existing one (necessitating an update to every row in the table, wasting space from the dropped column…

  5. Support FOR Openjdk JRE in SQL Server 2017 instead of Oracle JRE

    Currently Oracle JRE 7/8 is a prerequisite for Polybase installation in SQL Server 2017. With change in JAVA support by Oracle, it will be good to support the OpenJDK JRE (or IBM JRE) and provide customers with a whitepaper on how to migrate

    Note : Microsoft is a platinum sponsor of OpenJDK

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  6. SSIS 2012 Execute Package task: External Reference does not work with SSISDB

    There are currently two options within the Execute Package Task to execute child packages: Project Reference and External Reference. The problem with project reference is, that all packages need to be within the same SSIS projects. This is an issue for large projects, because it also affects the deployment. But when I switch to External Reference combined with SQL Server, I can not see the SSIS packages which are deployed in the new SSIS db, when I choose the SSIS DB as source.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 118

    <=-=May 23 2013 1:06PM=-=>

    Hello Marcel. We�ve looked into this item. While it will not be addressed in the current release cycle, we have added it to a list for consideration for the next. Thank you for the feedback. We will keep track of the suggestion. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)

    <=-=Jun 5 2013 2:05AM=-=>

    Is there a workaround available? How can I start a task deployed to a server from another SSIS task?

    <=-=Aug 1 2013 10:11PM=-=>

    Now that the DTS functionality is back for passing parameters to child packages, it allows for easy building of SSIS frameworks with reusable child packages. But with the all or none deployment model, it is challenging to manage large projects with multiple developers, especially since the slightest change to any package in the project updates the project file. Because of this, it’s easier to break…

  7. ubuntu 20.04

    Please make packages for ia-64 (x64) for ubuntu 20.04 LTS.

    Please make packages for ARM64 (aarch64) for ubuntu 20.04 LTS.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Publishing SSMS in other Languages then English in WSUS

    Pls publish SSMS 18.x or higher in other Languages then English in WSUS. This will be very helpfull for People/Admins in Europe.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Test the SSDT with new Versions of Visual Studio before releasing them to the public.

    TITLE: SQL Server Integration Services

    Could not load file or assembly 'Microsoft.SqlServer.Management.IntegrationServicesEnum, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)


    ADDITIONAL INFORMATION:

    The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)


    BUTTONS:

    OK

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  10. sql 2017 reporting services self migrate from previous versions

    Update reporting services standalone installer to self migrate from earlier versions of reporting services. The process is currently a real pain as it takes a lot of extra work to move to the latest SQL reporting services when the previous versions just upgraded it in place.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  11. The Deployment Utility (Microsoft.AnalysisServices.Deployment.exe) should return a non-zero exit code on error

    It would be extremely helpful if the Deployment Utility/Microsoft.AnalysisServices.Deployment.exe http://msdn.microsoft.com/en-us/library/ms162758%28v=SQL.105%29.aspx would return a non-zero exit code on error.

    A little bit of background on what we're trying to do:
    We've automated the generation of the Deployment Script as a part of our build processes using MSBuild:

    <Exec Command='"$(AnalysisServiceDeployTool)" Some.asdatabase /s:somelogfile.log /o:SomeOutput.xmla /d'

          WorkingDirectory=&#39;$(AnalysisServicesTemp)&#39;/&gt;
    

    The Exec Task relies on the Exit Code* to determine if the task failed or not, however it appears that the Deployment Utility will not give a non-zero exit code on failure, resulting in the Exec task assuming that it was successful.

    *This is not a 100%…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 14

    <=-=Sep 9 2012 9:55PM=-=>

    Thank you for your feedback. We will be investigating your proposed suggestion as part of the planning efforts for the next major release. If we have more questions as the planning process progresses we will get back to you

    Thanks
    The Analysis Services Team

    <=-=Nov 17 2012 1:33PM=-=>

    This is extremely disappointing and very important. You guys know any win32 process should NEVER return 0 on failure. Please make this a priority, it is critical to continuous delivery and automated builds with tabular and multidimensional models. We currently have no way of knowing whether this step of the build was successful or not without inspecting the build log manually on every build!!!

    <=-=Sep 22 2016 10:00AM=-=>

    Four years later – has anything changed? That this utility simply exits without an error indication when something goes wrong is troubling.

  12. SSDT overly strict with whitespace and special characters for default values, computed columns and filtered indexes, causing endle

    When SSDT publishes to a database, the deployed sql may be syntactically different to the source, in that the deployed sql may have individual names surrounded by square brackets if they didn't already, spacing may be different, etc. In these cases, irrespective of the Ignore Whitespace setting, these differences are ignored by subsequent publishes. It must be correct for these differences to be ignored, as otherwise SSDT would always want to deploy these changes, which are imposed by SSDT downstream of the project's table definition, on every publish.

    However, there are three cases I've found where SSDT does not ignore…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  13. SSDT VS2017/SQL2017 hard coded database reference

    The SSDT 2017 "15.3.0 preview" build targeting a SQL 2017 instance is hardcoding path information the SQL project files instead of using relative a path. We identified this when one developer added a project reference to the master database via VS2017 Enterprise Edition followed by another who attempted to compile the code using VS2017 Professional edition as the path information to master.dacpac is different between the two installs. When we looked at a similar setup in a project using SQL 2016, the entry is using a relative path controlled via a command variable.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add function to extract Asymmetric Key similar to CERTENCODED for Certificates (SQLCLR / SSDT)

    Currently we are able to extract the public and private keys of a Certificate via CERTENCODED ( https://docs.microsoft.com/en-us/sql/t-sql/functions/certencoded-transact-sql ) and CERTPRIVATEKEY ( https://docs.microsoft.com/en-us/sql/t-sql/functions/certprivatekey-transact-sql ). However, we cannot extract even the public key of an Asymmetric Key.

    This presents problems for SSDT when importing a database, and it makes it much, MUCH harder to work with the new "CLR strict security" server configuration option ( https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/clr-strict-security ) of SQL Server 2017 if the goal is to NOT rely on any external files (DLL or SNK) when publishing an Assembly. And this is definitely the goal of SSDT and any reasonable project…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  15. MSIX installer for SQL Management Studio

    Would be great to get the SSMS installer in a Microsoft-issued MSIX package to simplify deployment with SCCM or Intune.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Rebuild packages for new Ubuntu/Debian/... releases

    Current the sql server packages (both the [server](https://feedback.azure.com/forums/908035-sql-server/suggestions/34175752-sql-server-won-t-install-on-linux-ubuntu-18-04-due) and the tools/odbc packages [(see comments)](https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-2017) don't install on ubuntu bionic due to some depedency problems.

    It would be nice if you could rebuild the packages and add them to the bionic repository.

    (the same should happen if there is ana new Ubuntu/Debian/Red Hat release...)

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Database projects - Native support for one time DML migration scripts

    It would be nice to have a built in capability in SSDT database projects to be able to save pre or post deploy scripts in the project that will only ever be executed a single time per environment when deployed. I know you could hand roll a custom solution that would make this possible and 3rd parties like Redgate offer similar functionality. Database projects already have functionality close to this with the refactorlog in that they will track what refactor operations have been deployed to a certain environment and only execute them once; it would be nice if we could…

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Error updating temporal tables

    We have implemented the System Versioned Temporal Tables on the table "Orders". The application is using different access patterns to modify the data in this table. There are direct statements coming from the application or the application is running long batches in explicit transactions where it makes several changes to multiple tables. The update on the "Orders" table is not the first statement in those long batches! So, sometimes we are facing the following error.

    Data modification failed on system-versioned table "Orders" because transaction time was earlier than period start time for affected records.

    Apparently this is a standard behavior…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  19. SSIS Dedicated Installation

    SSIS is clearly a developer/ETL tool that is not dependent on the SQL Server database engine. We actually don't install Integration Services on our database servers. Many times we hand-off the installation to the LOB teams to install on their dedicate SSIS servers. It's time to decouple, separate SSIS from the SQL Server Installation. Just like SSRS, SSIS needs to be a standalone product installation.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  20. SSMS SSIS .ispac deployment previous SQL versions doesn't work

    SSMS is not usable for deployment of SSIS .ispac files to older SQL versions. The import project wizard seems to automaticly upgrade all SSIS packages even if the .ispac is created for the correct target platform.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base