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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. one of the Newly Added column's don't replicate NULL value

    After adding 3 columns to a Table with the following schema data is not replicated for one of the newly added columns
    --commented columns are the newly added.

    I initially got this in a SQL 2005 64 bit environment and then when I test it with the 32 bit SQL 2008 RC0 same result.
    SET ANSI_NULLS ON
    GO

    SET QUOTED_IDENTIFIER ON
    GO

    CREATE TABLE [dbo].[TESTTABLE](

    [TESTTABLEID] [int] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
    
    [ID] [int] NOT NULL,
    [Code] [nvarchar](3) NOT NULL,
    [ERName] [nvarchar](30) NOT NULL,
    [ExCode] [nvarchar](10) NULL,
    [TSymbol] [nvarchar](12) NOT NULL,
    [INCode] [nvarchar](12) NOT NULL,
    [CSCode] [nvarchar](9) NOT NULL,
    0 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. Microsoft.SqlServer.BatchParserClient.dll not included in Microsoft SQL Server 2008 Management Objects

    We are developing and testing against a SQL 2008 server. The required assembly Microsoft.SqlServer.BatchParserClient.dll is not included in the downloadable feature pack. I had to copy the DLL from a machine with SQL 2008 installed to the client machine. This assembly is not found after trying to use Database.ExecuteNonQuery Method. I believe this required assembly should be installed with the rest of the SMO assemblies.

    0 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

    <=-=Jul 15 2008 4:31AM=-=>

    Hi,
    Thanks for reporting this issue. This issue is already fixed and will be available in next public release of Sql Server.
    Thanks,
    Sravanthi

    <=-=Jul 18 2008 1:42PM=-=>

    I had the same issue . I my case I installed the 32 bit version of SMO to windows 2003 server and it did not install Microsoft.SqlServer.BatchParserClient.dll which caused a problem during execution.

    <=-=Nov 24 2009 10:12AM=-=>

    It may be fixed as far as the assembly cach install process for smo , but it is not fixed for creating
    redistributable setup packages.

    I have sql express advanced editions with sp1 and vs 2008 with sp1 installed. I have a Report Installer setup
    package which uses an imbedded vb.net app as an execution event installer process. I ported this project to
    2008. I had to update the vb.net smo refferences to sql 2008, and it did not…

  3. Ragial gauge range dissappear after calibrating the scale


    1. Drop a radial range.

    2. Calibrate the scale.

    3. The default range disappears from the design image but it�s the Ranges collection

    0 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 →
  4. SQL Server 2008 Express Advanced Password Expiration Checkbox Grayed Out

    After installing a fresh copy of SQL Server 2008 Express Advanced on Windows 2008 x64 Enterprise Edition I found that if I didn't uncheck the box for "User much change password on next login" during SQL account creation I could not uncheck it later because it was grayed out in the properties of that user. I had to delete my test database and test user and recreate them with this checkbox unchecked. I cannot alter SQL Server policies in this edition due to it being crippled, so this was the only workaround I found. Until I did this, no remote…

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

    <=-=Jul 21 2008 2:25PM=-=>

    Hello Crumb,

    Thank you for reporting this problem. SQL Server will prompt for the user to change the password the first time he/she logs into the server. If you would like to check/uncheck the option after the Login was created but before the user has logged into you could recreate the login. We will look at this issue for a future release of SQL Server.

    Thanks,
    Karthik

    MS SQL Server

    <=-=Jun 10 2011 6:42AM=-=>

    Hello Crumb,

    Thanks for logging the issue.

    We discussed and triaged the issue along with the other issues that have been logged in the SQL Server bug database, and due to other critical issues and resource and time constraints, we are not taking-up this issue for fixing it. We have taken note of this internally, and when we revisit this functionality in the future, we will try and get this…

  5. AMO Update Error. Memory error: Allocation failure : Not enough storage is available to process this command.

    Hi all,

    I have a looping code in C# using AMO which accepts dimension objects, makes some changes such as addition or updation of attributes and hierarchies. It also updates properties for the dimension and the lower objects(Like attribute and hierarchies).

    The full Description of the error can be found in MSDN forums at the following link :
    http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3625890&SiteID=1

    There is another link in this thread that can be used as a reference. I will attach the trace file to this feedback for reference.

    Regards...
    Girija Shankar

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

    <=-=Sep 8 2008 6:47AM=-=>

    I have added a workaround which worked for me. Can you please confirm and close this issue .

    Regards..
    Girija Shankar

    <=-=Oct 13 2008 11:26AM=-=>

    Girija.

    Thanks for findning the workaround. Can you please attach the workaround to this issue.
    Currently it doesnt look like it has been added.

  6. Service account Startup mode during install is available for selection

    When installing a SQL 2008 cluster, the Service account Startup mode during install is available for selection. It defaults to Manual but it could be changed to Automatic or Disabled that should not be possible on a Cluster

    0 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: 1

    <=-=Jul 18 2008 3:52PM=-=>

    Fabio,

    We will look at this for the next release.

    We shouldn’t create service accounts during prepare ideally, but we do due to ACL’ing reason during setup (to avoid re-ACL’ing during complete). Ideal fix is to remove service configuration from Prepare for next release (so that we can be fully sys-prep ready).

    Worst case, if we do not change the current behavior for next release, we shouldn’t allow user changing the service start up type from Manual on Prepare UI.

    But, there is nothing in Windows SCM that prevents user from changing the service start up type anyway. So, even if setup does not allow this, we cannot block Windows SCM from changing it.

    Thanks,

    Max

    <=-=Jun 9 2009 2:51PM=-=>

    Hi Fabio,

    We plan “not to allow” changing the startup type for clustered services for our next major release. We have an existing item…

  7. Query plan operators costing more than 100%

    For the query below, the overall cost estimate is less than the estimate for some individual operators. As a result, relative costs exceed 100% for these operators. The overall cost calculation appears to be incorrect, because it did not account for both subtree costs.

    0 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: 1

    <=-=Jul 18 2008 1:32PM=-=>

    There is some explanation here:
    http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=267530

    <=-=Jul 21 2008 5:06PM=-=>

    Dear Steve,

    Thanks for pointing out this inconsistency. This is a know bug and we’ll link your comment up with the known bug. We’ll see if we can address this in a future release.

    Thanks,
    Eric

    <=-=Jul 21 2008 5:10PM=-=>

    Dear Steve,

    Thanks for pointing out this inconsistency. This is a know bug and we’ll link your comment up with the known bug. We’ll see if we can address this in a future release.

    Thanks,
    Eric

    <=-=Aug 10 2011 1:21AM=-=>

    hi Steve,

    This is regarding the connect item 356913. Occasionally when queries have conditional statements (or more than one execution path) the query optimizer costs those paths too while arriving at the optimal plan. This is because in case of estimated plans, the optimizer really cannot decide which path will get executed. In these…

  8. Start Powershell failes when connecting to non default port

    When connecting in SSMS to a server configured to run under a different port than 1433 and TCP/IP network library only the Start Powershell command failes to connect to the server. The server is registered as SERVERNAME,PORT. The SqlBrowser service is not running.

    It seems that the comma needs to be escaped. The next command isn't working within the SQLPS utility as well:
    set-location SQLSERVER:\SQL\SERVERNAME,PORT\DEFAULT

    When you change this to:
    set-location SQLSERVER:\SQL\SERVERNAME`,PORT\DEFAULT
    it works.

    I'm know the character needs to be escaped in powershell or enoded. The problem is that the connection is failes when is start powershell within SSMS…

    0 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 →

    Upvotes: 2

    <=-=Jul 18 2008 7:58AM=-=>

    Hi Robert,
    Thanks for reporting the issue on PowerShell. This is by design. There are certain characters within PowerShell that have special meaning. This is mostly documented here: http://msdn.microsoft.com/en-us/library/cc281841(SQL.100).aspx

    You need to escape the special characters and there are a few options for doing so:
    1) Escape with a tick `
    2) Wrap the text in double quotes “blah,blah”
    3) Use the hex equivalent %2C
    4) Use the Encode-SqlName cmdlet

    Best of luck,
    Dan Jones
    Group Program Manager
    SQL Server Manageability

    <=-=Jul 18 2008 12:35PM=-=>

    Hi Dan,

    Well, I’m aware of that, as I described connecting in SQLPS works when you escape the character. It doesn’t work when you select Start Powershell from the context menu within SSMS. And I can’t escape the characters there, or can I?

    <=-=Jan 29 2009 8:48PM=-=>

    Hi, Robert! This is a bug and we will fix this…

  9. SQL Query Editor Extension Mapping

    When I map a the .prc extension to the SQL Query Editor, it is not recognized with a File | Open. However, it is recognized when I drag the .prc file into the editor.

    0 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 →

    Upvotes: 1

    <=-=Jul 17 2008 8:15AM=-=>

    Hi Tom,
    Thanks for reporting the bug. I was able to repro this but only in a very specific way. After I setup the prc extension I opened the file and it did not recognize it as a SQL file. I then restarted SSMS. When I open the file from the recent files list it doesn’t recognize it as a SQL file. However, if I open it using File-Open it does recognize it. It appears that SSMS/VS is caching some information about the file when it’s opened from Recent files. This isn’t something we’ll be able to address in SQL Server 2008. We’ll keep this on the books and review it again when we start the next release.

    Thanks,
    Dan Jones
    Group Program Manager
    SQL Server Manageability

    <=-=Nov 13 2008 3:07AM=-=>

    Very helpful, was able to apply this to UDF extensions too

  10. Disk usage summary does not display space used for data files

    Disk Usage Summary built-in report in SSMS (Data Collection) displays "MB MB" instead of the space used for specific data file.

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

    <=-=Jul 29 2008 8:12AM=-=>

    Hi brejk,
    Thank you for your feedback regarding this report. We are aware of the problem and we’ll use this as the tracking issue so that others can vote on the issue. You can use the Standard Disk Usage report for the selected database to view the correct report as a workaround.
    Thank you,
    Bill Ramos

    <=-=Jun 10 2011 6:20AM=-=>

    Hi brejk,

    This has been fixed. Please confirm this in the next available public release of SQL Server “Denali”.

    Nikhil
    SQL Server Team

  11. after upgrade to SQL Server 2008 spike on processing time in special regard to the indexes portion

    Since the upgrade of our SSAS environment on SQL Server 2008 we have noticed a consistent increase on cube process time.
    The picture below shows the time spent during process executing using the two version of SQL Server meanly 2005 and 2008.

    For your convenience I have attached the excel document that the pictures was derived from; as well as the xmla scripts that is used to process the indexes.

    We would like to know what could have caused such a spike on processing time in special regard to the indexes portion.

    0 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: 1

    <=-=Jul 25 2008 11:07AM=-=>

    Joseph.

    Thanks a lot for reporting the problem.
    It is very hard to diagnose it without having exact repro in-house.
    We suggest you work with Product support to setup a scenario for us to be able to debug and figure out what is happening.

    Thank you.
    The Analysis Services Team.

  12. Characters and linebrakes are disappering in a Job with powershell that holds an \

    Characters and linebrakes are disappering in a Job with powershell that holds an \

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

    <=-=Jul 24 2008 9:11AM=-=>

    Eric Verschoor,

    Thanks for the report – we will investigate this issue.

    -Richard Waymire

    <=-=Dec 1 2011 11:47AM=-=>

    We took a look at this bug along with several others recently.
    Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future.
    However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

    Thank you
    Alex Grach[MSFT]

  13. Transaction log file size will not grow exactly 4GB when filegrowth=4GB.

    When I set filegrowth to 4GB , 4096MB or 8GB for transaction log file of any database, after the log fills up, the autogrowth will kick in and then I monitor file growth of the log file. It will not grow exactly 4GB or 8GB. It grows in much smaller chunks. Something like, 248KB.
    If I set log filegrowth to 3GB, 5GB, 4095MB, 4097MB or anything that's not exactly 4GB, it will grow exactly the set size for filegrowth.
    This also happens on SQL2005 Developer Edition and Standard Edition on x86.

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

    <=-=Aug 12 2008 1:22PM=-=>

    Thank you for your report. This does seem like an interesting anomaly. We will see if we can reproduce this in the current product and addess it in ongoing development.

    <=-=Aug 4 2009 9:44AM=-=>

    I’m seeing behavior similar to this now with VLF and log files on the latest CUs of SQL 2005 and 2008.
    I was attempting to create a 40GB log file in 5 steps of 8GB each and I don’t arrive at 16 × 5 VLFs of the same size. I’m going to do some more testing before I log a bug.

  14. Many to many dimension query returns incorrect value

    I've just been shown a repro of what looks like a bug where a query with a many-to-many dimension and the expression MyM2MDim.MyHier.Children in the Where clause returns an incorrect value. It looks like a case where an incorrect assumption has been made for query optimisation purposes. I can repro on AS2005 SP2 and AS2008 RC0.

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

    <=-=Jul 24 2008 8:50PM=-=>

    Thanks a lot Chris for reporting the problem.

    Unfortunately it is too late to look at this in 2008 release of Analysis Services.
    We will take a look at this in the next release.

    Edward Melomed

    <=-=Aug 1 2008 12:56AM=-=>

    I think that a good solution would be a different one than simply changing the behavior of the query optimizer. I would add a property to measures (or measure groups) to specify if the evaluation of that specific measure/measure group has to always consider the related m2m dimension and its intermediate measoure group or if this passage can be optimized. This would solve the issue I described in my m2m paper (http://www.sqlbi.eu/manytomany.aspx) related to the distinct count alternative measure.

  15. Reporting Visual Studio: ShowGrid is not working

    In Visual Studio
    Tools -> Option -> Windows Forms Designer -> General the Settings are
    LayoutMode=SnapToGrid
    ShowGrid=True
    SnapToGrid=True

    But there is no visible Grid.

    0 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: 79

    <=-=Jul 22 2008 1:26PM=-=>

    Thank you for providing this feedback. With SQL Server 2008 we replaced grid lines with object snapping and snap lines. We will consider this as feedback that you would like grid lines back. We will consider adding them back in a future release. If this feature is brought back, however, it would not be enabled by this VS option, the Designer would have it’s own command to display or hide grid lines. The VS option you mention is for designing WinForms apps, not directly related to the Report Designer.

    <=-=Jul 23 2008 2:04AM=-=>

    Many thanks for your reply!

    Greetings
    Webfred

    <=-=Oct 23 2008 12:55PM=-=>

    I would also like the SnapToGrid, DrawGrid, and GridSpacing options back. Report development is so much more cumbersome with the object snapping and snap lines. I could actually see how things lined up when the grid was there. Now I’m…

  16. Cannot install 08-040 for SQL 2000 on Vista

    According to
    http://www.microsoft.com/downloads/details.aspx?familyid=8316BC5E-8C2D-4710-8ACC-B815CCC81CD4&displaylang=en
    this hotfix is supported on Vista. However if try to run the install on
    Vista, it fails with "There is not enough storage for this
    command".

    I have x64, but I have reports that it fails on x86 as well.

    Since SQL 2000 is not supported on Vista, the error may be on the download page.

    0 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 →
  17. Edit Menu -> Advanced -> Tabbify / Untabbify Selected Lines option is not working

    I select 10 lines of code and then selected "Tabbify Selected Lines" menu from "Edit->Advanced", but its not working, similary "Untabbify Selected Lines" as well.

    FYI, The uppercase and lowercase converts everything into uppercase, if we have some option to convert only keywords to uppercase then it would make the code look good and also please assign some shortcuts for "Tabbify Selected Lines" and "Untabbify as well, because those are options which we regularly use, so using the menu is time consuming so if we have shortcut it would save lot of time and easy to use as well

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

    <=-=Aug 27 2008 9:30AM=-=>

    arunraj_c,

    Thank you for reporting this issue. We will mark it as a product issue and request dev team to investigate it.

    Regards,
    Eric

    <=-=Jun 20 2011 12:31AM=-=>

    Hi Arun,

    This is regarding the connect issue 357143. Kindly note that the function “tabify” converts all tab length white spaces to a tab. So there is no visual indication and tabify does not mean to move selected text by a tab. Say there are 4 white spaces in a tab, then tabify would look for 4 consequent white spaces in the selected text and replace them by a single tab character. Similarly untabify replaces a tab character with equivalent number of white space characters.

    I hope this explains the behavior. We are closing the issue as by-design.

    thank you

    Seshagiri
    PM, SSMS

  18. Data Collection: Disk Usage Summary

    Incorrect Figure in Disk Space Used

    Workbench is a SQL Server 08 RC0

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

    <=-=Jul 11 2008 7:02PM=-=>

    Hi Nitya,
    thank you for your bug submission regarding the problem with the disk usage report. we are aware of the problem already and will fix this in a future release.
    Thank you,
    Bill Ramos

    <=-=Jun 18 2009 8:28AM=-=>

    Just a note – I needed to do some hosecleaning to duplicate this issue to the active connect item. This is now linked to http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=356518.
    Thank you,
    Bill Ramos

  19. Multiple Filters using hinting a spatial index should work

    The following query produces this error message when I do not believe its appropriate to:

    Msg 8635, Level 16, State 10, Line 2
    The query processor could not produce a query plan for a query with a spatial index hint. Reason: Could not find required comparison predicate. Try removing the index hints or removing SET FORCEPLAN.

    The BOL topic: "Geometry Methods Supported by Spatial Indexes" doesn't require just one filter.

    The queries in question:

    drop table dbo.shapeParts
    go
    create table dbo.shapeParts(

       shapePartID tinyint not null identity(1,1) primary key,
    
    shapeID tinyint not null,
    shapeQuad tinyint null,
    shape geometry not null);

    go …

    0 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: 1

    <=-=Jul 24 2008 1:04PM=-=>

    Thank you for the bug submission. Spatial indexes match only WHERE/ON clauses made of single atomic predicates or ANDs thereof — not ORs. We also do not infer that STIntersects here is redundant.

    <=-=Jul 28 2008 10:25AM=-=>

    We we have not done a good job (yet!) documenting how exactly Katmai spatial indexing works; capabilities, limitations, recommendations. This is a sore spot and it’s overdue. Meanwhile, “index union” support will go on the list of possible enhancements for next release.

    <=-=May 25 2011 9:52AM=-=>

    This is resolved as duplicate of 670505 connect item.
    https://connect.microsoft.com/SQLServer/feedback/details/670505/cross-feature-support-for-spatial-types-should-improve

  20. SQLServer Exception with SPs that start with Sys, contain TVP, and accessed via ADO.NET

    A fatal exception occurs, and SQL Server terminates the session, if you call a stored procedure from C#, and that stored procedure (1) contains a TVP and (2) begins with the letters "sys".

    For example, the following causes the problem:
    ALTER PROC [dbo].[SystemConfiguration_StoreContact]

    @ItemList contactDetail READONLY
    

    but these do not:
    ALTER PROC [dbo].[ystemConfiguration_StoreContact]

    @ItemList contactDetail READONLY
    

    ALTER PROC [dbo].[SystemConfiguration_StoreContact]

    @ItemList int
    

    0 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: 1

    <=-=Jul 28 2008 9:25AM=-=>

    Hi Brian,

    Thankyou for this bug report. After investigation, the situation that triggers this bug is:

    A CLR routine calls a stored proc that 1) contains a TVP and 2) has a name beginning “sys”.
    (yes, I know – we are probably thinking the same thoughts :-)

    Anyhow, we have a fix for this bug, pending review and checkin.

    Meantime, a workaround is to rename your stored proc to not begin “sys”.

    Thanks,

    Jim

    <=-=Jun 22 2010 1:57PM=-=>

    Ran into this bug today on a sql server 2008 instance and it took some time to diagnose. Is the fix available? When was it released? Where can I get it?

    <=-=Jan 4 2011 2:55PM=-=>

    Hi,
    We have fixed this issue for an upcoming cumulative update for SQL Server 2008 R2. Thanks again for reporting it.


    Umachandar, SQL Programmability Team

  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base