SQL Server

Microsoft SQL Server 2017 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 2017 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 Stack Overflow or MSDN.

Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. SSDT for Visual Studio 2017 - Include as part of the VS 2017 Installer

    Can we please pass over the SSDT components to the Visual Studio team so this can be included as part of the Visual Studio 2017 installation process?

    The VS team can then build out the installer in a way that SSDT is always compatible with their latest build and installer. We've been stuck with the break fix break fix loop with SSDT and incompatibility with VS upgrades for too long now. The SSDT team doesn't respond quickly enough, the latest example being SSDT 15.6/VS 2017 15.7.x installation issue, why are we waiting so long for an installer update?

    65 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      under review  ·  3 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    • Maintenance Plan Portability

      Maintenance Plans should be scriptable, deployable and maintainable without the need to manually create/update a plan on each server/instance. Current functionality requires the DBA to manually generate a SQL Maintenance Plan one at a time for each instance in the environment. Built in SQL Maintenance Plans should be scriptable, deployable and maintainable with TSQL or in some automated fashion that will allow deployment to large enterprise environments that do not require the use of a GUI.

      52 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        under review  ·  7 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
      • Restore multiple instance support for Reporting services in SQL 2017

        Please restore the multiple instance support per server for Reporting Services 2017. SQL Server reporting Services has supported multiple instances on one server in versions SQL 2000 thru 2016 and it was removed by design with the release of SQL 2017. This was a bad move as it will force my company to deploy 6X as many servers to deploy what is a lightweight application server.

        I'm not sure if this has anything to do with the PowerBI integration with SSRS, but it also suffers from this bad decision as well.

        Best Regards,
        James Fuller
        James.fuller@amwins.com

        32 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          under review  ·  6 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
        • Ability to upgrade SQL Server Management Studio directly from About menu

          I think it will be really cool to update the management studio directly from the about menu when it is open and also it for checking for new versions and notify us.

          Thanks in advance

          25 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            4 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →

            We have a “Check for updates link” in the Tools menu today, and SSMS prompts you to upgrade when it detects a new version unless you have turned off auto-check for updates. We have no plans to further automate these updates. We are pushing more updates through WSUS for enterprise installations.

          • SQL Server 2017 Installer should recognize Java JDK 9

            SQL Server 2017 Installer should recognize Java 9

            15 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              2 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
            • Allow Asymmetric Key to be created from binary hex bytes string just like CREATE CERTIFICATE (SQLCLR / SSDT / Module Signing)

              Creating an Asymmetric Key (for the purpose of creating an associated Login to provide { EXTERNAL ACCESS | UNSAFE } ASSEMBLY permission for SQLCLR Assemblies and hence avoid setting TRUSTWORTHY ON) requires a file or EKM provider or Assembly. Prior to SQL Server 2017 it was at least possible to load an Assembly (marked as SAFE) that is signed with the same private key into [master] to then create the Asymmetric Key from, and then drop the Assembly.

              But, with SQL Server 2017, ALL Assemblies will require being signed with a matching key / cert -based Login having the UNSAFE…

              14 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
              • Move SSMS and Updates into WSUS

                I want to control SSMS and updates via WSUS. Please add to the catalog for importing or add to Products under SQL Server in the WSUS catalog.

                11 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  2 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                • Unable to setup Managed Backup on SQL 2016 using Azure SAS credential

                  When attempting to setup Managed Backup on a SQL 2016 (RTM or CU1) while using an Azure SAS credential, during the setup call to "EXEC msdb.managed_backup.sp_backup_config_basic", it fails with the following error:

                  Msg 45207, Level 17, State 17, Procedure sp_add_task_command, Line 102 [Batch Start Line 33]
                  The operation failed because of an internal error. Value cannot be null.
                  Parameter name: sasToken Please retry later.
                  at Microsoft.WindowsAzure.Storage.Auth.StorageCredentials..ctor(String sasToken)
                  at Microsoft.SqlServer.SmartAdmin.SmartBackupAgent.FileService.VerifyContainerURL(String containerURL, SqlConnection conn)
                  at Microsoft.SqlServer.SmartAdmin.SmartBackupAgent.SmartBackup.ConfigureDbOrInstance(SmartBackupConfigParameters config, LogBaseService jobLogger, SqlConnection conn)

                  Additionally, reviewing the SQL Server AGENT LOG, shows the following error that is occurring the creation of the managed job.

                  [442]…

                  8 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

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

                    Upvotes: 30

                    <=-=Oct 15 2016 1:20PM=-=>

                    So based on the following documentation container_url needs to be a SAS url.

                    https://msdn.microsoft.com/en-us/library/dn833120.aspx?f=255&MSPPError=-2147217396

                    That said, I have performed all the steps in this document

                    https://msdn.microsoft.com/en-us/library/dn449491.aspx

                    I have in fact provided my SAS url as the container and get the following error.

                    Msg 45207, Level 17, State 6, Procedure sp_add_task_command, Line 102 [Batch Start Line 0]
                    SQL Server Managed Backup to Microsoft Azure cannot configure the default backup settings for the SQLServer instance because the container URL was invalid. It is also possible that your SAS credential is invalid.

                    I used the new-azurestoragecontainersastoken cmdlet to create a sastoken for the conatiner itself. I have also tried this using the sas tool in the azure portal, this creates a token for the account itself, this fails as well.

                    <=-=Oct 15 2016 1:56PM=-=>

                    Still working this and when I ran the script below

                    EXEC msdb.managed_backup.sp_backup_config_basic
                    @enable_backup…

                  • 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.

                    6 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      4 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                    • 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...)

                      5 votes
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        under review  ·  0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                      • SSDT: Within the Schema Compare to be allow to select publish profiles to resolve SQLCMD variables when comparing schema

                        Compare the database project against the SQL Server Database with code that uses SQLCMD variable, to allow different settings at deployment time, always show up as different because of the SQLCMD variable.

                        Which can cause problems when reserve engineering as the schema compare tool would remove the SQLCMD and cause problems when deploying to the others environments. Also miss-inform users that the object has drifted from the project when trying to manually investigate project and database drift.

                        5 votes
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

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

                          Upvotes: 12

                          <=-=Apr 9 2014 7:43AM=-=>

                          This is a significant reason why I have not yet adopted SSDT as my primary database development platform. I use this functionality extensively in VSDB projects.

                          <=-=Apr 9 2014 8:16AM=-=>

                          I want to convert my VS2010 DB projects to SSDT and the SQLCMD variable issue is definitely a hindrance.

                          <=-=Jul 3 2014 3:57AM=-=>

                          Schema Compare is practically unusable as is if you use SqlCmd variables and have multiple environments that you deploy to (i.e. dev, uat, live etc)… which is exactly the case that ssdt is designed mostly for.

                          <=-=Oct 2 2014 11:04AM=-=>

                          Hello all,

                          Thank you for submitting this feedback and adding the comments. We are evaluating this request and will update you when we have more information.

                          Xiaoning Ding
                          SQL Server Tools Dev Team

                        • 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…

                          5 votes
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                          • 4 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              under review  ·  1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                            • 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…

                              4 votes
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                0 comments  ·  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…

                              • GRANT EXECUTE ANY EXTERNAL SCRIPT not recognised by SSDT

                                Hello,

                                The permission GRANT EXECUTE ANY EXTERNAL SCRIPT is not recognised by SSDT therefore makes dacpac deployment of a project using R (and I guess Python too) services a hassle.

                                This is broken in all versions of SSDT up to and including 17.3.

                                4 votes
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                                • 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…

                                  3 votes
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Set the Maximum Size of the SQL Server Error Logs

                                    In SQL Server 2012 and later versions, you can use xp_instance_regwrite to set the maximum size of individual error logs. Please make this setting available via SMO, instead of having to use xp_instance_regwrite.

                                    Documentation for this feature can be found here: https://support.microsoft.com/en-us/help/2199578/how-to-manage-the-sql-server-error-log

                                    3 votes
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                                    • DacFx support of ignore schemas

                                      There are case where users/customers can work on a own schema in a database to create tables and other objects. These objects are not included in a Dacpac, so they where dropped if the dacpac package is deployed.
                                      Please provide a parameter to exclude/ignore 1 or more schemas from deployment process.

                                      3 votes
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        under review  ·  0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                                      • 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…

                                        3 votes
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                                        • 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…

                                          3 votes
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                            2 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3 4 5 21 22
                                          • Don't see your idea?

                                          SQL Server

                                          Feedback and Knowledge Base