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. Dataset details disappear in editor

    Adding a new dataset without saving changes to existing dataset and then cancelling the new one undoes all unsaved changes to original dataset

    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. Extra blank line appears in Stored Procedure everytime it is executed and reloaded

    After modifying a stored procedure in the management studio I click on execute and it saved. Then, when I close and reopen the same proc my procedure has an extra blank line after the 'go' line. After a few days my procedure has like 1-2 dozen extra lines at the top of the proc!

    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 →
  3. reportserverurl setting on cluster

    I installed RS2K5 on cluster, modified web.config and rswebapplication.config according to 'Configuring URL settings and View State Validation' in sql2k5 books online. Web browser seems not happy with the change of rswebapplication.config (refer to following error).

    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

    <=-=Apr 14 2006 11:56AM=-=>

    This looks like an issue with the documentation. Try removing the ReportServerVirtualDirectory element from the report manager config file and see if the error persists.

    <=-=Apr 19 2006 8:23AM=-=>

    So you mean we don’t have to edit that config file on clustered nodes?

    <=-=Jul 26 2006 8:50AM=-=>

    Will fix it in sp2?

    <=-=Jan 22 2008 3:04PM=-=>

    Hi Runyin, I am getting continuous “Close-the-loop” emails about this bug, which I fixed, resolved, and closed last year. I don’t know why Close-the-loop is generating a report for this bug, but I hope that by sneding you this email it will stop! Hope all is well with you and your fmaily.

  4. Report Builder Number Format Somtimes Freezes / Greyed out

    Somtimes when you are formatting numbers in Report Builder, the Number Format will be greyed out and you cannot change the number format anymore. You then have to rebuild the report to format the number.

    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

    <=-=Nov 1 2007 9:56PM=-=>

    Jeff, thanks for reporting. We have tried several times to reproduce this but are not seeing this behavior.

    <=-=Apr 17 2009 9:52AM=-=>

    I have also seen this issue. I can apply number formats to a field with no problem when I create a report, but when I save the report, and re-open it, and try to apply number formatting, the Number tab is missing from the Format dialog box, and the Number option is grayed out on the Format menu.
    The only workaround we’ve come up with is to delete the field and add it again.

    Steps to Reproduce: Add two numerical fields to your report, format one as currency (or change the decimal, etc.), and leave the other one alone. Save your report. Reopen it. Try to make the unformatted field display with no decimal places (or as currency.) It can’t be done,…

  5. Strings are not trimmed when they flow into a recordset destination

    If a recordset is populated, using the Recordset destination, with strings - those strings are padded with whitespace all the way to the full length of the data-flow column

    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

    <=-=May 22 2006 1:30PM=-=>

    This was originally found by Alex Levene
    http://www.sqlservercentral.com/forums/post.aspx?forumid=148&messageid=281548

    <=-=Aug 31 2006 12:55AM=-=>

    Why has this been closed? it is a bug.
    What does RESOURCE NOT LOCATED mean?
    Are you not allowed to add comments or something? I’ll just reopen it with another ticket if not!

    <=-=Aug 8 2007 9:46AM=-=>

    Thanks for your message. This was fixed in Yukon SP2.

  6. The correct ContainerStartTime is not accessible in OnPostExecute

    Lots of people (including myself) do their own custom logging using eventhandlers. One thing I and many other people want to is track how long a task executed for. To do this you need to be able to access System::ContainerStartTime of the container raising the error. Unfortunately, as soon as you try and access System::ContainerStartTime within the eventhandler you get the instance of that variable scoped to the eventhandler, NOT the one of the container raising the event.

    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 →
  7. SQL CLR does not support SMO

    Cannot create CLR (assembly) stored procedure that performs some SMO
    operations. When I am trying to register the assembly (after placing my
    library in C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
    directory)

    Will result in following error

    Msg 10301, Level 16, State 1, Line 1
    Assembly 'SMOTestLibrary' references assembly
    'microsoft.sqlserver.batchparser, version=9.0.242.0, culture=neutral,
    publickeytoken=89845dcd8080cc91.', which is not present in the current
    database. SQL Server attempted to locate and automatically load the
    referenced assembly from the same location where referring assembly came
    from, but that operation has failed (reason: 2(The system cannot find the
    file specified.)). Please load the referenced assembly into the curent
    database…

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

    <=-=Mar 28 2006 1:48PM=-=>

    Hi Siva,

    Just a quick update on the status of the issue you contacted us about.
    We have selected your request for consideration in the next version of SQL Server.

    Thank you for your support, suggestions, and feedback.

    Terrence Nevins
    SQL Server Program Manager

    <=-=Feb 24 2010 1:34PM=-=>

    This would be a great feature to have on the CLR side. Many times I have encountered issues writing a CLR routine where it would have been very handy to call SMO routines.

    Thanks,
    Tim
    SQL Server MVP

    <=-=Nov 18 2010 6:01AM=-=>

    Is this in scope for Denali? It is a greatly missed feature on our part and would make creating framework based solutions much easier.

  8. SQL Server 2005 Diagram Rename

    An interesting diagram situation...I have created a diagram in one of my DBs. When I try to rename the diagram from the tree in Management Studio, I receive a "not found" error for sprenamediagram. Chasing things down, I notice that the stored procs for managing diagrams get installed in my DB but not Master. Running Profiler, I see that Management Studio is using Master DB when executing sprenamediagram (hence the error) even though my DB is the default database for the Management Studio connection.

    If I manage the diagram (rename in this case) from VS 2005, all works…

    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

    <=-=May 11 2006 8:04AM=-=>

    Thank you for your defect report regarding the renaming of diagrams. We will address this in a future release of SQL Server.

    <=-=Jan 15 2010 8:13AM=-=>

    I reproduced this issue, using a SQL2005 DB with Management Studio 2008. When I switched to using Management Studio 2005 (not sure which SP), I was able to rename the diagram.

    <=-=Jul 8 2010 6:08AM=-=>

    TWIMC

    I concur with the seminal post.

    My testing shows the same odd behaviour and I guess that it is a bug.

    Thank you.

    — Mark Kamoski

    <=-=Feb 15 2011 5:47AM=-=>

    I had the same problem. I discovered that if the name of the database in which the diagram and the rename procedure exist contains a space that I have the error. If I remove the space from the database name, everything works as it seems it should.

    <=-=Sep 11 2012 2:15PM=-=>

  9. :Quit does not get highlighted as a SQLCMD statement

    :Quit does not get highlighted as a SQLCMD statement.

    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 →
  10. 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

    <=-=Feb 25 2006 1:08AM=-=>

    Thank you for bringing this to our attention. The problem was caused by linear regression does not handle parameters appropriately in some special cases. We have fixed this issue for Yukon SP2 and have verified the fix worked appropriately.

  11. Maximizing Query Editor results in Pending Checkins window being shown

    When the keyboard shortcut, SHIFT+ALT+ENTER, is used to maximize the Query Editor window, the Pending Checkins window shows up. This happens when the app is using the default windows layout and the Pending Checkins window is not visible. {I just installed SQL Server 2005, and have not set up any type of source control integration}

    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 →
  12. Maintenace plan integrity checks fail with "Alter Failed for server xxx"

    My maintenance plan integrity check task was failing with "Alter failed for server XXX".

    After tracing i found the maintenance plan executes sp_configure 'USER OPTIONS',xxxx followed by RECONFIGURE.
    The reconfigure statement then generates an error causing the plan to fail. This was because the server configuration option "Allow Updates" was set to 1. Changed the setting back to 0 and the reconfigure statement started to work again!

    BOL states the "allow updates" setting has no effect which is clearly not true as it causes this bug.

    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

    <=-=Feb 3 2006 6:52PM=-=>

    Hello,

    The “allow updates” option does not have its intended effect in SQL2005, i.e. you cannot update the system tables directly even when this option is ON.

    However, you will still get the error (5808) when RECONFIGURE is called after turning on this option. This is the same behavior as SQL2000. This option was meant to take effect with
    RECONFIGURE WITH OVERRIDE only. The same error behavior as SQL2000 has been preserved in SQL2005 although turning on the option does not have any effect on the ability to update system tables (which is
    always disallowed in SQL2005).

    It is recommended that you not use this option anymore and remove it from your scripts.

    I’m forwarding your question regarding the Maintenance Plans to get it answered by the appropriate people.

    Thank you for your feedback.

    Sameer Verkhedkar
    [MSFT]

    <=-=Feb 6 2006 5:40PM=-=>

    Thank…

  13. Removed Users are not actually removed in the Schema Properties dialog box

    A user removing from the Schema Properties dialog box is not really removed after clicking Ok

    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

    <=-=Nov 4 2005 7:56AM=-=>

    Hi Michael,
    Thank you for your detailed bug report. We were able to reproduce the problem and we will address it in a future release.
    Bill Ramos

    <=-=Mar 31 2006 7:56AM=-=>

    Quick update. We are placing this bug report under consideration for SP2.

    <=-=May 30 2006 2:04PM=-=>

    Hi Michael,
    Thank you for your feedback. The remove user functionality is more so as to remove a user from the list only when all the persmissions to the user have been revoked. If any permissions to the user are still granted then the remove does not work. There is a distinction between Remove users & Revoke permissions on this dialog. Let us know if this does not resolve your issue.
    Thanks
    Ramesh

    <=-=Jun 3 2006 2:25PM=-=>

    No, that does not fly.

    The function of the dialog must be one of:
    1) Pressing Remove revokes all permissions…

  14. The ORIGINAL_LOGIN function is not presented in the "System Functions (Transact-SQL)" topic

    The ORIGINALLOGIN() function is not presented in the topic "System Functions (Transact-SQL)", although similar functions (for example SYSTEMUSER) are presented in this topic. This is probably caused by the fact that ORIGINAL_LOGIN() is a new function defined in SQL Server 2005 (it wasn't present in the previous versions of SQL Server).

    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 →
  15. Exception - Error Source: Microsoft.VisualStudio.DataTools

    The following is observed in the SQLServer 2005 Management Studio Visual
    Editor:

    Open table (Right Click option on a table) fails when I try it on a table
    with lots of columns in it > 820 columns! Currently the table has no rows
    (empty table). The same table opens fine with sql 2000 enterprise manager.
    This table has been migrated/imported from sql 2000 without any errors! Other
    imported tables with less number of columns can be opened in the visual
    editor!

    Wondering is there a hidden limit in terms of number of columns with
    SQLserver 2005 Management Studio (Grid) Visual…

    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

    <=-=Mar 25 2006 2:12PM=-=>

    Here is a script to reproduce the problem. Run this, and then try to open the table “manycolumns”.

    declare sql nvarchar(MAX), @i int select @sql = 'CREATE TABLE manycolumns (x int NOT NULL PRIMARY KEY' select @i = 1 WHILE @i < 1000 BEGIN SELECT @sql = @sql + ', a' + ltrim(str(i)) + ’ int NOT NULL
    SELECT i = @i + 1 END SELECT @sql= @sql + ')' EXEC(sql)

    (I ran this on SP1 CTP.)

    <=-=Mar 28 2006 4:36PM=-=>

    Quick update. We are placing this bug report under consideration for SP2.

    <=-=Aug 3 2006 11:12AM=-=>

    Hi Kannan,
    Thank you for bug report. The Visual Studio team has fixed this for their next release. We will do the same for our Katmai release. In the meantime, you will need to create a view that contains less columns in the…

  16. Object reference not set to an instance of an object. (SQLEditors) when modifying table

    Trying to modify a table in SQL Server Management Studio throws an exception.

    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

    <=-=Apr 20 2006 1:40PM=-=>

    Hi Chris,
    Thank you for your feedback. We will investigate this for addressing in a future service pack release of SQL Server.
    Thanks,
    Ramesh Singh

    <=-=Aug 27 2007 2:16PM=-=>

    Hello Chris,

    The table editor functionality was checked for errors and this was found to be working fine in SQL Server 2008. Please check the coming CTP release of SQL Server.

    Regards,
    MS SQL Server Team

    <=-=Feb 9 2009 2:34PM=-=>

    I have seen this too, but only on 64 bit installations. I’m curious if it’s been fixed in sp3.

  17. Cannot run a SSIS Package which is under Source Control but not checked out

    It's not possible to run a package which is under source control without checking it out.

    With multiple developers working on these scripts having to check them out to run them is very disruptive as they are locked regularly.

    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

    <=-=Jun 2 2006 2:52PM=-=>

    Thanks, we are aware of this problem. As workaround, you may check out the modified file before running it, or start it using Debug > Start Debugging menu, which prompts to check out the file.

    We are considering fixing the problem for the next service pack.

    <=-=Jul 29 2011 3:41AM=-=>

    The Debug >Start Debugging workaround fails if other user has the package checked out with ‘0×80030005 Acces denied message’.

    If other user has the file checked out you can remove the writeonly attribute of the .dtsx file and try to run it.

  18. RU: SQL Server 2005 (Russian words usage mistmatched.)

    RUS: ?????????????? ??????? ????.
    1. "?????? ??????????????:" ?? ?????????? ? "??????", "? ???????? ?????????????????", "???????".
    2. "?????????" ?? ?????????? ? "??????????"
    ENG: Russian words usage mistmatched.
    1. "?????? ??????????????:" mistmatched with "??????", "? ???????? ?????????????????", "???????".
    2. "?????????" mistmatched with "??????????"

    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 →
  19. RU: SQL Server 2005 (russian text truncated in some reports from Summary page in SSMS)

    RUS: ?????????? ????? ? ??????? SSMS ?? ??????? "??????".
    ENG: russian text truncated in some reports from Summary page in SSMS

    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 →
  20. SQL FullText service throws errors while stopping service

    While stopping SQL Server FullText service on the local machine, or shutting down the server at the local machine, I receive two error pop-ups with the same message:

    msftesql.exe - Application Error

    The instruction at "0x4999ce21" referenced memory at "0x0073a4c8." The memory could not be "read." Click OK to terminate the program.

    The service continues to shut down, or the server continues to shutdown.

    However, when I remote into the same machine and reproduce steps, I do not get any errors.

    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

    <=-=Jun 22 2006 11:00AM=-=>

    I was able to recreate the same problem on another machine.

    <=-=Jul 14 2006 6:37AM=-=>

    I can’t believe this was marked as “Resolved” with a resolution of “Won’t fix”!!! If there’s a problem, fix it! Or, at least enter some comments explaining why it won’t be fixed!

    <=-=Jul 14 2006 8:06AM=-=>

    Could I get a second opinion?
    I’m kind of confused why the resolution is “won’t fix?”

    My company has a LAN/OS team responsible for rebooting machines. They will page us as a possible error every time this message appears.

    <=-=Oct 9 2006 5:16PM=-=>

    (not sure if you have seen this feedback as there have been changes to the system)
    Dear Customer,
    Could you repro the problem on SP1 build? We have fixed an AV in SP1 during msftesql.exe shutdown. Send us a dump when it happens. The dump file should be under…

  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base