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. Microsoft SQL Server Management Studio Error message opening template under source control

    Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
    Oct 14 2005 00:33:37
    Copyright (c) 1988-2005 Microsoft Corporation
    Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

    Visual SourceSafe

    We have custom SQL boiler plate templates for our dev group. We store in a version control library. When we open one of the templates from SSMS, we get the error below. The template still opens and we can work and save as something else, which is what we want. However, this exception is thrown everytime.

    It is a nuisance. Is this a bug that will be fixed?

    TITLE: Microsoft…

    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. detected incompatible components detected during sql server 2005 express installation

    installation does not complete.
    dialog indicates incompatible versions of .net, visual studio, or pre sql server 2005 are installed
    none of these versions are installed (although visual studio and .net 1.1 & .net 1.1 sdk had been installed on this machine and were
    uninstalled... note: the uninstall did not remove 1.x folders from the folder C:\WINDOWS\Microsoft.NET\Framework
    so they were manually removed
    version 2.0.50727 verified for mscorlib.dll as specified in SqlServer2005/RequirementsSQLEXP2005.htm#Before_you_install

    separately installed .net 2 per install instructions (although the instructions also said that net 2 is installed automatically with ALL versions of sqlserver 2005, it said to perform this step) …

    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

    <=-=Dec 19 2005 4:36PM=-=>

    Please look at the Program Files\Microsoft SQL Server\90\Setup
    Bootstrap\LOG\Files\SQLSetup*_Core.log file. It should have a bit of
    information in it saying what the conflict is and some GUIDs indicating
    the product codes of the conflicting programs. The section you are looking
    for will look something like this (and may repeat):

    Running: PerformSCCAction2 at: 2004/6/27 13:54:12 Product “{982DB00A-9C4E-436B-8707-18E113BAA44C}” versioned 9.00.823 is not compatible with current builds of SQL Server.Expected at least version: 9.00.849 The Product Name is "Microsoft SQL Server 2005 Analysis Services Beta 2"

    In this case, the offending product is �Microsoft SQL Server 2005 Analysis
    Services Beta 2" with a product code of
    “{982DB00A-9C4E-436B-8707-18E113BAA44C}”

    If the programs are still visible in the Add/Remove Programs control panel (ARP),
    please remove them in the order specified by the readme file. If they are not in
    ARP, please run the following…

  3. Jobs, Steps reviewing : Index was outside the bounds of the array. (SqlManagerUI)

    When a job is being created, there is no problem with Steps.
    When reviewing the steps of a job created before, following error occured:
    Index was outside the bounds of the array. (SqlManagerUI)
    ----
    Advanced Information
    Details :

    Index was outside the bounds of the array. (SqlManagerUI)

    ------------------------------
    Program Location:

    at Microsoft.SqlServer.Management.SqlManagerUI.JobSteps.PopulateGrid(JobStepsData steps)
    at Microsoft.SqlServer.Management.SqlManagerUI.JobSteps.Microsoft.SqlServer.Management.SqlMgmt.IPanelForm.OnInitialization()
    at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SetView(Int32 index, TreeNode node)
    at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.OnBeforeSelection(Object sender, TreeViewCancelEventArgs e)
    ----
    Meanwhile, when a job is created, there is no problem with the job's execution.

    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 12 2006 8:04PM=-=>

    Hi,

    We tried to repro this problem but we couldn’t. Can you give us more details about the circumstances in which it repros?

    Thank you,
    Ciprian Gerea

    <=-=Feb 16 2006 5:08PM=-=>

    We are closing this bug because we were not able to repro. If you have additional information please do not hesitate to contact us.

    Thank you,
    Ciprian Gerea

    <=-=Dec 8 2011 7:12AM=-=>

    It should not have been closed as not reproducible.

    I had the same issue this morning and found out what the issue was.

    I had a job on SQL Server 2008 which has a step that was using Powershell as Type.
    Now, from my client machine, which had SQL Server 2005 client installed, I was looking at the job and was not able to go to Steps tab, getting the above mentioned error.
    The reason is that SQL Jobs steps in …

  4. SQL 2005 Express fails on Install of Visual Studio 2005 Team Edition ENU

    SQL 2005 Express fails on Install of Visual Studio 2005 Team Edition ENU. See attached log files for full dump of install, but actual error that causes failure is 'Error Code: 15151
    MSI (s) (68!BC) [16:47:39:387]: Product: Microsoft SQL Server 2005 Express Edition -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot alter the login 'sa', because it does not exist or you do not have permission."

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

    We’ll send you updates on this idea

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

    Upvotes: 1

    <=-=Feb 15 2006 1:16PM=-=>

    Thank you for reporting this issue. Can you please include the log files from ProgramFiles\Microsoft SQL Server\90\Logs\Files? We need these in order to further investigate.

    -Jeffrey Baker, SQL Server Lifecycle Platform Team

  5. User defined function in SELECT clause incorrectly forces table scan

    sql server incorrectly ignores indexes (performs table scan) when user defined function is specified in SELECT clause

    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 14 2005 10:43AM=-=>

    Using the latest server bits and the CTP15 build, I was not able to repro the problem using the repro script.
    Were there any
    . other steps in the repro process?
    . server settings that may be relevant?
    . traceflags on?

    <=-=Jun 14 2005 11:51AM=-=>

    Not exactly sure which release of Yukon.
    @@version value of instance exhibiting problem is:
    Microsoft SQL Server 2005 – 9.00.1116 (Intel X86)
    Apr 9 2005 20:56:37
    Copyright © 1988-2004 Microsoft Corporation
    Beta Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

    The repro script is complete and should reveal the problem (on the version above). No special settings on our instance (accepted defaults thru software installation process); Traceflags??? not familiar with them but don’t think they’re relevant.

    If you can’t reproduce, I’ll presume it’s fixed in the latest version.

    <=-=Jun 14 2005 4:15PM=-=>

    Looks like a resolved issue…

  6. SQL Server 2005 Express Edition Install - invalid Setup Bootstrap\setup.in

    Install fails with the following message, although the directory is there and has lots of stuff in it.
    TITLE: Microsoft SQL Server 2005 Setup
    ------------------------------

    The log file path (C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.ini) is invalid.
    * The path may contain invalid characters.
    * The file may exist but not be writable, the folder may not exist, the folder may be located on an unavailable volume or protected with a password, or the path may contain environment variables that are not set (e.g. TEMP). To proceed, make sure that the log file path is valid, writable, and available, and then…

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

    We’ll send you updates on this idea

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

    Upvotes: 1

    <=-=Nov 30 2005 4:21PM=-=>

    In order to further diagnose the problem that you are reporting, we need to have the setup log files. They can be found in the latest .cab file at ProgramFiles\Microsoft SQL Server\90\Setup Bootstrap\Log\Files. FYI, there is a summary error report at ProgramFiles\Microsoft SQL Server\90\Setup Bootstrap\Log\Summary.txt that may help you to diagnose the problem on your own.

    Please attach the cab to this bug report.

    Radu Singer

    <=-=Dec 6 2005 5:48PM=-=>

    Thank you for your feedback.

    We had a developer review your error message and based on the code, he thinks the .ini file contains a [Logging] section with an invalid “Path” value. It appears to be a filename rather than a folder name.

    Regardless, using the [Logging] section is not the correct way to do this, the customer should be using the “LOGPATH” command line param to set the…

  7. File Import Data Conversion Errors

    Trying to import a pipe-delim ASCII file using Import/Export Wizard from SS Mgmt Studio. Not able to change the data types and successfully import the rows. There were integer, float, nvarchar and date/time data types in the source data. Changing the data type on import from nvarchar resulted in failure to completely load the data. However, a small portion of the data did load without error.

    The error report generated by the DTS is attached.

    I was able to import the data by leaving all data types as NVARCHAR(125). After I imported the data, I successfully modified the table design,…

    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

    <=-=Feb 24 2006 11:08AM=-=>

    Hi
    Thanks For bringing this to our attention.
    However, we need more info so as to proceed with investigation. Can you please provide us a piece of your source file which can reproduce your problem?

    Thanks
    Wenyang Hu from Microsoft
    p.s.
    By default, if the source data can not be converted to the destination type (the type you specified), the Flat File will error. However if you do not want it to fail, instead, when it happens put null (or truncated value) in the destination column, you can also do so by modifying the Error Output – in the generated package, edit FlatFileSrc, click “Error Output”, you will be able to change the Error Handling there from “Fail Component” to “Ignore” or “Redirect” for each individual column.

    <=-=Feb 28 2006 10:52AM=-=>

    Hello, can you please respond with additional informaiton?
    Thank you for your time.

  8. SQL Server 2005 Beta 3 Setup has detected incompatible beta components from Visual Studio or SQL Server.

    When trying to install SQL Server 2005 developer edition setup gives this error :

    "SQL Server 2005 Beta 3 Setup has detected incompatible beta components from Visual Studio or SQL Server. To proceed, use Windows Add or Remove Programs to remove previous SQL Server Yukon components, SQL Server Support Files, .NET Framework 1.2 and 2.0. Then run SQL Server 2005 Beta 3 Setup again. For detailed instructions on uninstalling SQL Server builds, see the SQL Server 2005 Beta 3 readme file.
    "

    I Tried to run a cleanup program included in CD , it says that system is clean and…

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

    We’ll send you updates on this idea

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

    Upvotes: 1

    <=-=Dec 19 2005 4:36PM=-=>

    Please look at the Program Files\Microsoft SQL Server\90\Setup
    Bootstrap\LOG\Files\SQLSetup*_Core.log file. It should have a bit of
    information in it saying what the conflict is and some GUIDs indicating
    the product codes of the conflicting programs. The section you are looking
    for will look something like this (and may repeat):

    Running: PerformSCCAction2 at: 2004/6/27 13:54:12 Product “{982DB00A-9C4E-436B-8707-18E113BAA44C}” versioned 9.00.823 is not compatible with current builds of SQL Server.Expected at least version: 9.00.849 The Product Name is "Microsoft SQL Server 2005 Analysis Services Beta 2"

    In this case, the offending product is �Microsoft SQL Server 2005 Analysis
    Services Beta 2" with a product code of
    “{982DB00A-9C4E-436B-8707-18E113BAA44C}”

    If the programs are still visible in the Add/Remove Programs control panel (ARP),
    please remove them in the order specified by the readme file. If they are not in
    ARP, please run the following…

  9. Can't Locate "C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe"

    After installing SQL Server Enterprise Edition it can't find "C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe" file, but there is a shortcut in a menu saying that Business Intelligence Development Studio is installed... I couldn't find this file even using normal file search.

    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

    <=-=Jan 5 2006 11:24AM=-=>

    We can think of two issues that might have caused this:

    1/ A prior installation of Visual Studio was installed on the box. It was then removed, but some registry keys were left. Setup detected what it thought was VS being installed, did not install it’s own version, then created the shortcut (which didn’t work).
    2/ A prior installaton of VS was installed, SQL Setup detected it, created the shortcut, then the VS was uninstalled.

    If these do not match your scenarios, can you please attach the log files from Program Files\Microsoft SQL Server\90\Setup Bootstrap\Logs\Files

    <=-=Mar 1 2010 8:33AM=-=>

    I get the same problem. Not sure what registry files are still there when I uninstall everything. I think that I am having the first problem you addressed.

    <=-=Mar 1 2010 1:24PM=-=>

    Figured it out, after two days of headache.

    I had this same…

  10. Test - please ignore

    this is just a test

    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 →
  11. Calendar control always accept date in MM/dd/yyyy format

    Calendar control in Report parameter page gives an error when the selected date is in dd/MM/yyyy format.

    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

    <=-=May 19 2006 4:52PM=-=>

    We need some more information before proceeding with evaluating this issue:
    What tool were you using when this occurred – was it Report Manager or Management Studio. In general, Report Manager uses the input format based on your Accept Language header set by your browser. This header is set in IE using the Tools —> Internet Options —> Lanaguges button. If you are using Management studio, the input language should be senstive to the OS regional settings. Also, can you provide the values you tried in the repsective options based on the tool you used. Thank you.

    <=-=May 19 2006 5:32PM=-=>

    Microsoft comments: We need some more information before proceeding with evaluating this issue:
    What tool were you using when this occurred – was it Report Manager or Management Studio. In general, Report Manager uses the input format based on your Accept Language header…

  12. Create full-text population schedule failed

    TITLE: Full-Text Indexing Wizard Progress
    ------------------------------

    Create full-text population schedule failed.

    ------------------------------
    ADDITIONAL INFORMATION:

    Failed to connect to server .. (Microsoft.SqlServer.ConnectionInfo)

    ------------------------------

    An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

    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 2 2005 1:48PM=-=>

    Thank you for reporting this issue. Unfortunately, we are unable to replicate the error that you have reported. The error, which appears to be related to establishing a connection, might be affiliated with networking protocols and/or operation of the related service and/or permissions/rights with which the user is attempting to complete the operation. Have you verified that connections are permitted to/from the local/remote SQL Server via: Start > Programs > Microsoft SQL Server 2005 > SQL Server Surface Area Configuration? If you could provide more details as to the configuration you are using to create the FT catalog and population, it might help isolate the issue.

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

    <=-=May 11 2006 11:24AM=-=>

    I have tried the steps you outlined below in RS 2005 SP1. They have worked for me: I was able to pass the credentials to main report and they were passed to the drillthrough report. This is a snippet from the master RDL I have used.

    Drillthrough =Parameters!ConnectionString.Value click here

    Please note that passing connection strings through report parameters URLs is not a secure method, I hope you only use it only for testing.

  14. DBComms.error reading input

    While trying to connect to SQL Server 2005 using jdbc I get the following exception:

    com.microsoft.sqlserver.jdbc.SQLServerException: DBComms.error reading input. Context:Read packet header, Unexpected end of stream, readBytes:-1, negative read result, PktNumber:0, ReadThisPacket:0, PktDataSize:4,096

    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

    <=-=Jan 26 2006 3:48PM=-=>

    Hello medusa,

    Thank you for your time in reporting this issue. Rest assured, the driver actually does connect to SQL Server 2005 databases! :-) I’m hoping this is just a configuration issue… I’ll need you to turn on some diagnostic logging to help me start looking at this. Could you set com.microsoft.sqlserver.jdbc.TDS.DATA.level = FINEST in your logging.properties file and send to me – davido atmicrosoft. com – the results of the connection attempt? This will generate a dump of the on-the-wire protocol, which should hopefully allow me to tell you why the SQL server you’re trying to connect to is dropping the connection on you.

    Thank you,
    —David Olix
    JDBC Development

    <=-=Feb 9 2006 11:08AM=-=>

    Hello again medusa,

    Since we have been unsuccessful in attempting to contact you through this channel for additional information, we are closing this issue here.…

  15. Encrypted Database Backup and restore

    See theread below
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=308381&SiteID=1&mode=1

    Thread name Encryption and database restore

    Please assign to Laurentiu Cristofor

    Basically I have a database created on ony one of several machines with encrypted data in it when I backup and transfer this database to another machine I cannon create the asymetric keys or the symmetric keys encrypted with the asymmetric keys

    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 24 2006 6:04PM=-=>

    We are trying to repro this issue on one of our machines. On the first machine we restored the attached databases, the keys worked ok.

    <=-=Mar 27 2006 6:44PM=-=>

    We tried the backups on more machines, but we were not able to repro this issue. On all machines, the keys worked correctly after restoring the backups.

    <=-=Apr 5 2006 7:00PM=-=>

    Closing as NotRepro, as we have not been able to repro this issue on our machines. If you can get another database with a repro, let us know and we’ll investigate further.
    Thanks
    Laurentiu

  16. Transfer Objects Fails - Source Table Does not exist

    Set up Transfer object to copy one table from a source db to a destination db. Under the Destination Copy Options, wich should be Source Copy Options, under (Collection) I select the tables I want to copy from the source to the destination. When I run the package I get the following error:

    Error: 0xC002F363 at Transfer Test Tables, Transfer Objects Task: Table "FiscalMonth" does not exist at the source.
    Task failed: Transfer Test Tables.

    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

    <=-=Aug 23 2005 9:08AM=-=>

    Does the table exist at the source? Is the table name correctly spelled? Do you have the package? If so, will you send it with the script to build the table you’re trying to transfer? Is this reproduceable with other tables? What version of SSIS are you using?

    <=-=Aug 24 2005 2:12PM=-=>

    Which version of SQL Server is being used? Probably if a newer version is used this problem may be solved.

    This bug is not reproable as described. I need more info: Which version of sql server are used for source and destination? Are you choosing all tables, or a set of tables? Are you setting copy schema? … It is better to have the package attached. But I could copy a table from a source to a destination just fine.

    <=-=Jan 18 2012 12:58AM=-=>

    Please re-open.

    This error msg shows when trying…

  17. Failure to Install SQL Server 2005

    Failure on installation process

    Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
    Action: "UninstallForRS2000Action" will be skipped due to the following condition:
    Condition "Action: InstallRSAction was skipped." returned true.
    Running: ReportChainingResults at: 2006/4/9 14:23:13
    Error: Action "ReportChainingResults" threw an exception during execution.
    One or more packages failed to install. Refer to logs for error details. : 1067
    Error Code: 0x8007042b (1067)
    Windows Error Text: The process terminated unexpectedly.

    Source File Name: sqlchaining\sqlchainingactions.cpp
    Compiler Timestamp: Thu Sep 1 22:23:05 2005
    Function Name: sqls::ReportChainingResults::perform
    Source Line Number: 3097

    ---- Context -----------------------------------------------
    sqls::HostSetupPackageInstallerSynch::postCommit
    sqls::HighlyAvailablePackage::preInstall
    led due to cancel code received from…

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

    We’ll send you updates on this idea

    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Project Engineer

    Will not install.
    Fails with Error 1706 in Application log as:
    Product: Microsoft SQL Server Native Client -- Error 1706. An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.

    System Configuration Check

    - WMI Service Requirement (Success)
    Messages
    * WMI Service Requirement

    * Check Passed

    - MSXML Requirement (Success)
    Messages
    * MSXML Requirement

    * Check Passed

    - Operating System Minimum Level Requirement (Success)
    Messages
    * Operating System Minimum Level Requirement

    * Check Passed

    - Operating System Service Pack Level Requirement. (Success)
    Messages …

    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

    <=-=Dec 5 2005 6:04PM=-=>

    Thank you for your feedback.

    In order to further diagnose the problem that you are reporting, we need to have the setup log files. They can be found in the latest .cab file at ProgramFiles\Microsoft SQL Server\90\Setup Bootstrap\Log\Files. FYI, there is a summary error report at ProgramFiles\Microsoft SQL Server\90\Setup Bootstrap\Log\Summary.txt that may help you to diagnose the problem on your own.

    Please attach the cab to this bug report.

    Radu Singer

  19. CONVERT from string to datetime does not always work for ISO8601 format

    When trying to convert datetime's fetched from XML we get errors.
    It seems SQL server does not like too much digits after the decimal point for the seconds.
    I have a lot of XML code with datetimes in it created from:

    XmlConvert.ToString(DateTime.UtcNow,XmlDateTimeSerializationMode.Utc)

    This function seems to generate dateTimes as follows:
    "2006-07-29T15:56:33.6946834Z"
    and SQL server does not like this.

    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

    <=-=Sep 27 2006 6:44PM=-=>

    Hi
    We are considering improvements to date & time in a future release of SQL Server that will address your feedback.

    Thanks,

    - Christian Kleinerman

    <=-=May 3 2013 4:47AM=-=>

    why can’t I vote for this topic anymore? what’s the status?

  20. Poor query performance with: set statistics time on (SQL2K5)

    The query become very slow when setting statistice time on

    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 →
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base