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 Stack Overflow or MSDN.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Source Control Disabled by Default in SSMS 17

    Your have disabled the Source Control Provider option in SSMS 17 by default. What the hell were you thinking?

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

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. BULK INSERT with IDENTITY column creates query plan with SORT

    The attached sample demonstrates an unnecessary SORT operator when inserting into a table with an identity column even though the ORDER hint is specified on the BULK INSERT statement.

    The BULK INSERT time for table bulk101 with the IDENTITY column is 49 seconds

    The BULK INSERT time for table bulk102 without the IDENTITY column is 23 seconds.

    I don't see the need for the SORT operator.

    Also; there is no easy way to DROP/ADD the IDENITY property which really limits any workarounds.

    With a billion row table this make a big difference.

    Also; if I don't set KEEPIDENTIY, meaning new…

    4 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: 4

    <=-=Jun 6 2008 10:29AM=-=>

    Thanks for identifying this. we will consider this fix in the next release

    <=-=Jun 20 2015 1:30PM=-=>

    In SQL Server 2012 there is still Sort operator used when bulk loading into a table (empty) with Identity property, although data file is sorted and BULK INSERT is executed with ORDER hint.
    This issue was opened in 2008 and it’s still active, could you please fix it finally??
    It was really problematic back in the days when there was no workaround known as the one proposed in this issue, but do we really need to apply workarounds?
    This sort operator is not needed, that’s for sure.

    <=-=Sep 26 2017 7:15PM=-=>

    Still present in SQL Server 2017. This really should be addressed.

  3. Add support for autonomous transactions

    Support for autonomous transactions (i.e. the ability to nest a unit of work) would allow for more concurrency. At the moment an operation that is logically independent such as a logging operation can lock resources until the transaction as a whole succeeds.

    A great example of where this would be useful is in the implementation of sequences. Once a sequence range is allocated the change can be committed independent of the surrounding transaction. Doing so allows other transactions to allocate sequence ranges while the first transaction is progressing. This allows for greater concurrency.

    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: 102

    <=-=Dec 11 2007 2:24PM=-=>

    Hello Anthony

    Thanks for your feedback and feature request. Autonomous transactions are a powerful feature and can be used to satisfy a variety of core requirements, such as sequence generation, error logging, and more. Though autonomous transactions will not be available in SQL Server 2008, we are actively tracking this as a feature request and are considering supporting it in a future release of SQL Server.

    Thank you

    SQL Server Engine Team

    <=-=Aug 31 2008 6:14AM=-=>

    Also consider the ability to pick multiple “atonomous” transactions to simultaneously COMMIT or ROLLBACK.

    For example,
    BEGIN TRANSACTION A
    BEGIN TRANSACTION B
    BEGIN TRANSACTION C
    COMMIT TRANSACTION B,C
    BEGIN TRANSACTION D
    ROLLBACK TRANSACTION A,D

    Here is the kicker: the COMMIT or ROLLBACK is atomic with respect to all named transactions that are listed.

    <=-=Oct 20 2011 11:37AM=-=>

    Competition was and still is so much always ahead:
    Sequences,…

  4. Introduce more regular expressions functions to T-SQL

    Regular expressions need to be more fully implemented in the T-SQL engine. For instance Oracle's REGEXP_SUBSTR would be nice so I could look for a string like b%e in abcdefg, replace it to get a[new string]fg.

    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: 12

    <=-=Oct 19 2007 8:18AM=-=>

    Hello,

    This is indeed a good suggestion—-so good we’ve gotten it a few times. :) I’m resolving this as a duplicate of Connect item 296631.

    Cheers,
    -Isaac

    <=-=Mar 26 2010 10:55AM=-=>

    Hi,
    I have resolved this request as duplicate of feedback item below:

    https://connect.microsoft.com/SQLServer/feedback/details/261342/regex-functionality-in-pattern-matching?wa=wsignin1.0


    Umachandar, SQL Programmability Team

  5. BCP out to include field columns names

    BCP out to include field columns.
    Would be very helpful it the BCP command line tool will have the option to export the field column names

    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: 41

    <=-=Oct 4 2007 10:13AM=-=>

    Thank you for your feature suggestion. We are considering the improvement in our next release.

    <=-=Jan 23 2012 11:23AM=-=>

    It’s been three and a half years, and we’re headed toward our third release since this item was filed, but is this still being considered for “our next release”?

    <=-=Feb 22 2012 7:56AM=-=>

    One simple workaround to allow automation – (A 3 step job):
    1. Create a file _header.txt that has the column headings
    i.e. copy the first row [with header] of a select * from table, paste into excell, keep only headings and save as .txt

    2. bcp out to Data.txt file
    i.e. bcp DB.dbo.table_name out c:\table_name
    Data.txt -Sserver -T -c

    3. Concatenate files with the copy command
    i.e. copy /a /Y C:\tbl_header.txt + C:\tbl_Data.txt C:\tbl.txt

    Also, you can bcp out of a view which offers tremendous additional functionality… :-)

    <=-=May 28 2014 3:54AM=-=>

  6. No error raised when a remote procedure times out

    If you call a stored procedure in a linked server, and the provider times out, for
    instance there is a blocking situation on the remote server, SQL Server only prints
    a message, but error is raised, so the condition cannot be caught in BEGIN TRY.

    The problem appears both in SQL 2005 and SQL 2008.

    As indicated in the repro, there is a workaround by looking at the return code
    from the procedure.

    4 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: 19

    <=-=Apr 8 2008 1:06PM=-=>

    You have closed the bug gy design without a comment. Please understand that this about the most efficient way to insult a customer. May the customer has got it all wrong, but at least he deserves an explanation.

    So could you please care to explain the “design” for this behaviour? What I failed to mention in my bug report, is that if I run the SELECT statement directly against
    the linked server:

    SELECT * FROM REMOTESVR.Northwind.dbo.Orders WHERE OrderID = 11000

    you do get an error raised. So why is no error raised when a remote procedure call times out? It is not considered an error?

    <=-=Apr 9 2008 11:38AM=-=>

    Erland,

    Sorry for not responding sooner. This just was bad timing on our part. Dev and test closed the report before I had a chance to communicate with you.

    The fact that you can�t…

  7. Allow Common Table Expressions in all query expressions

    Currently, a Common Table Expression (CTE) is allowed only in query statements (SELECT, INSERT, UPDATE, and DELETE). According to the SQL:2003 standard, a CTE (or "<with clause>", as the standards call it) should be allowed in all query expression, which includes subqueries. This would enable us to write, for instance:

    IF EXISTS
    (
    WITH tab AS
    (SELECT 1 AS col)
    SELECT * FROM tab
    )
    PRINT 'okiedokie'
    ELSE PRINT 'not ok';

    This syntax, which is allowed according to SQL:2003, is not accepted by SQL Server 2005. I have reported this as a bug (see https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=254336), but this has been…

    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: 47

    <=-=Nov 14 2007 11:20AM=-=>

    Hello,

    Thank you for sending your feedback to us. We will consider adding this functionality in a future release of SQL Server.

    Thanks,
    Vineet Rao

    <=-=Dec 3 2007 1:42PM=-=>

    Dear Hugo

    Thank you for your feedback. I really like your suggestion and I can see how useful it could be. Unfortunately, we’re at a point in the release cycle for SQL Server 2008 where we’re not able to address this issue as part of the release. We’ll consider it for the next release.

    Best regards,
    Eric Hanson

  8. PIVOT

    PIVOT statement is required explicittly indicate a list of values that will be the columns to be created. The trouble is that is not DINAMIC and if a new value appear, a modification must be done for accept the new one.

    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: 100

    <=-=Nov 23 2005 3:16PM=-=>

    Thank you Yoshiko for making us aware of this customer request. What makes this request difficult to fulfill technically is that the inner subquery would determine the shape of the output result set. The way SQL Server is built, the shape of a relational result set needs to be determined independently of the data the query accesses. I understand the business reasoning of having such a facility though, so we are keeping this issue active for the next version of the product to see what alternate solutions we can come up with for this meaningful scenario.

    Oliver Seeliger,
    SQL Server Development

    <=-=Oct 13 2008 4:05PM=-=>

    I’d like to further request the ability to order the pivoted columns by optionally specifying the order by clause in the subquery. Right now, the only way to pivot the columns server-side is to modify the workaround I posted…

  9. Placing Database under Source Control

    I have been trying to evaluate how SQL Server Management Studio integrates with source control. The only thing I can find is the ability to place a database 'solution' under source control and that basically puts create scripts and change scripts under source control. It doesn't keep 2 or more people from making changes to the same object.

    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: 2

    <=-=Jun 20 2008 2:27PM=-=> harolds,

    Thank you for the suggestion. I will send a notification to the feature team to keep tracking of this suggestion.

    Regards,
    Eric Kang
    Program Manager, Microsoft SQL Server

    <=-=Aug 22 2008 11:49AM=-=>

    Harold is a colleague of mine. It just seems strange to us that all SQL related source control is done at a SQL script level instead of an actual object level within SQL Server itself. You should be required “check-out” a stored procedure, for example, before you can ALTER it. If you “Undo check-out” then the object should be restored to it’s previous state.

  10. Allow enabling and disabling of a column's IDENTITY property

    Sometimes IDENTITY columns need to be cleaned up a bit -- their values updated or re-ordered, for instance. This can occur when data replication strategies fail, or when unexpected data was inserted. This is a somewhat rare occurrence, but when it does happen it can be extremely painful due to the fact that IDENTITY columns cannot be updated, and the property cannot be enabled or disabled. As a result, in most cases doing what should be a simple update requires creation of a new table.

    Likewise, we sometimes want to be able to turn an existing column into an IDENTITY…

    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: 60

    <=-=Jan 18 2007 10:51AM=-=>

    Thank you for the feedback, we’ll look into ways to improve on the scenario you describe.

    Thanks,

    - Christian Kleinerman

    <=-=Jul 5 2007 12:27AM=-=>

    IDENTITY columns CAN be updated! See workaround…

    <=-=Feb 21 2008 8:08AM=-=>

    Workaround doesn’t work in 2000 or 2005.

    I would rate updates more important than turn on/off, but both would be very handy.

    <=-=Oct 16 2009 4:00AM=-=>

    @way0utwest – the workaround definitely does work in 2005 – I used it just the other day!

    <=-=Feb 4 2010 5:16PM=-=>

    I have added a partial workaround using ALTER TABLESWITCH.
    I do agree that this would be a useful extension to ALTER TABLE ALTER COLUMN though…

    <=-=May 2 2013 8:10PM=-=>

    I just realised how painful having identity columns !! we recently wanted to merge two client databases (their businesses merging) and it became a nightmare!! Because we used identities as…

  11. triggers before insert and row level.

    Need to have real Before triggers and row level triggers. SQL doesn't have these triggers or sequences. They have "instead of" but not a real Before Trigger like enterprise level databases have. It's a real pain to program in SQL or to convert from Oracle or MySQL.

    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: 43

    <=-=Jul 3 2007 12:12AM=-=>

    BEFORE triggers are part of ANS SQL 99 (and 2003), and as such have been implemented by many manufacturers (Oracle, IBM).

    It’s time MS implemented ANS SQL.

    <=-=Jul 8 2007 5:49AM=-=>

    That request is for 3 features instead of one!
    1) I agree about Before Triggers
    2) Row triggers are easily done with SQL although with non ANSI syntax. But they are a bad practice, so low priority for me.
    3) Sequence would be nice eventually, but it is not a show stopper.

    <=-=Aug 13 2007 2:53PM=-=>

    Thank you for posting your request. We realize that BEFORE triggers are extremely useful, specifically in migration scenarios. Unfortunately, we are not able to provide this functionality in SQL Server 2008. We are considering it for a future release. Meanwhile, we suggest using INSTEAD OF triggers to achieve similar functionality.

    <=-=Aug 17 2007 1:01PM=-=>

    INSTEAD

  12. Defered Constraint Checking

    We often need to reload application tables, such as configuration, enumeration values etc which we do via a bulk insert from application generated export. When foriegn key constraints are added against these tables deleting and reloading data results in constraint violation. Since an alter statement cannot be placed in the same batch the process constraint disable/reenable cannot be performed within the context of the transaction to ensure constraint is reenabled if the data reload fails.

    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: 6

    <=-=Jul 9 2007 12:51PM=-=>

    Dupe of:

    https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124624

    <=-=Jan 22 2008 2:09PM=-=>

    Kurt,
    Thanks for your valuable feedback and sorry for the late answer. As you might have seen in the community discussion comment of your submission, there is a related suggestion about the same issue. We are planning to implement this feature in our next major release. This other suggestion also includes a possible workaround, see https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124624
    With best regards,
    Roman

    <=-=Apr 5 2010 3:12PM=-=>

    Hi,
    I have resolved your request as duplciate of feedback item below:

    https://connect.microsoft.com/SQLServer/feedback/details/124728


    Umachandar, SQL Programmability Team

  13. Change the title of a report to be different from .rdl file name

    If my RDL file is named Reportforseeingthings.rdl

    Displayed the web portal report title as "Report for seeing things"

    This would allow users to adhere to URL design best practices and give designers the ability to accomodate their clients naming pattern requests.

    3 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 →
  14. NOT MATCHED and MATCHED parts of a SQL MERGE statement are not optimized

    The "MATCHED" and "NOT MATCHED" parts of a SQL MERGE statement are not optimized when criteria is based on constant or variable values, causing the statement to run for unnecessarily long periods of time and consume excess resources even though no action can actually be performed due to the criteria. This causes the merge statement to perform great degrees of additional work as is demonstrated in the attached SQL file.

    As a workaround for this, we have had to remove parts of the merge statement and perform them separately within IF blocks thereby negating the luster of the MERGE statement…

    3 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: 17

    <=-=Jan 19 2011 4:53PM=-=>

    Dear Josh,
    Thanks for taking time to post this suggestion.
    The problem you mentioned comes from the fact that when you run a stored procedure for the first time, the query optimizer builds a plan which does not take into account that variable.
    So, as a workaround I would suggest to add OPTION, it will ensure that the procedure is recompiled and so will force to use a new plan.
    However, your suggestion is very valuable and concerns not only the MERGE statement but all cached plans. We will look into this problem in the upcoming releases.
    Best regards,
    Jean-Sebastien, SQL Server

    <=-=Jan 25 2011 11:06AM=-=>

    Creating the procedures with “WITH RECOMPILE” did not change the performance of the procedure. The MERGE statement still seems to scan the data unnecessarily.

    We have created a separate merge statement within each of the…

  15. SQL Server Audit - Need actual values stored with Audit record

    When SQL Server stores the Audit record, the values in the update clause and where clause are replaced with parameters. To meet the requirements to audit who viewed and changed information (specifically what information), we need to store the actual values with the audit record.

    This is a great new feature, but without the values, it isn't sufficient to meet requirements.

    3 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: 5

    <=-=Sep 30 2010 10:18AM=-=>

    Hi Tracy,

    First of all, thank you for your feedback!

    In order to investigate further, I wanted to get an understanding of how this query is invoked. Are you noticing this behavior when invoking the query using a stored procedure?

    Thank you and regards,
    Don Pinto
    SQL Server Engine

    <=-=Jul 7 2011 4:28PM=-=>

    Hi,

    We have detected another connect item requesting for the same functionality.

    We have linked this connect item with another connect item that is kept open (http://connect.microsoft.com/SQLServer/feedback/details/624935/sql-server-2008-database-audit-on-insert-update-and-delete-actual-sql-and-not-parameter-values) and closed this item.

    Thank you and regards,
    Don Pinto
    SQL Server Engine

  16. SSRS: Providing ability to annotate/comment in report design

    One feature I would like to see Microsoft introduce to SSRS is the ability to annotate or comment, anywhere within the report. As a programmer who has moved to Reporting Services I find the "graphical programming" fantastic and easy to use: reports are easy to build but then often difficult to change or debug because there are settings and checkboxes in a million different places within the report design.

    Would be great if there is a way of annotating in SSRS reports. Currently SSIS for example has a way of adding programmer comments on the Design surface.

    3 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: 20

    <=-=Oct 26 2011 2:18PM=-=>

    This is a critical feature to reporting at my organization. There is value add for analysts to be able to annotate reports (as mentioned above) anywhere in the report. It is sometimes called data sense making. Without it, we cannot fully adopt SSRS and still need to take advantage of being able to do so in Excel using objects. I would suggest the ability to annotate a published report by a category of users with the right permissions. Data is vetted and interpretted as makes its way up the chain and that is an important function of the chain itself. By the time the PM, or Executive sees the reports, the data should be interpretted and annotated.

    <=-=Jul 18 2015 11:16AM=-=>

    @Kingstepper, I read your comment as wanting to be able to annotate a rendered report whereas the original suggestion from Theroyale is asking…

  17. [SSRS] CSV/XML Renderers should evaluate Hidden expressions for DataElementOutput=Auto

    In SSRS 2005, any dynamic columns would not appear in CSV exports unless DataElementOutput were set to Auto, because the renderer treated the presence of a formula as True. In 2008 R2, leaving DataElementOutput = Auto with leads to all dynamic columns being always exported. As stated in https://connect.microsoft.com/SQLServer/feedback/details/322439, this is by design and seems documented.

    IMHO the renderer should evaluate the hidden expression when DataElementOutput is Auto and no higher-level circumstances dictate behaviour. I always assumed the 2005 way was due to some kind of laziness - someone writing if ( element.Hidden ) {... which would of course…

    3 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: 10

    <=-=May 30 2011 12:57AM=-=>

    I have the same issue with exporting Tablix report to CSV format. There are columns in the Tablix that I want to exclude from the output dynamically based a parameter user selected. The Column Visibility is set to based on an expression. It works fine when exporting to other format inlcuding EXCEL, but not for CSV and XML. All columns are exported to CSV disregarding the experssions.

  18. SSRS 2016 - KPI with profile dependencies

    I try since several days to set a KPI for each user.

    In fact, the user must have his number of remaining holidays. To do this, the dataset is filtering with the USERID.

    But, it's not possible to refresh the KPI if the dataset contains a profile dependencies.

    In my case, it is not a report but a KPI. A KPI is present at the connection of the user. The user does not need, as a report, click to launch an execution. So I can not use the user profile to display a KPI.

    One topic is open in the…

    3 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: 14

    <=-=Sep 8 2016 5:20PM=-=>

    Thanks for your feedback – it is currently not possible to personalize KPI’s in Reporting Services, and this is implementation is by design currently. However, it is something we will consider for a future release based on customer feedback. I will mark this item as closed as by design, but we have this already on the list of features we’ll be considering to add in a future release.

    Thanks,

    The SQL BI Team

    <=-=Feb 25 2017 7:34AM=-=>

    Dear Vivien,

    I’ve tried this as well – I just send the USERID to a Stored Procedure – and couldn’t get it to work – patched and tried everything… I hope it will come soon – its obvious that this is something you want?

    Not that it is smart – but you can create a dataset per user and then a do a KPI for each user…

  19. Unnecessarily bad performance for coalesce(subquery)

    It appears that the algebrizer transforms coalesce(a, b) to

    CASE WHEN a IS NOT NULL THEN a ELSE b END

    before optimizer gets a chance to see it. This is testified by the fact a
    query like "SELECT coalesce(xyz, 0) FROM sys.objects" yields two error
    messages for the missing column and not one.

    When a is a subquery, this becomes

    CASE WHEN (subquery) IS NOT NULL THEN (subquery) ELSE b END

    This is unfortunate, because the optimizer does not seem to be able to match
    the two instances of subquery, why it gets evaluated twice. This can easily be
    worked…

    3 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: 50

    <=-=Apr 2 2008 5:15PM=-=>

    Erland,
    Thanks for reporting this issue. It is by design that the subquery in a coalesce is not matched between the optimizer and the algebrizer. Enabling this would involve considerable efforts and does not meet the current triage bar for SQL 2008. We assume that this does not affect many customers, however, we will consider it again for the next major release.
    A simple workaround that still uses coalesce would be to store the subquery’s result in a variable and use that in the coalesce statement.
    With best regards,
    Roman Schindlauer
    SQL Server Relational Engine

    <=-=Apr 2 2008 6:33PM=-=>

    Erland, your repro steps should indicate that having Northwind installed is a prerequisite. :-)

    <=-=Apr 3 2008 1:14PM=-=>

    I can understand that this a too tall order for SQL 2008 RTM, nevertheless it is something that should be addressed in one way or another.

  20. Package Concepts, Global Variables

    Hi,

    I like to see the Package concepts like in Oracle, in which we can declare the variables and then use in the multiple stored procedures in the package.

    This will be lot helpful in breaking the big stored procedures into small ones.

    Please consider the request in future release

    3 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: 18

    <=-=Nov 13 2007 5:05PM=-=>

    Hi Vijay

    Thank you for your feedback. The concept of global variables and the ability to ‘package’ stored procedures and modules is very useful functionality. We are considering it for a future SQL Server release.

    Sara Tahir
    Microsoft SQL Server

    <=-=Nov 19 2007 9:24AM=-=>

    Hi Sara,

    Thanks for your info. Can you let me know which release of SQL Server that it is planned.

    Thanks & Regards

    Vijay Anand Kannan

    <=-=Dec 19 2007 9:36AM=-=>

    Hi Vijay,

    At this point of time, we havent decided on which release of SQL Server we will add this. Unfortunately this will not be in SQL Server 2008 but we will definitely consider it for the release after that.

    Thanks,
    -Vineet Rao.

    <=-=May 20 2008 12:22PM=-=>

    Hi,

    Can you please let me know if you have any plan for the implementation of the package.

    Thanks & Regards

    Vijay Anand…

  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base