Configuration note  of SQL SERVER 2005

Hello,
Is there a SAP configuration note for SQL 2005 like note 327494 for SQL 2000 ?
Or does someone know if there should be special configuration for SQL SERVER 2005 ?
Pelase advice,
Dimitry

Hello
Please review 879941 Configuration Parameters for SQL Server 2005
thanks
N.P.C

Similar Messages

  • Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

    I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
    "Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
    Nor will the query execute; I get a transport-level error 0. Any thoughts?

    Hi Davidmhjr,
    >>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
    Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
    If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
    with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
    So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
    More information about configuration requirement to run T-SQL debugger as below, please refer:
    There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
    Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
    On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
    •Add TCP port 135 to the exceptions list.
    •Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
    any named instance.
    •If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
    On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
    •Add TCP port 135 to the exceptions list.
    •Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
    Hope it is helpful.
    Regards, Amber zhang

  • Error"Failed to open the connection"  - Named Instance of SQL Server 2005

    "Failed to open the connection" error, when connecting to the Named Instance of SQL Server 2005
    The report is throwing error, when changing the logon information dynamically through C#.
    Code
         string reportPath = @"D:\NET\TestReport\TestReport.rpt";
         ReportDocument reportDocument = new ReportDocument();
         reportDocument.Load(reportPath);
         foreach(CrystalDecisions.CrystalReports.Engine.Table table in tables)
              TableLogOnInfo tableLogonInfo = table.LogOnInfo;                         
              tableLogonInfo.ConnectionInfo.ServerName = @"TestServer\Instance1";  //Connnecting to Named instance of SQL Server 2005
              tableLogonInfo.ConnectionInfo.UserID = "sa";
              tableLogonInfo.ConnectionInfo.Password = "password";
              tableLogonInfo.ConnectionInfo.DatabaseName = "TEST_DB";
              table.ApplyLogOnInfo(tableLogonInfo);     
         crystalReportViewer1.ReportSource = reportDocument;
    Error Message
         Failed to open the connection.
         Failed to open the connection.
         C:\DOCUME1\PUGALE1\LOCALS~1\Temp\{DF9593A5-5C80-4CBC-ABC3-EC4EF204A7EB}.rpt
    The error is occuring only whenever i am connecting to the Named Instance of SQL Server 2005.
    Thanks in Advance
    Edited by: pugalendran p on Feb 2, 2009 10:32 AM
    Edited by: pugalendran p on Feb 2, 2009 10:43 AM

    Hi,
    Following solution might help you to resolve the issue.
    Solution1:
    Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
    Resolution
    Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
    Import the universe from the designer.
    Go to File->Parameters.
    Edit Connection.
    On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
    Change the DSN to new DSN connection
    Test the connection.
    Save the Universe and Export it to the repository.
    Solution2:
    I am taking Oracle as an example over here.
    This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
    Resolution
    To resolve,
    check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
    look for any paths that contain a mapped drive partition
    Change the mapped drive letter to a UNC path (
    server\folder)
    Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
    If the path is not updated to the new path
    Reboot the server
    Regards,
    Sarbhjeet Kaur

  • Error in adding PRIMARY Data file of SQL Server 2005

    Hi Experts,
    I am using SQL 2005 as back end database for SAP ECC6. Due to Space problem in PRD data volume, i have added PRDDATA4.ndf file in SSMS ( SQL Server Management Studio) and saved. But, suddenly i got one more idea and extended the file size of exisiting PRDDATA1.mdf, PRDDATA2.ndf & PRDDATA3.ndf immediately i removed the PRDDATA4.ndf file before starting the service. But, while seeing in SAP using ST04 it showing the PRDDATA4.ndf with error message of file missing. What i have to do now? How can i delete the information showing in ST04. But it is not showing in SSMS.
    Please help how to solve this.
    Regards,
    B.Sudharsan

    Hi,
    Following solution might help you to resolve the issue.
    Solution1:
    Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
    Resolution
    Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
    Import the universe from the designer.
    Go to File->Parameters.
    Edit Connection.
    On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
    Change the DSN to new DSN connection
    Test the connection.
    Save the Universe and Export it to the repository.
    Solution2:
    I am taking Oracle as an example over here.
    This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
    Resolution
    To resolve,
    check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
    look for any paths that contain a mapped drive partition
    Change the mapped drive letter to a UNC path (
    server\folder)
    Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
    If the path is not updated to the new path
    Reboot the server
    Regards,
    Sarbhjeet Kaur

  • SQL Server 2005 SSAS connect to BI possible?

    Hi there,
    I have tested the new .Net Data Provider 1.0 for SAP Netweaver BI in SQL Server Reporting Service (SSRS). What I am wondering is that could SQL Server Analysis Service (SSAS) connect to SAP BI, too? How to do this?
    Best Regardly

    Dear Tom,
    You can use Microsoft SQL Server 2005 Integration Services (SSIS) for this connection or through XML for Analysis (XML/A) (an XML standard for Online Analytical Processing - OLAP) it can be done. But I am not sure weather this service is available or not as SQL Server 2005 Reporting Services, which is now certified to run reports on SAP BW.
    As I have never ventured in this, I would suggest you to use documentations of Microsoft SQL Server 2005 Integration Services (SSIS) and SSAS given by MS.
    Also have a look at this doc:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4ab89e84-0d01-0010-cda2-82ddc3548c65
    Hope it helps.
    Regards,
    Ashish

  • Upgrade from SQL Server 2005 to SQL Server Express 2014 Enterprise

    I was just wondering if it is possible to upgrade from SQL Server 2005 to SQL Server Express or will I have to build the environment and then migrate the database?
    Thanks for any help

    Hi Lance_Romance,
    As others’ posts, you don’t have to build new environment and then migrate databases between SQL Server instances, you can use the in-place upgrade strategy to upgrade from SQL Server 2005 to SQL Server 2014 .Please note that SQL Server 2005 SP4 is required
    in this case.
    Before upgrading , I recommend you to use
    upgrade advisor, it can help to analyze your existing SQL Server deployment and inform you of issues that need to be addressed.  In addition, please perform a full server backup prior to performing the in-place upgrade, which will be an important way
    to revert your SQL Server to its previous state if the upgrade does not go as planned. For more details, please review this blog:
    Upgrading to SQL Server 2014: A Dozen Things to Check.
    Thanks,
    Lydia Zhang

  • SQL Server 2005 Installation Error

    I am installine ECC6 on SQL Serer 2006. I have started the SQL Server installation, using the SQL4SAP.vbs and after about 10 minutes the installation stops with an error. I am pointed to a fine Summary.txt but the details in the file do not give a clue on the problem:
    Machine         : SAPDEMO
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
    SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
    Time            : Mon Dec 03 09:09:38 2007
    List of log files:
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core(Local).log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SqlWriter_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_MSXML6_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BOL_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Datastore.xml
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0 LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SNAC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Support.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SCC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_WI.log

    Hi Rajeev,
    Indeed it was a typo error I am attempting SQL Server 2005.
    I am using the 32 bit installation, that has been checked.
    Here are the details from C:\Windows\SQL4SAP.log
    Customized installation of SQL Server 2005 for SAP *
    Log File: C:\WINDOWS\SQL4SAP.log
    Script started 03/12/2007 08:46:25 on SAPDEMO
    System settings:
      Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
      Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
      Win32_ComputerSystem.SystemType=X86-based PC
      Win32_OperatingSystem.OSType=18
      Win32_OperatingSystem.Version=5.2.3790
      Win32_OperatingSystem.ServicePackMajorVersion=2
      Win32_OperatingSystem.Caption=Microsoft(R) Windows(R) Server 2003, Standard Edition
      Win32_OperatingSystem.ProductType=3
      Win32_OperatingSystem.OSProductSuite=272
      Win32_OperatingSystem.OSLanguage=1033
    Windows version:
      OSVersion         = 5.2
      OSFamily          = Windows2003
      OSServicePack     = 2
      OSEdition         = Server
      OSSystemType      = X86
      OSProductSuite    = Terminal Server
      OSMsiVersion      = 3.1.4000.4042
      OSMdacVersion     = 2.82.3959.0
      OSLanguage        = English – United States
      OSLanguageID      = 1033
    Environment on SAPDEMO:
      userDir           = C:\Documents and Settings\Administrator\
      tmpDir            = C:\DOCUME1\ADMINI1\LOCALS~1\Temp\1\
      rootDir           = C:\WINDOWS\
      prgDir            = C:\Program Files\
      prgDirX86         = \
    SQL4SAP version:
      version:          ' v3.2.44    Mar 2007: SQL2005 SP2, Windows2003 SP2
      size:             86124
      created:          30/11/2007 16:59:31
      modified:         20/03/2007 13:36:44
      exe:              C:\WINDOWS\system32\cscript.exe
      script:           C:\SAP_CD\CD2\SQL4SAP.vbs
      C:                C:
    Script path:
      myRoot            = C:\SAP_CD\CD2\
      myDir             = C:\SAP_CD\CD2\x86\
      myDirUNC          = C:\SAP_CD\CD2\x86\
    Script settings:
      SqlAuthInstall    = False
      SilentInstall     = False
      DeEditionOnly     = False
      DeEditionPossible = False
      SapItMsgBox       = False
      SilentRtmSetup    = True
    Service Account:
      "C:\SAP_CD\CD2\x86\SqlCmd\GetSidName.exe" S-1-5-18 =>NT AUTHORITY\SYSTEM
      OSSystemAccount= NT AUTHORITY\SYSTEM
    03/12/2007 08:46:28
    Input Box "Select SQL Server instance"
    No SQL Server instance was found.
    SQL Server Native Client               not installed
    SQL Server 2005 Client Tools           not installed
    Enter a new or existing instance name.
    - for a Default Instance, enter:     (default)   or   .
    - for a Named Instance, enter:       <SID>
    To install SQL Client Tools Only, press Cancel.
    Result: (default)
    Registry settings (1/2):
    HKLM\SOFTWARE\Microsoft\DataAccess\FullInstallVer
    READ: 2.82.3959.0
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    READ: 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    READ: 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\Version
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\PatchLevel
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CurrentVersion
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CSDVersion
    READ:
    03/12/2007 08:46:32
    Message Box "Confirmation"
    You have chosen to install the new instance
    SQL Instance:       (default)
    SQL Version:        9.00.3042
    SQL Edition:        2005 Enterprise Edition
    SQL Collation:      SQL_Latin1_General_CP850_BIN2
    Authentication:     Windows only
    Login sa:           random password, login disabled
    =======================================
    The installation may take 15 minutes or longer
    =======================================
    Do you want to start the installation now?
    Result: vbOK
    03/12/2007 08:46:34
    installing SQL Server 2005 Enterprise Edition on X86 - build 9.00.1399 ...
      Log File:    C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
      Command:     "C:\SAP_CD\CD2\x86\EnterpriseEdition\Servers\setup.exe" /qn USERNAME="SAP ISV Royalty Licensing Program" ADDLOCAL=Connectivity,SQL_Tools90,SQLXML,Tools_Legacy,SQL_Documentation,SQL_BooksOnline,SQL_Data_Files,SQL_FullText PERSEAT=50 INSTANCENAME=MSSQLSERVER SQLCOLLATION=SQL_Latin1_General_CP850_BIN2 AGTAUTOSTART=1 SQLACCOUNT="NT AUTHORITY\SYSTEM" AGTACCOUNT="NT AUTHORITY\SYSTEM" SQLBROWSERACCOUNT="NT AUTHORITY\SYSTEM" DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxxxxxxxxxxxxx
      Return Code: 1605
    03/12/2007 08:48:41
    Log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
    Microsoft SQL Server 2005 9.00.1399.06
    ==============================
    OS Version      : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
    Time            : Mon Dec 03 08:46:48 2007
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server VSS Writer
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server 2005 Books Online (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
    Machine         : SAPDEMO
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
    SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
    Time            : Mon Dec 03 08:48:39 2007
    List of log files:
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core(Local).log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_MSXML6_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Datastore.xml
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0 LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SNAC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Support.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SCC.log
    service MSSQLSERVER does not exist
    03/12/2007 08:48:41
    Message Box "Installation failed"
    The unattended installation failed.
      Installation Step: SQL Server - build 9.00.1399
      Return Code:       1605
      Log File:          C:\WINDOWS\SQL4SAP.log
    Check the log file above!
    See also SAP note 896566 for known issues
    Result: vbOK
    Registry settings (2/2):
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\MSSQLSERVER
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg0
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg1
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg2
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg3
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg4
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg5
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg6
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg7
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg8
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg9
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg10
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg11
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg12
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg13
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg14
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg15
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg16
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg17
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg18
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg19
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg20
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLSERVER\Setup\SQLPath
    READ:
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    WRITE(REG_DWORD): 4
    03/12/2007 08:48:47
    Quit script with return code 1

  • Does OBI SE1 work with SQL server 2005

    Does anybody know if SQL Server 2005 can be used with OBIEE?
    Any responses would be appreciated.

    Yes. Create a new database in the physical layer of the rpd and open the "Database" dropdown in the "Data source definition"...not the "SQL Server 2005" entry there.
    Cheers,
    C.

  • DB mail not working in sql server 2005

    Hi,
    from today i get following error on sql server 2005
     Exception Type: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException
    Message: There was an error on the connection. Reason: Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.
    Data: System.Collections.ListDictionaryInternal
    TargetSite: Void OpenConnection(Microsoft.SqlServer.Management.Common.SqlConnectionInfo)
    I can not send the mail.I am sending the mails same profile that configured.Before it is working perfectly.Today I send the bulk mails(near about 4000-5000 mails) through the java code. And from that time i can not get any mails.
    Please tell me how to solve the problem?

    Hello,
    Please refer to the following thread:
    https://social.technet.microsoft.com/Forums/en-US/c8fa3c2d-9e8a-4886-97bf-264c1b8bc31c/throttling-settings-for-sending-more-that-1500-emails-simultaneously-using-sql-job?forum=exchangesvrsecuremessaging
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL Server Agent - Job History not being recorded (SQL Server 2005)

    I have been trying to get to the bottom of an issue with SQL Server Agent not recording any job history. I am using SQL Server 2005 on a single Windows Server 2008 machine (i.e. no other domain controllers/active directory servers).
    The SQL Server Agent service is configured to 'Log On As' NT user account 'sqlagent'. The jobs themselves are executed successfully (all 'Transact-SQL' type steps actually use the 'sa' account) however the there is no actual job history to be found for any
    of the jobs -- in the SQL Activity monitor, the 'Last Run Outcome' is always 'Unknown' and the 'Last Run' date is always 'Never' for all jobs; in the SQL Job History Viewer there are no entries for any instances of a job being executed.
    The 'sqlagent' NT user account ia a member of the 'Administrators' NT group; the 'Administrators' group appears under Security > Logins on the database server. I have another server that also uses the same setup with a 'sqlagent' NT user account, on that
    database server the 'sqlagent' user account appears under Security > Logins and the SQL job history works correctly. I have attempted to add the 'sqlagent' to the Logins on the affected server using the SQL Server Surface Area configuration but this operation
    returns an error, detailed below.
    Additionally, I have attempted to use the built-in NT system account 'NETWORKSEVICES' to run the SQL Agent Service but this also results in exceptions in the error log and no job history being recorded. The entries in the error logs are very similar to those
    from the 'sqlagent' NT user account but instead the user is referred to as 'NT AUTHORITY\ANONYMOUS LOGON' in the error logs, again these are detailed below.
    Many thanks in advance for anyone's time and help with this issue!
    Arthur
    The following errors are raised in SQL Server Agent > Error Logs each time a job is executed:
    Date 11/11/2012 18:30:01
    Log SQL Agent (Current - 11/11/2012 18:30:00)
    Message
    [298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
    Date 11/11/2012 18:30:01
    Log SQL Agent (Current - 11/11/2012 18:30:00)
    Message
    [382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
    If the SQLAgent service is configured to use the NT system account 'NETWORKSERVICE' then the following errors are returned instead:
    Date 29/10/2012 18:30:15
    Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
    Message
    [298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]
    Date 29/10/2012 18:30:15
    Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
    Message
    [382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
    I have tried granting the 'sqlagent' NT user account with SysAdmin Server Role privaledges using the SQL Server User Provisioning tool in SQL Server Surface Area Configuration, but this always throws the following, similar error:
    Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Error: 18452)
    ===================================
    Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
    Server Name: 127.0.0.1,1344
    Error Number: 18452
    Severity: 14
    State: 1
    Line Number: 65536
    Program Location:
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at sqlprov.SysAdminServerRole.ProvisionInstance(Instance instance, String userName)
       at sqlprov.ProvisionTask.Provision(Instance instance, String userName)
       at sqlprov.MainForm.ProvisionTasks()

    Hi Rama,
    Thanks for your reply. I have run the query you specified and can see only one entry with "NTLM" in the auth_scheme column, all of the rest have "SQL". It figures that the entry with "NTLM" is relating to the one NT user account that can successfully log
    in to the service (as mentioned in my reply to Nag above, this is the NT user account that installed the service on the machine). I have also executed the same query on the other machine that I mentioned in my original post and this contains two "NTLM" entries,
    I'd assume that these relate to the NT user that installed the software and the correctly working "sqlagent" NT user account that is correctly logging the job history on that machine.
    I think the problem is very much to do with granting access to new NT user accounts, as per the KB article that you have quoted above. In this case, it is not relating to scenarios 1 or 2 as these relate to SQL Server logins and this issue is about a Windows
    Authentication login. As I mentioned to Nag above, I am unable to grant any NT user accounts with access to the service however the NT accounts are all defined locally on the same machine as the SQL server is installed (i.e. there is no domain controller,
    active directory controller, etc) so I don't understand how the Windows login cannot be verified.
    Any further advice on the issue would be greatly appreciated, please let me know if there is any more information I can provide to help diagnose the problem.
    Many thanks!
    Arthur

  • SQL Server 2005: Multi-part identifier could not be bound

    Hello,
    I use IBM WebSphere Portal and am desperately trying to move data from the default Cloudspace Database to MS SQL Server 2005, of course following the official guidelines.
    What happens is that WebSphere's Configuration Wizard fails because of an error caused by the SQL Script. Trouble is, I can't bring it to work not even in the SQL Server Management Studio.
    What follows is the code generated by the script. The error is caused by the last "check"-constraint (colored in red).
    CREATE TABLE community.APP_DESC (
    OID BINARY(18) NOT NULL,
    TYPE INTEGER NOT NULL,
    APP_NAME NVARCHAR(255) NOT NULL,
    IS_ACTIVE INTEGER NOT NULL,
    JSR_VERSION NVARCHAR(255),
    GUID NVARCHAR(255),
    WEB_MOD_OID BINARY(18),
    WEB_MOD_SL BINARY(18),
    WSRP_PROD_OID BINARY(18),
    WSRP_PROD_SL BINARY(18),
    DEFAULT_LOCALE NVARCHAR(64),
    CREATED BIGINT NOT NULL,
    MODIFIED BIGINT NOT NULL,
    WSC_GROUP_ID NVARCHAR(255),
    CONSTRAINT PK20 PRIMARY KEY NONCLUSTERED (OID),
    CONSTRAINT FK20A FOREIGN KEY (WEB_MOD_OID) REFERENCES community.WEB_MOD (OID) ON DELETE CASCADE,
    constraint FK20B FOREIGN KEY (WSRP_PROD_OID) REFERENCES community.WSRP_PROD (OID) ON DELETE CASCADE,
    CONSTRAINT CC20A CHECK (((community.APP_DESC.WEB_MOD_OID IS NULL) AND (community.APP_DESC.WEB_MOD_SL IS NOT NULL)) OR ((community.APP_DESC.WEB_MOD_OID IS NOT NULL) AND (community.APP_DESC.WEB_MOD_SL IS NULL)))
    And that's what SQL Server 2005 told me:
    Msg 4104, Level 16, State 1, Line 1
    The multi-part identifier "community.APP_DESC.WEB_MOD_OID" could not be bound.
    Msg 4104, Level 16, State 1, Line 1
    The multi-part identifier "community.APP_DESC.WEB_MOD_SL" could not be bound.
    Msg 4104, Level 16, State 1, Line 1
    The multi-part identifier "community.APP_DESC.WEB_MOD_OID" could not be bound.
    Msg 4104, Level 16, State 1, Line 1
    The multi-part identifier "community.APP_DESC.WEB_MOD_SL" could not be bound.
    BTW, as this is a generated script I do not have the possibility to change it. Because it has been released by IBM I am rather convinced that it is correct - therefore I was wondering whether SQL Server 2005 has a known bug that makes it refuse "check"-constraints.
    Any hint is very appreciated.
    Thanks in advance,
    adapter

    THe problem is that is was probably not made for SQL Server 2005. It should read:
    CONSTRAINT PK20 PRIMARY KEY NONCLUSTERED (OID),
    CONSTRAINT FK20A FOREIGN KEY (WEB_MOD_OID) REFERENCES community.WEB_MOD (OID) ON DELETE CASCADE,
    constraint FK20B FOREIGN KEY (WSRP_PROD_OID) REFERENCES community.WSRP_PROD (OID) ON DELETE CASCADE,
    CONSTRAINT CC20A CHECK (((APP_DESC.WEB_MOD_OID IS NULL) AND (APP_DESC.WEB_MOD_SL IS NOT NULL)) OR ((APP_DESC.WEB_MOD_OID IS NOT NULL) AND (APP_DESC.WEB_MOD_SL IS NULL)))
    The meaning of the first identifier changed in SQL Server 2005, as this is now the Schema and not the owner. DO you have a chance of using a SQL Server 2000 computer ? In terms of licences you will have a downgrade licence for the SQL Server, otherwise you should ping the IBM guys to provide a compatible script.
    HTH, Jens K. Suessmeyer.
    http://www.sqlserver2005.de

  • Troble configuring Hyperion Shared Services with SQL Server 2005

    I recently installed SQL server (SQL SERVER 2005) in my machine and then am trying to install Hyperion (9.3.1) products. I started with Shared services. It was installed successfully. Problem is occuring when am trying to configure Shared service with SQL database using Hyperion Configuration utility (9.3.1)
    The error which is popping up is
    Unable to connect to the database for the product Hyperion Shared Services.
    Things which I tried from my end
    1. Made sure TCP IP Protocol was enabled in SQL server configuration server.
    2. hypuser was created in SQl server.
    3. hypdb was created in SQL server.
    4. Was having dynamic IP address so install Loopback adapter to obtain Static IP address and port.
    5. Port and IP address was correct.
    Let me know where I am going wrong.
    Any help will be greatly appreciated.

    Finally got it fixed firewall settings needed to be change : This document helped me a lot to troubleshoot the issue
    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)
    This problem may occur when SQL Server 2005 is not configured to accept incoming local and remote connections, which is disabled by default in SQL Server 2005 Express Edition, SQL Server 2005 Developer Edition and also SQL Server 2005 Enterprise Edition. To solve the connection forbidden problem, SQL Server 2005 needs to configure to allow incoming local and remote connections.
    Firstly, ensure that SQL Server 2005 is configured properly to allow incoming connections on the instance of database server, else enable and turn on the local and remote connections setting.
    Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Surface Area Configuration.
    On the “SQL Server 2005 Surface Area Configuration” page, click Surface Area Configuration for Services and Connections.
    On the “Surface Area Configuration for Services and Connections” page, expand Database Engine tree, click Remote Connections.
    Select Local and remote connections, or Local connections only which applicable only if there is no remote system tries to connect to the SQL Server, useful when you just trying to connect and authenticate with the server after installing.
    Select the appropriate protocol to enable to local and/or remote connections environment. To ensure maximum compatibility, select Using both TCP/IP and named pipes.
    Click Apply button when done.
    Click OK button when prompted with the message saying that “Changes to Connection Settings will not take effect until you restart the Database Engine service.”
    On the “Surface Area Configuration for Services and Connections” page, expand Database Engine, then click Service.
    Click Stop button to stop the SQL Server service.
    Wait until the MSSQLSERVER service stops, and then click Start button to restart the MSSQLSERVER service.
    Secondly, SQL Server Browser service has to be enabled to allow for local and remote connections if SQL Server 2005 is running by using an instance name and users are not using a specific TCP/IP port number in the connection string.
    Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Surface Area Configuration.
    On the “SQL Server 2005 Surface Area Configuration” page, click Surface Area Configuration for Services and Connections.
    On the “Surface Area Configuration for Services and Connections” page, click SQL Server Browser.
    Select Automatic as the Startup type to start SQL Server Browser service automatically every time system starts.
    Click Apply button.
    Click on Start button to start the service immediately.
    Click OK button.
    Finally, if remote computer needs to connect and access SQL Server, an exceptions in Windows Firewall included in Windows XP SP2 (Service Pack 2), Windows Server 2003 and Windows Vista needs to be created. If you’re using third-party firewall system, the exception rules also needed to be created to allow external remote connections to the SQL Server 2005 and SQL Server Browser Service to communicate through the firewall, else connections will be blocked. Consult the firewall manual for more details. Each instance of SQL Server 2005 must have its own exception, together with an exclusion for SQL Server Browser service.
    SQL Server 2005 uses an instance ID as part of the path when you install its program files. To create an exception for each instance of SQL Server, you must identify the correct instance ID. To obtain an instance ID, follow these steps:
    Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Configuration Manager.
    In “SQL Server Configuration Manager”, click the SQL Server Browser service in the right pane, right-click the instance name in the main window, and then click Properties.
    On the “SQL Server Browser Properties” page, click the Advanced tab, locate the instance ID in the property list.
    Click OK button.
    Then create an exception for SQL Server 2005 in Windows Firewall.
    Click on Start button, the click on Run and type firewall.cpl, and then click OK. For Windows Vista, type firewall.cpl in Start Search box and press Enter key, then click on Allow a program through Windows Firewall link on left tasks pane.
    In “Windows Firewall”, click the Exceptions tab, and then click Add Program.
    In the “Add a Program” window, click Browse button.
    Click the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe executable program, click Open button. MSSQL.1 with is a placeholder for the instance ID that is obtained from previous procedure. Note that the path may be different depending on where SQL Server 2005 is installed.
    Click OK button.
    Repeat steps 1 through 5 for each instance of SQL Server 2005 that needs an exception.
    For SQL Server Browser service, locate the C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe executable program, and click Open button.
    Click OK button.

  • Replication Configuration issue after migrating from SQL Server 2005 to SQL Server 2008 R2

    Hi All,
    This weekend we have migrated one of our Core system from SQL Server 2005 SP3 to SQL Server 2008 R2 SP2. Migration went successful. However when we are trying to Configure transaction replication we are getting below Error:
    Msg 21854, Level 16, State 1, Procedure sp_MSrepl_addarticle, Line 573
    Could not add new article to publication 'abc' because of active schema change activities or a snapshot is being generated.
    Background:
    Database compability Changed from 90 to 100.
    A quick Help would be appreciated.
    Best Regards - Viral
    Thanks - Viral

    Is a snapshot being generated? the message seems to indicate one is.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • MSS SQL Server 2005 - Partitioning - Review Note 869407 for Status

    I was reviewing OSS Notes today in preparation for applying BW 3.5 Support Stacks 16 - 18 and stumbled on this note regarding partitioning on SQL Server.  Thought I'd share it.  Read the full note if partitioning on SQL Server is something you want.
    <a href="https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=869407&nlang=&smpsrv=">Note 869407 - Partitioning on MS SQL Server 2005</a>
    MS SQL Server 2005 partitioning in BW 3.5 (NW04) and 7.0 (NW04s).
    This note is only valid for MS SQL Server 2005 pilot customers.
    If you implement this note on your MS SQL Server 2005 you should first contact SAP because partitioning on MS SQL Server 2005 is still in a partitioning pilot phase .
    The current pilot phase for SQL 2005 table partitioning was extended and will end approx mid/end of 2006 although SQL 2005 is already available.

    First of all please be aware HSODBC has been desupported since 15th of March 2008. When starting a new project you should start with a supported product and this product is called DG4ODBC and it is available as release 11.
    Looking at the provided listener it shows several configurations issues.
    Have a lokk at yout tnsnames.ora => you mentioned to use the listener servicing port 1521.
    This Listener serves 2 SIDs with the same name:
    SID_DESC =
    (SID_NAME = yscc02)
    (ORACLE_HOME = /u01/app/oracle/product/101)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = yscc02)
    (ORACLE_HOME = /u01/app/oracle/product/101)
    (PROGRAM = hsodbc)
    (ENVS = "LD_LIBRARY_PATH=/u01/app/oracle/product/101/lib32:/usr/lib:/u01/app/oracle/product/101/hs/lib32")
    So when you now connect, the listener does not know which service to spawn. Please check out Metalink note:
    Note.238771.1 How to Setup Generic Connectivity - HSODBC - on AIX
    when you want to continue using HSODBC although I strongly recommend you to use DG4ODBC which is configured as mentioned in Metalink note:
    Note.561033.1 How to Setup DG4ODBC on 64bit Unix OS (Linux, Solaris, AIX, HP-UX)

  • EPM 11 Configuration with SQL Server 2005

    Hello,
    I am having a terrible time trying to get the EPM System Configurer to communicate with SQL Server 2005 Evalution. I keep getting the error "Cannot open database "server" requested by the login. The login failed." I have the windows firewall turned off. The protocol TCPIP is turned on and other protocal are turned off. Any suggestions. Thanks in advance.

    As John mentioned it is supposed to be supported in a future release. That version would be 11.2 -- there will be a version coming out before 11.2 and it will not support 2008.
    Regards,
    John A. Booth
    http://www.metavero.com

Maybe you are looking for

  • Need help in framing an SQL query

    Hi , Requirement is that Let's say I have a table say X I am passing two input params from UI and in DAO i am querying these input prams against the table X(has c1,c2 as columns ) (as it has two columns mapping the input params A,B from UI). if eithe

  • Add and remove option in DataGrid in flex

    Dear Friends,                 I have a datagrid which we can add a row and remove the row.In this DataGrid when i clicked to add new row im getting check Box at first,which i dont want to need at first.Pls help me regarding this.Please find the scree

  • Itunes store does not load

    Hello, I am unable to connect to itunes store. There is no error message showing. Just the loading bar moves half way accross and then I am left with a white screen. I have checked the following; internet works fine, i am able to dowload music art, m

  • PC wont recognize iphone4 after restore failure trying to upgrade to OS5

    After trying to upgrade to OS5, I received a failure notice on the restore and it said to update my Windows7 and restart. Now my PC will not recognize the iphone as a device in MyComputer or in iTunes.  The phone just displays the illustration screen

  • Spool Not Visible in SM37

    Hi, I have a program which when executed in background mode doesnot show spool in sm37, but when i go into spool directory. I am calling the back ground through functional module POPUP_TO_CONFIRM_STEP, case xx when 'N'.       sy-ucomm = 'SJOB'.