How to stop SQL Server 2008 R2 generating SQLDump.mdmp files constantly?

Something went wrong with local SQL Server 2008 R2 and it constantly generates SQLDump.mdmp files. It generated 40Gb(!) of SQLDump.mdmp this morning. Server rebooted, but didn't help.
Any ideas what happened with SQL Server and how to stop SQLDump.mdmp files generation?
SharePoint 2007 - 2010 Tips & Tricks Portal | Microsoft MVP |
My Blog about Information Management |
My twitter

Memory Dumps are generated automatically by the SQL Server under various circumstances - most of which indicate potential problems in the Instance or the machine. Some that I can recall right now are:
Database Corruption
Non-yielding scheduler
Non-yielding resource monitor
AV (Access Violation)
There can be several other reasons as well. SQL Server generates the dumps, so that these dumps can be analyzed to find out potential problems in the SQL Server.
IMHO, rather than trying to find out ways to stop the dumps from being generated, please try to find out potential problems in the Instance or the machine and fix that. This will stop the dump generation anyway.
In case you need any assistance in analyzing the Dumps, please feel free to engage Microsoft Support.
Suhas De
Please mark solved if your question is completely answered; vote it as helpful to help others find a solution quicker.
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog: http://blogs.msdn.com/b/suhde

Similar Messages

  • How to install SQL SERVER 2008 r2 in window 7 home premimum 64bit

    how to install SQL SERVER 2008 r2 in home premimum 64bit os. can any say that weather it will support or not in window 7 home premimum os.
    my server log file:
    Final result:                  SQL Server installation failed.
    To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068052700
      Exit facility code:            1212
      Exit error code:               1316
      Exit message:                  SQL Server installation
    failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2014-03-27 00:52:25
      End time:                      2014-03-27
    00:56:09
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL
    Server\100\Setup Bootstrap\Log\20140327_005035\SSCRuntime_Cpu32_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
    Machine Properties:
      Machine name:                  SEVALAL-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance          
      Instance ID                    Feature                                  Language          
      Edition              Version         Clustered 
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER  
          Database Engine Services                 1033                 Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER  
          SQL Server Replication                   1033                 Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER  
          Full-Text Search                         1033                 Standard Edition     10.50.1600.1    No    
      Sql Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER  
           Analysis Services                        1033                 Standard Edition     10.50.1600.1    No  
      Sql Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER  
           Reporting Services                       1033                 Standard Edition     10.50.1600.1    No    
      Sql Server 2008      SEVALAL              MSSQL10.SEVALAL
                   Database Engine Services                 1033                 Express Edition      10.3.5500.0    
    No        
      Sql Server 2008      SEVALAL              MSSQL10.SEVALAL
                   SQL Server Replication                   1033                 Express Edition      10.3.5500.0  
      No        
      Sql Server 2008 R2                        
                                  Client Tools Connectivity                1033                    
                     10.50.1600.1    No        
      Sql Server 2008 R2                        
                                  Client Tools Backwards Compatibility     1033                            
             10.50.1600.1    No        
      Sql Server 2008 R2                        
                                  Client Tools SDK                         1033              
                           10.50.1600.1    No        
    Package properties:
      Description:                   SQL Server Database Services
    2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
      Installation edition:          STANDARD
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup
    Bootstrap\Log\20140327_005035\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                True
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      IS,SSMS,ADV_SSMS,OCS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL
    Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft
    SQL Server
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  True
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup
    Bootstrap\Log\20140327_005035\ConfigurationFile.ini
    Detailed results:
      Feature:                       Integration
    Services
      Status:                        Failed:
    see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management
    Tools - Complete
      Status:                        Failed:
    see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management
    Tools - Basic
      Status:                        Failed:
    see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Microsoft Sync
    Framework
      Status:                        Failed:
    see logs for details
      MSI status:                    Passed
      Configuration status:          Passed

    my summary log file information:
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068052700
      Exit facility code:            1212
      Exit error code:               1316
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2014-03-27 00:52:25
      End time:                      2014-03-27 00:56:09
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\SSCRuntime_Cpu32_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
    Machine Properties:
      Machine name:                  SEVALAL-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                 1033            
        Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication                   1033            
        Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text Search                         1033      
              Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services                        1033      
              Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services                       1033      
              Standard Edition     10.50.1600.1    No        
      Sql Server 2008      SEVALAL              MSSQL10.SEVALAL                Database Engine Services                 1033  
                  Express Edition      10.3.5500.0     No        
      Sql Server 2008      SEVALAL              MSSQL10.SEVALAL                SQL Server Replication                   1033
                    Express Edition      10.3.5500.0     No        
      Sql Server 2008 R2                                                       Client Tools Connectivity      
             1033                                      10.50.1600.1    No        
      Sql Server 2008 R2                                                       Client Tools Backwards Compatibility  
      1033                                      10.50.1600.1    No        
      Sql Server 2008 R2                                                       Client Tools SDK        
                    1033                                      10.50.1600.1    No        
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
      Installation edition:          STANDARD
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                True
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      IS,SSMS,ADV_SSMS,OCS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  True
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\ConfigurationFile.ini
    Detailed results:
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Microsoft Sync Framework
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\SystemConfigurationCheck_Report.htm

  • How to restore SQL Server 2008 database to SQL Server Express 2012

    How to restore SQL Server 2008 database to SQL Server Express 2012.
    I BACKED UP a SQL Server 2008 database from work, which runs the enterprise version of 2008, and I tried to RESTORE it to my new 64-Bit home PC which is running the new SQL Server Express 2012 64-Bit (Advanced Edition).
    But if fails. I get the following message text.
    Can anyone help me please. I thought restoring a 2008 database to the later version 2012 would be possible.
    Here is the error message. Thanks.
    TITLE: Microsoft SQL Server Management Studio
    Restore of database failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)
    ADDITIONAL INFORMATION:
    System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the backup, or use a
    backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)

    ADDITIONAL INFORMATION:
    System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the
    backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)
    Are you sure your database is SQL server 2008 from error message it seems your SQL server version is 2000.I guess you have multiple versions of SQL server.
    AFAIK you cannot restore backup of SQL server 2000 to 2012 directly .Restore it first to SQL 2008/2008R2 or 2005 then take backup again of new database created and then you would be able to restore it on 2012.Its kind of intermediate way
    Also make sure your DB size is less than 10 G as max DB size supported by Express edition is 10 G and if your DB size is more than 10 G restore will fail.
    You are also trying to restore enterprise DB backup on express edition so you will loose enterprise features on express edition
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • How to connect sql server 2008 r2 sp2 with vs2013 ultimate?

    how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?

    Hi Shahzad,
    >>how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
    Based on your issue, if you wan to connect the sql server 2008 r2 sp2 from VS2013 IDE. I suggest you can try the Ammar and darnold924's suggestion to check your issue.
    In addition, I suggest you can also refer the following steps to connect the sql server 2008 r2 sp2 with visual studio 2013 ultimate.
    Step1: I suggest you can go to VIEW->SQL Server Object Explorer->Right click SQL Server->Add SQL Server.
    Step2: After you connect the SQL Server 2008 r2 sp2 fine, I suggest you can go to VIEW->Server Explorer-> right click the Data Connection->Add Connection.
    And then you can create the connect string in the Add Connection dialog box.
    Hope it help you!
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • How to let sql server 2008 know the table created at front end in c#

    How to let sql server 2008 know the table created at front end in c#

    The best solution is to create table type and pass the DataTable as table-valued parameter. I have an article on my web site about this:
    http://www.sommarskog.se/arrays-in-sql-2008.html
    The full article is a bit of overkill for what you are doing right now, but just the few first pages should get you going.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • How can install SQL Server 2008 Integration Services without CD?

    How can install SQL Server 2008 R2 Integration Services without CD?
    The PC with Windows 7 32-bits is far away and poor bandwidth . So, I want to install SQL Server 2008 Integration Services without CD.
    Does any installer for SSIS only?

    Copy the install media from a memory stick, portable drive or network.
    Arthur My Blog

  • How to configure Sql Server 2008 R2 for debugging without disabling Windows Firewall?

    When I try to debug a procedure in Sql Server 2008 R2 I get a dialog box telling me to unblock some ports.
    >>
    The Windows Firewall on this machine is currently blocking remote debugging.  Remote debugging requiers that the debugger be allowed to receive informatino from the network.  Remote debugging also requires DCOM (TCP Port 135) and IPSEC (UDP 4500
    / UDP 500) be unblocked.
    <<
    I went to the Windows Firewall and added some new Inbound rules for each of the specified ports (in the images below.  But after this and rebooting entire computer -- I still get this dialog box when I want to go into debug mode from SSMS.  I can
    actually kind of debug standalone code in the SSMS window if I cancel the dialog box.  But I can't debug an actual stored procedure -- which is what I need to do.  I also noticed that my server has an IP address instead of LocalHost.  This is
    not a public Server -- it's my private development machine which is on a peer to peer network (with one other workstation), but I don't need that workstation to be able to access this server..  Would localholst make a difference for debugging?  How
    should I configure the sql server?  The firewall?
    Rich P

    Use PRINT and SELECT for debugging. That's what I do. I used to play with the debugger in SQL 2000 and older days, but I realised that I spent more time on getting it to work that I gained from using it.
    I thought about that.  I guess that IS the way to go.  Very well.  Thank you for the suggestion.   Although, when the debugger does work in the regular window (not a stored proc because it doesn't work there) the debugger IS nice. 
    For debugging my proc I am thinking I will insert param vals into a test collection table for now.  One obscure error I am getting with a particular proc -- in a When loop on one parameter I get the "value will be truncated" error -- but everything
    is set to accept 1000 characters and none of the source data even comes close to 1000 characters.  I have isolated at what point the error occurs and which section of data where the error is occurring but I have not isolated the cause of the error. 
    I cannot reproduce the error when I run the procedure by hand in a regular query window with the exact same code.  The error only occurs when the code is run in the stored proc.
    Rich P

  • How to install SQL server 2008 express on Windows server 2008 R2 standard OS

    Hi,
    I have Windows server 2008 R2 Standard edition (64-bit) and trying to install SQL server 2008 express edition since I do not have SQL server 2008. When I install it I am unable to see Management Studio so I am trying to install management studio as well
    but still I am facing issue. Please let me know whether SQL server 2008 express edition is compatible with  Windows server 2008 R2 Standard. If not then pls let me know the proper steps to install it.
    Regds

    Hello,
    Service Pack 1 for SQL Server 2008 is required to be compatible with Windows Server 2008 R2.
    Please download QL Server 2008 Express with SP1 included from the following link:
    http://www.microsoft.com/en-us/download/details.aspx?id=25052
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • How to stop SQL Server Agent Job if Stored Procedure returns value 0

    I have SQL Server 2012 SSIS.
    I have 2 SSIS packages.
    I have created SQL Server Agent Job for running packages.
    I have created steps. If first step have run succesfully next step is run.
    I have need to add new logic.
    I have validation stored procedure, which validate DB table values and returns 1 or 0.
    I would like to create logic where first of all this SP is runned. Return value of SP determines if steps are run or not.
    I was thinking to use Execute SQL Task for running SP.
    If value 1 is returned, then run rest of Tasks is run.
    If value 0 is returned, what should I do so that Job is stopped? I need assistance! 
    I want current step to stop never moved to next step.
    Is there any SSIS tasks, which can stop the Job?
    Or should I make Step for running validation SP?
    How to do so that if value 0 is returned stop Job.
    Kenny_I

    Please refer the below link:
    http://technet.microsoft.com/en-us/library/aa260308(v=sql.80).aspx
    Please read Remarks carefully!!!
    Remarks
    If a job is currently executing a step of type CmdExec, the process being run (for example, MyProgram.exe) is forced to end prematurely. Premature ending can result in unpredictable behavior such as files in use by the process being held open. Consequently,
    sp_stop_job should be used only in extreme circumstances if the job contains steps of type CmdExec.
    Permissions
    Execute permissions default to the public role in the
    msdb database. A user who can execute this procedure and is a member of the
    sysadmin fixed role can stop any job. A user who is not a member of the
    sysadmin role can use sp_stop_job to stop only the jobs he/she owns.
    When sp_stop_job is invoked by a user who is a member of the
    sysadmin fixed server role, sp_stop_job will be executed under the security context in which the SQL Server service is running. When the user is not a member of the
    sysadmin group, sp_stop_job will impersonate the SQL Server Agent proxy account, which is specified using
    xp_sqlagent_proxy_account. If the proxy account is not available,
    sp_stop_job will fail. This is only true for Microsoft® Windows® NT 4.0 and Windows 2000. On Windows 9.x, there is no impersonation and
    sp_stop_job is always executed under the security context of the Windows 9.x user who started SQL Server.

  • How to connect SQl Server 2008 to SAP BW

    Hi Experts,
    i would to build the following scenario.
    I would like to connect an infoprovider or a query in sap BW to a SQL Server.
    The goal will be to use the Management studio as well and to send the data from SAP BW (Cube or Query) to the sql server.
    1. Could you please advice steps by steps how to do the istallation?
    2; Which connectors should i use?
    3. Is there any document which provide the tools, drivers, connectors to be used?
    4. Is there any how to which can help after the installation to run the scenario?
    Thank you in advance for your Input.
    Cheers
    Gilo

    Hello,
    What you request can be done with DB Connect.
    A good starting point is the following link :
    [http://help.sap.com/saphelp_NW04/helpdata/en/58/54f9c1562d104c9465dabd816f3f24/content.htm|http://help.sap.com/saphelp_NW04/helpdata/en/58/54f9c1562d104c9465dabd816f3f24/content.htm]
    Also I recommend to search further on SDN because there are some interesting posts on connecting BW to external databases like SQL Server.
    Wim

  • SQL Server 2008 R2 on Windows 2012 R2

    It appears I cannot install SS2008 R2 on WS2012 R2.  I get the following: 
    'Your version of Microsoft SQL Server (2008 and 2008 R2) isn't compatible with this version of Windows.'
    Can someone please confirm this and when this issue might be resolved?

    Hello,
    Please try a slipstream installation of SQL Server 2008 R2 + SP2 using the following article:
    http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

    Hi All,
    I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
    When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains  invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
    Below is the screenshot for the same.
    So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
    http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
    Again i still see the same above errors and with that a new error related to a MOF File.
    Below are the contents of the error logs. Can some one assist on this issue.
    ======================================================
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068052692
      Exit facility code:            1212
      Exit error code:               1324
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2015-01-15 13:53:03
      End time:                      2015-01-15 14:04:29
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
    Machine Properties:
      Machine name:                  ALPCLDSCOM01
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      Installation location:         D:\SQLServer2008R2_SP1\x64\setup\
      Installation edition:          ENTERPRISE
      Slipstream:                    True
      SP Level                       1
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 E2KLAB\SCOMAC
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     D:\SQLServer2008R2_SP1\SP
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  E2KLAB\SCOMAC
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 E2KLAB\SCOMAC
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
      MSI error description:         The folder path 'Program Files' contains an invalid character.
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
    Gautam.75801

    Hi Alberto,
    Still the same issue.
    I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and  repaired the .NET using the .NET Repair tool
    Also changed the installation directory to D:\ Drive this time. Still same issue.
    log file:
    ===============
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068052692
      Exit facility code:            1212
      Exit error code:               1324
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2015-01-15 22:55:37
      End time:                      2015-01-15 23:07:32
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
    Machine Properties:
      Machine name:                  ALPCLDSCOM01
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       1
      Installation location:         D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
      Installation edition:          ENTERPRISE
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              D:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           D:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   D:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           E2KLAB\Gautamr
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
    Any other suggestion i can try ?
    Gautam.75801

  • SQL Server 2008 R2 Setup Very Slow

    Hi,
    We have a multi-node SQL Server 2008 R2 Failover Cluster.
     I've noticed that the SQL Server 2008 R2 Setup is extremely slow and that it appears to only be using 1 of the 128 "CPUs" (i.e. in Task Manager).
    We use this for creating new cluster groups and alike.
    Is this tool only single threaded and is there a way to increase the performance? Our CPUs are 2.something GHz, we have 512GB of RAM and fast local disks.
    Thanks

    Hello,
    What happen if you slipstream the SQL Server 2008 R2 with the latest SQL Server 2008 R2 service pack? Maybe SQL Server setup does better after the slipstream process.
    http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
    http://msdn.microsoft.com/en-us/library/dd638062(v=sql.105).aspx (Slipstream a SQL Server 2008 R2
    Update)
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Installing SSMS 2012 after SQL Server 2008 R2 Express was installed (without tools)

    Hi everybody,
    This is a question in another forum I am frequent. Someone installed SQL Server Express 2008 R2 and he used the wrong exe, so he installed it without tools. Now he wants to install SSMS.
    It looks like SSMS 2012 wants to have SQL Server 2012 Express installed first.
    Can someone please confirm if it's possible to install just SSMS 2012 after SQL Server 2008 R2 Express was already installed and if possible, guide through the installation steps?
    Thanks a lot in advance.
    For every expert, there is an equal and opposite expert. - Becker's Law
    My blog
    My TechNet articles

    Hi Naomi,
    Agree with Shanky.
    I have tested the scenario you described. Everything works well, I successfully install SQL Server Management studio 2012 after SQL Server 2008 R2 Express (without tools) was already installed.
    Please note that we don’t need to install SQL Server 2012 Express first when installing SSMS 2012. For detailed installation steps of SQL Server 2008 R2 Express and SSMS 2012, you can review below blogs.
    How to Install SQL Server 2008 R2 (Express Edition)
    SQL Server Management Studio – A step-by-step installation guide
    In addition, we can use SSMS 2012 to manage SQL Server Express 2005 /2008 /2008 R2, the tool is backward compatible.
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.
    Lydia Zhang
    TechNet Community Support

  • SQL Server 2008 R2 Standard - Compatibility issues with Windows Server 2012 R2

    Hello,
    We used as a test a box on which we installed Windows Server 2012 R2 and SQL Server 2008 R2 Standard Edition. No Service pack was installed. It worked perfect.
    Now we try to do it on another box and all of the sudden there is compatibility issue when we try to instal SQL Server. We can still install SQL Server by clicking "Continue without getting help".
    Where can this come from? If it is hardware related what are the thing I should look at?
    Thanks all

    Hello,
    Adding to Shanky suggestion, you can perform a slipstream installation of SQL Server 2008 R2 + SP3 to make SQL Server
    2008 R2 compatible with the newer operating system, as explained on the following post.
    http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
    https://support.microsoft.com/en-us/kb/955392/
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

Maybe you are looking for

  • Package names missing when specifying classes

    Hi! I need to generate Javadoc for some (not all) of the classes in one of the packages. So I specified the class names in the batch file (thanks again, Doug!) instead of specifying the package name. Now only the classes in the package have HTMLs, bu

  • Please help safari icon got deleted from my applications!!!

    Hi my safari icon got deleted from my applications! do u no how i can get it back without putting the osx disk back in the computer. thanks

  • What is the best way to install & clone hard drives on macbooks? does apple do that?

    It is time for a new hard drive for my macbook - just doiubles the memory, but am still getting the spinning beach ball. The genius bar told me I need a new hard drive, but that I could buy it and out it in myself. But, I just heard that the best way

  • What is Pushdown Optimization in informatica

    Hey Satish, Adding to Soundarya, you can do Pushdown optimization at source end also.  What I've seen the real time projects is Push down optimization is more useful in Re-engineering projects/Performace Tuning projects. That means as the existing lo

  • IPhone 4S stops playing music

    Hi, my iPhone 4S randomly (or so I thought) stops playing music but still rings when a call connects and beeps when an email comes in. The on screen volume controls would disappear and the side volume button stopped working too.  I have seen many man