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. CREATE OR ALTER is not fully supported in Transactional Replication DDL commands

    We've been having trouble with some objects not replicating correctly after a DDL change.

    When a published function or proc is altered, the following appears to happen:
    A database trigger is called: tr_MStran_alterschemaonly
    Which calls a proc called: sys.sp_MStran_ddlrepl - This proc will output debug IF MSrepl_debug_DDL exists (create anything called this!)
    which calls a function: master.sys.fn_replgetparsedddlcmd, which is designed to return the ddl after the object's name, to be used for generating the command to be applied 
    at the subscribers.

    SQL Server BOL states that ALTER is supported (https://docs.microsoft.com/en-us/sql/relational-databases/replication/publish/replicate-schema-changes?view=sql-server-2016)

    However, this doesn't appear to be the case:

    (13.0.4451.0):…

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add support for OVER (ORDER BY) for CLR Aggregate functions

    Currently, there is no way to specify aggregate function processing order - and, indeed, the IsInvariantToOrder property of the SqlUserDefinedAggregate attribute has no effect.

    This can be important for string concatenation aggregates, as the strings may have to be aggregated in a specific order. The ability to use a clause such as:

    SELECT dbo.StringConcatenate(StringValue) OVER (ORDER BY ID) FROM dbo.MyTable

    This would mean that you could support better forms of aggregation, and that other aggregates could be implemented in a more succinct way (for example, a median aggregate could benefit from knowing that input was ordered).

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 36

    <=-=Oct 8 2010 11:58AM=-=>

    Hi Matt,
    Thanks for your feedback. We will consider it for a future version of SQL Server. Please note however that the syntax you are proposing doesn’t achieve what you are looking for. The ORDER BY within OVER clause controls the ordering of the window and not the order of rows to the aggregate. We support OVER clause (excluding ORDER BY clause since we don’t have it) already for CLR aggregates. So if we extend OVER clause to support ORDER BY it will work with existing CLR aggregates also.
    ANSI SQL:2008 and earlier has a feature called ordered set functions that use a WITHIN GROUP specification. One such aggregate is PERCENTILE_CONT which looks like:

    PERCENTILE_CONT( ) WITHIN GROUP (ORDER BY )

    Once we support the above syntax for ordered set function, we will consider extending the CLR Aggregate contract to do the…
  3. SQL Server 2008 Database Audit on INSERT UPDATE and DELETE actual SQL and not parameter values

    If a database Audit Specification is created for a table object on SELECT, INSERT UPDATE and DELETE and the Transact SQL to perform the SELECT, INSERT UPDATE or DELETE contains a parameter, then the parameter is shown in the Audit Log instead of the parameter value.

    For example, executing the following TSQL statement:

    INSERT INTO [config] VALUES ('test','1234')

    creates an audit entry:
    ..
    object_name:config
    statement:INSERT INTO [config] VALUES ('test','1234')
    ..

    However, executing the TSQL:

    DECLARE @stat1 varchar(10)='test'
    DECLARE @stat2 varchar(10)='1234'
    INSERT INTO [config] VALUES (@stat1,@stat2)

    Creates the audit entry:
    ..
    object_name:config
    statement:INSERT INTO [config] VALUES (@stat1,@stat2)
    ..

    In order for…

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 54

    <=-=Nov 29 2010 8:49AM=-=>

    Hi,

    First of all, thank you for your feedback!

    This is a great suggestion to improve the SQL Server Audit experience and we will try to consider this in our future release planning.

    Thank you and regards,
    Don Pinto
    SQL Server Engine

    <=-=Jul 29 2011 9:58AM=-=>

    I can’t believe there aren’t more comments on this subject. I assume it’s simply because not many are currently using the auditing system, likely one reason is due to the limitation described here.

    It seems like a logical step to include parameters within the additional_information field (which appears completely unused with regard to table level events). Perhaps this was overlooked due to performance issues?

    While I’m on the topic, and understanding that CDC is NOT necessarily to be used for auditing, it seems odd to me that the information regarding WHO did something is not included with the…

  4. 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…

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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…

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

    2. 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…

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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…

  6. Allow Sub Folders in SSRS Projects

    I think that it would be great if we could create sub folders under the Reports folder of a SSRS project in BIDS so that if we needed to create folders for our reports on the Report Server we wouldn't have to keep them in separate projects with separate data sources.

    I know that we can have multiple projects in a single solution, but this is just a work around. I've got a dozen projects in a single solution in BIDS and when I make changes to reports in different folders that are related but for business reasons are in…

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 309

    <=-=Feb 2 2012 2:12PM=-=>

    Additionally, having a hidden folder for sub reports would be a BIG improvement. I can do it in Report Builder, but not in Visual Studio. That is BACKWARDS. Give the developer more power than the end user, not LESS! The current limitations are very counter productive.

    <=-=Aug 6 2012 3:04AM=-=>

    47 votes – and no answer from microsoft in 3 years.

    I would like either this – OR to have shared data sources and shared datasets at the solution level as well.

    Basically i need a way to have different deployment options (where to deploy to etc) but have shared data sets and sources across multiple projects.

    <=-=Sep 13 2012 2:29AM=-=>

    I wouldn’t minds but visual studio natively has the facility to create your own folder structure, its been disabled in BIDS!

    I ended up having to write an app to…

  7. Populate has_default_value in sys.parameters

    As we all know, T-SQL stored procedure parameter defaults are not stored in sys.parameters, all_parameters, and system_parameters. They are also not exposed through sp_sproc_columns, sys.columns, or sp_procedure_params_rowset.

    However, Management Studio has no problems at least indicating whether or not a default value exists (though not the actual value) for a specific parameter (this is new in 2005; Query Analyzer did not show this). So I know that the information can be retrieved somehow, whether it is parsing the text in sys.sql_modules.definition, or using spt_sproc_columns_odbc_view, or some internal mechanism invisible to profiler.

    This is not an overly common request, but it…

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 62

    <=-=Nov 13 2006 2:23PM=-=>

    HI Tim,

    As posted by Tibor Karaszi, BOL document that “SQL Server only maintains default values for CLR objects in this catalog view; therefore, this
    column has a value of 0 for Transact-SQL objects. To view the default value of a parameter in a Transact-SQL object, query the definition column of the sys.sql_modules catalog view, or use the OBJECT_DEFINITION system function.”

    We dont store even the bit that indicating parameter is of default value in Yukon.

    Thanks for the feedback, we will look into addressing this more completely in future releases.

    Best Regards
    Andrew
    [MSFT]

    <=-=Nov 13 2006 2:56PM=-=>

    Hi Andrew, this is Aaron not Tim. If you are not gong to fix these omissions from sys.parameters, then could you at least share/publish the code that Management Studio uses to parse syscomments.text, since it is fully capable of showing…

  8. Partition Table using min/max functions and Top N - Index selection and performance

    Partitioned Tables performance issues - For select statements using Min and Max functions and Top N with ordering over an index.

    Poor performance is being detected for Queries on partitioned tables utilising the min and max functions and select Top N clause with "order by" matching columns of the index.

    The candidate index is either not being used or is being used to scan or seek all rows rather than a subset.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 125

    <=-=Aug 10 2007 9:17PM=-=>

    Hi Microsoft, please confirm this optimizer problem by running the scripts, it is self evident and can be optimised significantly better.

    Eg. For a minimum, the optimal plan is to obtain the minimum for each partition using the index and then taking the minimum of all the (partition) results. The same principle can apply to maximum, and for Top N over an index …

    The plan should stand out as optimal, because the number of reads over the index is very small, and there will be one set of page reads (usually only one page) for each partition…. you can use the assumption that the number of partitions is significantly smaller than the number of rows (or even count the number of partitions), to estimate the cost (page reads) – which comes out at about N pages where N is the number of partitions.…

  9. Allow for outer joins in indexed views

    Currently there is a restriction for indexed views to only contain inner joins. This effectively restricts the use case to non-null fk relations. Nullable fk relations are impossible to materialize.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 3

    <=-=Feb 7 2011 2:05PM=-=>

    Why not a filtered index?

    <=-=Feb 8 2011 10:31AM=-=>

    Hi,

    Thanks for the feedback. We’ll consider this for a future release. The columnstore index feature coming in the Denali release provides such excellent performance that many data warehouse and data mart customers won’t need indexed views any more. So that may provide an adequate solution for you. See http://download.microsoft.com/download/8/C/1/8C1CE06B-DE2F-40D1-9C5C-3EE521C25CE9/Columnstore%20Indexes%20for%20Fast%20DW%20QP%20SQL%20Server%2011.pdf

    Best regards,
    Eric Hanson
    Program Manager
    SQL Server Query Processing

    <=-=Feb 8 2011 10:51AM=-=>

    Please don’t leave out OLTP customer… Indexed views are great for eliminating joins for mostly read data. Consider the following schema:

    create table forumthreads (id, userid null, title)
    create table users (id, name)

    and the query:
    select top 10 * from forumthreads left join users order by users.name

    No single-table index can satisfy the sort order so the entire result set must be materialized and top-n sorted. It would be much…

  10. Cardinality Estimation Error With Pushed Predicate on a Lookup

    In SQL Server 2005, a filtering condition on a column retrieved from a Key Lookup is applied in an explicit Filter operator after an apply join.
    In SQL Server 2008 onward, this filter can be pushed down to the lookup during copy out, but cardinality estimates are not updated correctly.
    The post-filter cardinality estimate is applied to the inner side of the lookup join, rather than the result of the join as a whole.

    -- SQL Server 2005 AdventureWorks
    SELECT
    th.ProductID,
    th.TransactionID,
    th.TransactionDate
    FROM Production.TransactionHistory AS th
    WHERE
    th.ProductID = 1
    AND th.TransactionDate BETWEEN '20030901' AND '20031231';

    Estimate from index…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 76

    <=-=Oct 26 2012 11:30AM=-=>

    Thanks for the feedback, we are looking into this request

    <=-=Sep 17 2013 2:44PM=-=>

    Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. This is because the fix is risky to implement.
    Thanks again for reporting the product issue and continued support in improving our product.

    <=-=Dec 2 2015 2:45AM=-=>

    This is something we are investigating, and needs thorough testing. This is so we do not introduce wide-spread regressions, like in cases when we had the CE underestimate, and then we would not have had not enough memory granted, leading to spills otherwise.

    <=-=Jan 3 2017 9:52AM=-=>

    Tested and confirmed fixed in SQL Server 2016 Service Pack 1 (build 13.0.4001.0)

    <=-=Jan 3 2017 10:23AM=-=>

    Actually, no. A related item…

  11. SSRS: Export tooltips to Excel as comments

    It would be nice if exporting a report to Excel resulted in the tooltips travelling with it and appearing in Excel as comments.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 56

    <=-=Jan 13 2010 10:03AM=-=>

    Hello,

    Thanks for writing in with this feature request. While this feature isn’t available yet, we’ve flagged it for consideration for a future release of SQL Server Reporting Services.

    Best regards,
    Chris B.
    SSRS Team

    <=-=Dec 13 2012 7:57AM=-=>

    How shit that you can’t do this already!! How did they never bloody think of this? Multi-billion dollar company, and they can’t think of anything innovative. Even Apple are better than Microsoft.

    <=-=Apr 4 2013 12:42PM=-=>

    Having worked with multiple companies over the years in the BI space there are two primary export/save as scenarios for the displayed report, Excel or PDF. When exporting to Excel, business clients invariably want all the richness of the report preserved to the extent possible. Lost tooltips is one example, charts rendered as bitmaps with no data behind is another.

    We hope SSRS is actually moving to the…

  12. Customizable Parameter Prompt Value in SSRS

    Currently, there is no way in SSRS to customize the pompt value for the parameter. This means, at the design time, the developer has to type the prompt value for the parameter. Currently this is not data driven, nor it can be changed thru a .NET assembly code.

    This is a problem where a single report has to be accessed by users who speak multiple languages, for them the prompt value has to be translated and also adjusted to the user culture.

    examples for Prompt values are "Select Country", "Select Users", "Select Model"

    The drop down values associated to the…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 37

    <=-=May 3 2007 4:26PM=-=>

    Thank you for requesting this feature. We will consider this in the next release of Reporting Services.

    <=-=May 4 2007 9:57AM=-=>

    Thank you for requesting this feature. We will consider this in the next release of Reporting Services.

    <=-=Nov 1 2007 7:45AM=-=>

    This is incredibly important for localizing report parameter prompts. Right now we can localize everything except report parameter prompts. This means we’re having to write our own code to do all the parameters. Which means we’re starting to look seriously at other tools that have a better API.

    <=-=Nov 29 2012 7:20AM=-=>

    This keeps SSRS from being used as a platform for an application. Equally important is the ability to parameterize the fields for a dataset. I can write code for the query but then have to specify what fields are being pulled – boo!

    <=-=Apr 10 2013 8:04AM=-=>

    SQL Server…

  13. suppress namespace attributes in nested SELECT FOR XML statements

    When using the 'WITH XMLNAMESPACES' Construct, the namespace declarations show up in each nested query of a 'SELECT FOR XML' statement.
    While it does produce a valid XML document, the results are not exactly pretty.

    Example query with a subselect:
    -------------------------------------------------------------------------
    WITH XMLNAMESPACES('http://test.com/customer'; AS rt, 'http://test.com/customer/'; AS rtc)
    SELECT Customer_id AS "@Customer_id"
    , (SELECT sub.Name AS "rt:Name"
    FROM Customer AS sub
    WHERE sub.Customer_id = Customer.Customer_id
    FOR XML PATH(''), type)
    FROM Customer
    FOR XML PATH('rt:Customer')
    -------------------------------------------------------------------------
    (the sub-query is meant as an illustration)
    This query produces:
    -------------------------------------------------------------------------
    <rt:Customer xmlns:rtc="http://test.com/customer/types&quot; xmlns:rt="http://test.com/customer&quot; Customer_id="1">
    <rt:Name xmlns:rtc=xmlns:rtc="…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 178

    <=-=Apr 13 2007 1:31PM=-=>

    Dear Michael

    Thanks for the feedback. We will be looking into your suggestion for a future release of SQL Server.

    Best regards
    Michael

    <=-=Jun 4 2007 1:43PM=-=>

    This would be very useful for our products as well.

    <=-=Aug 26 2008 8:55AM=-=>

    I just encountered this weird behavior. Although it is valid XML, it makes the resulting document extremely large as well as inconsistent. E.g., the intermediate elements created by the “AS” clause of the subquery don’t have the namespace declaration. I vote for a fix.

    <=-=Sep 17 2008 8:20AM=-=>

    I also think this should be changed. It makes the XML very difficult to read!

    <=-=Jan 29 2009 12:09AM=-=>

    The current function realy bloats the returned XML, we’ve used the “old-school” for xml expicit but the sql to construct that is realy messy.
    We’ve used the xml functionality in SQL server for a…

  14. Remote table-valued function calls are not allowed

    Steps to reproduce:

    create function dbo.TestFunc() returns @t table (id int) as
    begin
    insert @t values (1)
    insert @t values (2)
    insert @t values (3)
    return
    end
    go
    select * from tempdb.dbo.TestFunc()
    go
    select * from [sharepoint].tempdb.dbo.TestFunc()
    -- [sharepoint] - local machine

    And get error
    Msg 4122, Level 16, State 1, Line 1
    Remote table-valued function calls are not allowed.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 100

    <=-=Dec 7 2007 10:41AM=-=>

    Yes, this would be great. You can call views and stored procs from another server or another database; you should be able to call table-valued functions also.

    I hope this is fixed in SQL Server 2008.

    <=-=Dec 21 2007 2:15PM=-=>

    Thanks for your feedback regarding remote table-valued function calls. We are currently investigating the effort needed to implement this functionality. Since we are wrapping up our efforts on the next release of SQL Server (2008) it is unlikley that a fix will be available by then.

    Regards,

    Joachim Hammer

    Program Manager
    SQL Server

    <=-=Feb 22 2008 6:31AM=-=>

    This is one of those “loose ends” that frustrates the SQL 2005 users. I hope that the MS SQL 2008 team(s) will take care…

    <=-=Jul 3 2008 11:46AM=-=>

    Hope this is fixed soon. Big issue for linking two sql servers.

    <=-=Sep 23 2008 8:12AM=-=>

    Oh, gods, yes…

  15. Have SSMS respect a Resource Lock

    When I set a lock on the Resource Group where my Azure SQL Server and DB reside - I can still delete the DB using SQL Server Management Studio This action should at least generate a prompt in SSMS indicating a Resource Lock has been set

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →

    SSMS doesn’t know anything about Azure resource groups at this time. I suspect the lock only applies to the ARM REST API. Perhaps this suggestion should be copied over to Azure SQL Database; they could check for this lock on the server side and fail the TSQL query.

  16. SSMS change connection to multiple servers

    In SSMS, I can use the registered servers pane to open a new query window connected to multiple servers. Make it so that I can then right-click in that window, choose "connection / change connection," and then change my connection to a new group of servers, or at least choose multiple single servers. As it is now, "change connection" only lets you point at a single server.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  17. new virtual table: errors. It would analogous to the deleted and inserted tables

    If a constraint violation happens in a DML statement and the input was a dataset, the offending data in the source is difficult to find. The statement fails and the datasource has to be searched (and possibly recreated) and checked for the violation.

    Thread from the forum.
    http://social.technet.microsoft.com/Forums/en-US/transactsql/thread/3e17f8dc-9685-412b-8e76-94ad41536d5d

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 650

    <=-=Dec 20 2012 1:14PM=-=>

    Oh god yes. If you do this please be sure to include rows not inserted due to IGNORE_DUP_KEY settings on indexes and constraints.

    <=-=Dec 20 2012 1:17PM=-=>

    @Rob: No, please do not include those rows! If I’ve added IGNORE_DUP_KEY it’s because I want to ignore them. They’re NOT errors. (Okay, now we can see how difficult this feature would be to implement…)

    <=-=Dec 20 2012 1:22PM=-=>

    “It could also include a column for the constraint name that was violated.”

    An error may be caused by something other than a constraint violation, e.g. a data type violation:

    DECLARE @t TABLE (i INT)
    INSERT @t SELECT ‘abc’

    … so I’d rather the virtual table have a column with the actual error message. (Which would include the constraint name anyway.) And maybe a column for the error number.

    <=-=Dec 20 2012 1:24PM=-=>

    Of course the last…

  18. View Any Database

    The instance level View Any Database permission takes precedence over assigning more granular securables; this permits a user to view all databases in an instance, not just those databases for which the user has permission.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 11

    <=-=Nov 5 2010 7:16AM=-=>

    I agree that we need more granularity. Servers are holding greater numbers of databases, and the importance of masking groups of databases for admin purposes is growing. Currently, if the “ANY” permission is not granted, the principal must be the database owner (or highly privileged).

    A database level VIEW DATABASE permission would enhance manageability.

    <=-=Dec 13 2010 5:02AM=-=>

    Hi Grant,

    Thanks for the suggestion. This is something that we have been thinking about and we’ll consider this for a future version of SQL Server.

    Thanks,
    il-Sung.

    <=-=Aug 30 2011 11:38AM=-=>

    Hi Grant,

    Thank you for your feedback. We will consider this for a future version of SQL Server.

    Regards,
    Don Pinto
    SQL Server Engine

    <=-=Feb 11 2013 2:38PM=-=>

    Thank you for your feedback. We will consider this for a future version of SQL Server.

    <=-=Jun 25 2015 12:35PM=-=>

    agree with Michael Smith.…

  19. Add to the FULL TEXT INDEX a REGULAR EXPRESSION ability

    My requirement comes from having to find all records in a table of documents in which there is a field "Title" and "DocumentText" through a FULLTEXT search, but in most cases the search is to find documents that contain an item number. This item code is an alphanumeric variable composition but may be correctly recognized by a regular expression.

    Actually I must search through the exact expression LIKE '%item%' with very poor performance.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 3

    <=-=Feb 25 2011 10:27AM=-=>

    Thanks for your suggestion for improving the Fulltext Search Featureset. This is an often requested feature and is on our radar for improvements in future releases. At this stage unfortunately we can not provide any timeline on its availability.

    Best regards
    Microsoft SQL Server Search Group

  20. Page Compression for Out-of-Row LOB Storage

    Disappointingly page compression does not apply to out-of-row LOB storage for data types such as VARCHAR(MAX) and NVARCHAR(MAX) [and also TEXT and NTEXT].

    Would you consider adding this in a future release?

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 10

    <=-=Mar 8 2011 9:34AM=-=>

    Thanks for contacting SQL Server team with the feedback. We will consider this in a future release. At this time, you can compress Out-of-row BLOBs by storing them as FileStream on a compressed volume. But I do understand that this is not your scenario as the data types you mentioned are not suitable for Filestream

    Thanks
    Sunil

    <=-=Mar 8 2011 1:30PM=-=>

    Sunil, thanks for the feedback. I had considered this option, but we’re using database mirroring as a resiliency solution which, unfortunately, doesn’t support Filestream.

    Thanks
    Chris

    <=-=Jan 15 2012 11:47AM=-=>

    Chris, I updated the title of your request. You are not really saying PAGE compression for out of row or LOB data. What you are saying is that we need the ability to compress this data as well. Also, I added a variance of UNICODE compresion as well.

    thanks
    Sunil

    <=-=Dec 1 2014…
  • Don't see your idea?

SQL Server

Feedback and Knowledge Base