Online Indexing in SQL Server 2005 in SAP

Hi SDN,
I had a requirment where i need to create a index in SQLPLUS.
please let me know the transaction code where we will create index in SAP with SQLPLUS.
i need to create index with code like this.
create index z03 on AFRU (fileds) online = ON.
please tell me where we will create this in SAP

sap note had provided these steps
For tables larger than 1GB:
You may need a long time to create the index. Database specific options may
be available to accelerate index creation.
When you want to use a database specific method to accelerate index
creations you can use the following method:
1. Create the index on the Development system using transaction
SE11 (ABAP Data Dictionary).
Note the exact name of the created index.
2. Create the index with the exact name on the Quality assurance system
on database level using the database specific tool (see below).
3. After the index is successfully created, transport the index
to the quality assurance system. This will only transport the
ABAP Dictionary information. As the index already exists, it
is not created after the transport.
4. If steps 2. and 3. are successful repeat these steps on the
productive system.
Database specific acceleration possibilites for index creation
Oracle:
Create the index using SQLPLUS with the following command:
create index <index name> on <table name> ( <field1, field2, ...> )
nologging tablespace <tablespace name>
parallel (degree <number>)
storage <storage clause>
..........online;
Replace <index name> by the exact name of the index
Replace <field1, field2, ...> by the fields of the index
Replace <tablespace name> by the tablespace where the index should be
stored
Replace <number> by the number of CPUs you want to use for index
creation
Replace <storage clause> by the storage clause for the index
Please refer to the Oracle handbook for more details.
Edited by: Naresh Nelapatla on Mar 18, 2009 3:00 PM

Similar Messages

  • Reporting Services of SQL Server 2005 in SAP B1

    Hi,
    Can I used Reporting Services of SQL Server 2005 in SAP B1? If  yes then please guide me how can I do it. If not then is it possible to use these services in 8.8 version?
    Regards,
    Ghazanfar

    Hi Ghazanfar,
    The answer is YES.  You may check this blog:
    /people/community.user/blog/2008/07/04/sql-server-reporting-magic
    Thanks,
    Gordon

  • Changing installation PATH on SQL Server 2005 with SAP DVD

    Hi experts,
    i would like to install SQL Server 2005 delivered by SAP on another disk, for example D: instead of C:\Program files\
    i read the note 363018 but there's no solution to my problem.
    Thanks in advanced for your help.
    Pascal.

    Hi Markus,
    yes, that's what i have expected but i m not good enought to find the changement to do.
    Am i allowed to post the script?
    Thanks.

  • Failing to connect SQL Server 2005 from SAP

    I'm trying to connect SQL database to write some data to an external sql table. But it's failing giving below message,
    Error Message returned from "ADBC_TEST_CONNECTION" program:
    Testing a Database Connection Defined in DBCON        
    Could not open connection EACT_MESSAGES               
    sql error          1- occured:                        
    Login timeout expired                                                                               
    I can connect from .NET Applications using the same connection string configuration.
    What could be the reason for this.
    Do I need to enable some service for this in SQL server. I have enabled all possible SQL related services.
    But still no luck.

    I found a solution..
    Instead putting the server name, used IP address which is static. that solved the issue.

  • Installing SAP R/3 with SQL Server 2005..

    Hi,
    Microsoft is about to release "SQL 2005" in Nov05. Has anybody in here thought of installing/upgrading SAP on MS-SQL's latest version of the database server. On doing some research on the net I noticed that Microsoft has already upgraded their SAP R/3 environment to the beta edition of SQL Server 2005. I did not find any information on SAP having certified SQL Server 2005 yet.
    Do we have to wait till ECC6.0 or whatever the new version of ECC would be to leverage the SQL Server 2005 D/b ?
    Any thoughts/information on the readiness of SQL Server 2005 for SAP R/3 would be appreciated.
    Jay

    Hi Jay,
       Past experience says SAP won't support a new platform (e.g. DB, OS, etc) until they have had a chance to test it.  Your official SAP document for what is supported is in the Product Availability Matrix.  http://service.sap.com/pam
    With that said, that doesn't mean that you can't try it out. Of course not in a test environment. You get some very good learning experiences from trying.  But don't enter a customer message about a non supported platform.
    Good luck,
    John

  • Upgrade SQL Server 2000to SQL Server 2005 in an SAP environment

    Hi,
    I have a scenario in which we are going to upgrade SQL server 2000 to SQL server 2005 in SAP an environment.
    Now SQL server has a concept of In-Place Upgrade and Side-by-Side Migration Process.I want to know what does both of these mean.
    We have an SAP note(799058.It talks about the upgrade in Step II.Is it the same as In-Place Upgrade concept in SQL?
    What is step III in the note talking about? Is it talking about Side-by-Side Migration?
    It would be of gr8 help if someone could provide the conceptual knowledge on these and what does the note mentioned above talks.

    Hello
    Please review my post on SQL upgrade.
    SAP on SQL Server
    You may also like to review
    http://www.microsoft.ie/downloads/itprosql-90.ppt#568,17,Demo
    Can you please advise your DB size and the max. amount of downtime your business can afford?
    I will check, but I am almost sure that a side-by-side SQL upgrade is not appropriate for SAP systems.
    Thanks
    N.P.C

  • 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

  • Log File Issue In SQL server 2005 standard Edition

    We have database of size 375GB .The data file has 80 GB free space within .When trying to rebuild the index we had 450 GB free space on the disk where Log file is residing.The rebuild index activity failed due to space issue.added more space and got the
    job done successfully
    The Log file has grow up to 611GB to complete the rebuild index.
    version :SQL server 2005 Standard Edition .Is ther a way to estimate the space required for rebuild index in this version.
    I am aware we notmaly allocate 1.5 times of data file.But in this case It was totaly wrong.
    Any suggestion with examples would be appreciated.
    Raghu

    OK, there's a few things here.
    Can you outline for everybody the recovery model you are using, the frequency with which you take full, differential and transaction log backups.
    Are you selectively rebuilding your indexes or are you rebuilding everything?
    How often are you doing this? Do you need to?
    There are some great resources on automated index maintenance, check out
    this post by Kendra Little.
    Depending on your recovery point objectives I would expect a production database to be in the full recovery mode and as part of this you need to be taking regular log backups otherwise your log file will just continue to grow. By taking a log backup it will
    clear out information from inactive VLF's and therefore allow SQL Server to write back to those VLF's rather than having to grow the log file. This is a simplified version of events, there are caveats.
    A VLF will be marked as active if it still has an open transaction in it or there is a HA option that still requires that data to be available as that data has not been copied to another node yet.
    Most customers that I see take transaction log backups every 15 - 30 minutes, but this really does depend upon how much data your company can afford to lose. That's another discussion for another day.
    Make sure that you take a transaction log backup prior to your job that does your index rebuilds (hopefully a smart job not a sledge hammer job).
    As mentioned previously swapping to bulk logged can help to reduce the size of the amount of information logged during index rebuilds. If you do this make sure to swap back into the full recovery model straight after and perform a full backup. There are
    problems with the ability to do point in time restores whilst in the bulk logged recovery model, so you need to reduce the amount of time you use it.
    Really you also need to look at how your indexes are created does the design of them lead to them being fragmented on a regular basis? Are they being used? Are there better indexes out there that can help performance?
    Hopefully that should put you on the right track.
    If you find this helpful, please mark the post as helpful,
    If you think this solves the problem, please propose or mark it an an answer.
    Please provide details on your SQL Server environment such as version and edition, also DDL statements for tables when posting T-SQL issues
    Richard Douglas
    My Blog: Http://SQL.RichardDouglas.co.uk
    Twitter: @SQLRich

  • SAP and Database Encrption on SQL Server 2005 or 2008

    Hi.  I searched as best I could for any existing threads on this topic, and could not find any, so I hope it's OK to raise a new one.
    We're running SAP ECC 6.0 on a SQL 2005 database.  Database size is around 3.3 TB, with Trans Log of about 550GB, storage is HP EVA.
    I've been asked to report on how Database Encryption would impact our systems, both from the perspective of enabling it initially and then how it would affect performance going forward.
    I've read a few White Papers,  for example:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4ab89e84-0d01-0010-cda2-82ddc3548c65?QuickLink=index&overridelayout=true
    .. and from what I'm reading, it looks like I would want to be moving to SQL Server 2008 as a first step.  Does anyone have any experience of implementing SQL encryption for a SAP database, either in 2K5 or 2K8?
    All comments or help will be welcomed.
    Thanks
    Steven Clark

    Hello Steven,
    You can also check the following websites:
    http://blogs.msdn.com/b/saponsqlserver/archive/2011/09/05/decreased-disk-space-requirement-for-sap-unicode-systems.aspx
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50c5de8f-282a-2e10-cb8a-a5859a0994a4&overridelayout=true
    And, SAP notes:
    [1581700 PAGE compression support for DDIC & Hom./Het. System Copy|http://service.sap.com/sap/support/notes/1581700]
    [1488135 Database compression for SQL Server|http://service.sap.com/sap/support/notes/1488135]
    Regards,
    Eduardo Rezende

  • Size of SQL Server 2005 Database for SAP B1 2005 B is heavy

    Hi all,
    In my company we are working with SAP B1 2005 B SP 25.
    Our Database is in SQL Server 2005. Its Size reaches 6 GB in less then two years periods.
    Can Any body guide me to reduce the size or how to maintain database. Can we split Database in SAP B1 ?
    Due to the size users getting less speed
    Awaiting your valuable guidance for the same.
    Best Regards,
    Chintesh Soni

    Hi Chintesh,
    I would advise caution doing any of the things suggested in SAP Note 548772. In particular, I strongly recommend you do NOT set auto-shrink on. This is a really bad idea on a production database and I can't understand why SAP would suggest it.
    Is it the data file that is 6GB or the overall size of the database (ie data and log files)? If your log file is large  then this can slow performance. I recommend setting up transaction log backups on an hourly basis. This is good practice and not only keeps the log file healthy but also gives you the option to recover your data to the last transaction log backup in the case of an emergency. If you don't want transaction log backups then do as the SAP note mentions and set the recovery model to simple and do a once-off truncation of the log file.
    Are you doing regular maintenance on the database (ie rebuilding indexes, updating statistics)? Are you monitoring fragmentation on the data drive and doing a defrag occasionally to keep the drive healthy?
    Kind Regards,
    Owen

  • Issue in rebuilding index after restoring database from sql server 2005 to 2012

    Hi All,
    We have recently restored a database named DBA_admin from our sql server 2005 instance to sql server 2012 and we have added the database to out weekly maintenance plan. After adding the database to maintenance plan the job is failing every weekend due to
    below error message.
    Error message from maintenance plan history:
    Executing the query "ALTER INDEX [PK_lsttype] ON [dbo].[lstAssign..." failed with the following error: "Invalid object name 'admin.dbo.databaselog'.
      ALTER_INDEX - dbo.PK_lsttype". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
    Below is the code within the maintenance plan which the rebuild index task is using for database dba_admin:
    USE [dba_admin]
    GO
    ALTER INDEX [PK_lstType] ON [dbo].[lstType] REBUILD PARTITION = ALL WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 98, DATA_COMPRESSION = PAGE)
    Please let me know if any one knows how to fix this issue.
    Thanks in Advance.

    Sorry for the confusion.
    Here is what is happening.
    The query is failing while trying to rebuild index [Pk_lsttype] on table [lstAssign], both these objects belong to database
    admin.
    I have verified the old instance there is table databaselog within the database
    dba_admin, but in new SQL instance within the database dba_admin the table is not present.
    Even I'm not sure of what this table databaselog has to do with rebuilding indexes on table
    lstAssign within the admin database.
    I have manually tried to execute the alter index command within the database
    admin and it is failing with the below error.
    ALTER_TABLE - dbo.Query_pnb_sms
    Msg 208, Level 16, State 1, Procedure ddlDatabaseTriggerLog, Line 39
    Invalid object name 'dba_admin.dbo.databaselog'.

  • SQL server 2005 SP3 can run SAP B1 2005A SP01 PL51

    Hi All,
    I could successfully install SAP B1 2005A SP01 PL51 in the SQL server 2005 SP3.
    In this link:
    http://service.sap.com/smb/sbo/platforms
    you won't find it such info.
    Why I upgrade, it is caused by the printing error issue using citrix.
    Anyone of you that have problem after run the B1 on that SQL, pls share.
    Someone who need webex file that shows the install process can request it to me. Let me know.
    Rgds,

    Hi Arshdeep,
    Thx for your reply. I just wonder why SAP did not inform the availability SP3 from Microsoft and the explanation about the inapplicable of SP3 for SAP B1 in the B1 platform link.
    I have  tested without using any steps and any other procedures. Practice is a good lesson to learn for me. Nevertheless, one concern from modern customers are the compatibility or adaptibility of SAP B1 to Microsoft product especially SQL since it is one of database platform.
    Old-fashioned customer will disregard that because they will think as long as my SAP B1 and SQL server still run well, I don't care..
    Rgds,

  • How to install mini SAP in MS SQL Server 2005 Express?

    Hi, is anyone know how to install the mini SAP v4.6 by using MS SQL Server 2005 Express?
    I get error when connecting to the Database at 88% of the installation.
    Please help. Thank you.

    I do not think you can install miniSAP 4.6D on MS SQL server 2005 express.
    1) you need the up todate patch to run on MSSE. If  SAP did the work to allow it to run, it would be patch 55+. As supplied it is patch zero.
    2) You can install on MSDE (MS SQL server 2000) patch 4. Look for my post INFO: Installing MiniSAP 4.6D on a named instance of MSDE (MS-SQL).
    3) after the install on MSDE SP4 you would have to change the database code page to 'BIN2' look for the OSS note.
    4) then you can start patching through to the most recent.
    The main reason you cannot do this is MS have changed the version key format to include '.6' as extra info which SAP cannot interprate, too many dots.
    MattG.
    Message was edited: add URL

  • UDCONNECT (SQL SERVER 2005 - SAP BW 7.0 Unix)

    Hi,
    I´m trying connect SQL Server database with SAP BW 7.0 (running over Unix) using UDCONNECT.
    I have done all steps as defined in SAP document:
        How to Configure UD Connect on the J2EE Server for JDBC Access to External Databases
    But when I try to check the connection against database through URL:
    http://:/Tjdbc/servlet/TestJdbc
    the system returns the next error:
    Test JDBC Page
    Error!
    Could not connect to database. Connection is inactive or does not support JDBC.
    Go back
    Exception Details:
    com.sap.ip.bi.sdk.exception.BIConnectionFailedException: Cannot open the connection
         at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:238)
         at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getConnection(JDBCModel.java:796)
         at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getTables(JDBCModel.java:132)
         at com.sap.ip.bi.sdk.trialarea.connector.servlet.controller.Control2.doPost(Control2.java:25)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    I have checked with two diferents SQL Servers and the result was the same.
    The databases support TCP/IP connections and port 1433 is open.
    Thanks in advance.

    I used Microsoft JDBC V 1.1 to connect my BW on Solaris to SQL 2005. This is the only 1 version that i can make it work. Other version 1.0 , 1.2 and 2.0 (requires JDK 5 but we are on 1.4 ) did not work for us.
    Best Regards

  • Client transport  between SAP on Oracle 10G and MS SQL server 2005

    Hi Folks,
    We have a requirement where we have to do client export/import from SAP ECC 6.O running on Oracle 10g and to SAP ECC 6.0 running on MS SQL server 2005.I want to know whether SAP supports this and patch levels of all components two systems should be the same.
    Thanks in advance,
    Basis Admin

    Not recommendet because of potential :
    -  patch level inconsistency
    - ABAP dictionary inconsistency (programs, tables)
    - possible client independent configuration conflicts
        existing config cen disturb "imported" client
        imported config can ddisturb  existing clients
    If there are any inconsistencies mentioned above you are in trouble...
    regards,
    wojtek

Maybe you are looking for