Best SQL Server 2005 books

Hi,
I am trying to determine a couple of books that will help me understand SQL Server 2005 from a few of perspectives:
Optimizing databases, specifically from SQL 2000 - I have a recommended book Pro SQL Server 2005 Database Design and Optimization
Developing SQL Server 2005 based applications using VIsual Studio 2005 and .NET 2.0 - I have been unable to narrow down to a specific book here. I learn best by example, so I was hoping for a book that basically goes through implementing a "real world" project from scratch to finish. I am going to be using the full-blown enterprise edition of SQL 2005, not the Express Edition; but a book that uses the Express Edition trumps any other book, I would be open to it. Any suggestions on such a book?
Understanding T-SQL and Stored Procedures from a SQL Server 2005 perspective -- Any suggestions? A book that spells out the differences from SQL 2000 would be an added advantage.
Thanks.

Have a look at Itzik Ben-Gan's book:
http://en.bookfi.org/g/Itzik%20Ben-Gan
Here the below, we have a good collection of books
http://www.onlinevideolecture.com/ebooks/it-ebooks/index.php?subject=Microsoft%20SQL%20Server

Similar Messages

Error 1406 while installing SQL server 2005 on windows 2003 64 bit standard

Hi Gurus,
When I am trying to install SQL SERVER 2005 on Windows Serevr 2005 i get the error code 1406
I tried using the script sql4sap.vbs. and tried to set the named instance.
please suggest
Please find the contents of the 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 Apr 14 14:51:07 2008
Machine         : UKSAPTEST02
Product         : .NET Framework 2.0
Product Version : 2.0.50727
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_.NET Framework 2.0.log
Last Action     : InstallFinalize
Error String    :Could not write value to key \Software\Classes\.appref-ms
Error Number    : 1406
UKSAPTEST02 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
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 Apr 14 14:52:26 2008
List of log files:
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_Core.log
Many thanks
Sreeram
Edited by: sreeram kaki on Apr 14, 2008 6:12 PM

Hi Clas,
Thanks for the valuable suggestions,
I tried to install the database (sql server 2005) using the local admin password on another server which do not have the antivirus installed. I started the installation at 3:15 PM today and the installation is still in progerss
please see the log below from 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            : Tue Apr 15 15:04:28 2008
Machine         : UKSAPTEST01
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\SQLSetup0001_UKSAPTEST01_SQLSupport_1.log
Machine         : UKSAPTEST01
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\SQLSetup0001_UKSAPTEST01_SQLNCLI_1.log
Machine         : UKSAPTEST01
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\SQLSetup0001_UKSAPTEST01_SqlWriter_1.log
Machine         : UKSAPTEST01
Product         : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_1.log
Machine         : UKSAPTEST01
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\SQLSetup0001_UKSAPTEST01_SQLSupport_2.log
Machine         : UKSAPTEST01
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\SQLSetup0001_UKSAPTEST01_SQLNCLI_2.log
Machine         : UKSAPTEST01
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\SQLSetup0001_UKSAPTEST01_BOL_1.log
Machine         : UKSAPTEST01
Product         : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_2.log
Also see the last few lines of the log file
SQLSetup0001_UKSAPTEST01_SQL.log
Action start 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Deleting Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 0 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Adding Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
MSI (s) (C0!50) [17:10:43:815]: Doing action: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:830]: PROPERTY CHANGE: Deleting Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlGroupMember' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlGroupMember : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:830]: Doing action: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:50) [17:10:43:830]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D8.tmp, Entrypoint: Write_sqlUserSecurity
Action start 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlUserSecurity
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlUserSecurity
PerfTime Start: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<Func Name='Write_sqlUserSecurity'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Adding Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeChan
MSI (s) (C0!34) [17:10:43:924]: Doing action: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Deleting Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$
Action ended 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlUserSecurity' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:940]: Doing action: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:10) [17:10:43:940]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D9.tmp, Entrypoint: Write_sqlFileSDDL
Action start 17:10:43: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlFileSDDL
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlFileSDDL
PerfTime Start: Write_sqlFileSDDL : Tue Apr 15 17:10:43 2008
Thanks & Regards,
Sreeram
Edited by: sreeram kaki on Apr 15, 2008 6:45 PM

SQL Server 2005 Dev Integration Services Fail

I've got VS2005 v.8.0.50727.867 (vsvista.050727-8600) on my 64bit Windows 7 box. I am trying to install SQL Server 2005 Integration Services on this Win7 box so I can load and edit the Win XP SSIS projects that I had on my XP box. So far I've
not been able to successfully install the Integration Services with a failed permission on the SQL**DTD.msi file.....I've copied this file locally and tried to run it and it would start but then would give permission error.
Is there an inherent incompatibility running SSIS projects in SQL Server 2005 on a 64bit Win 7 box? Worked great on my XP box.
I've been "upgrading" the SSIS projects to VS2008 since I was able to get SSIS installed. Any ideas what I need to do to get this beast to work?
TIA
Harry

Thanks Alberto
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version      : Professional Service Pack 1 (Build 7601)
Time            : Mon Aug 25 09:31:30 2014
DT0315 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features,
install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL
Server in Books Online.
DT0315 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
Machine         : DT0315
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\SQLSetup0007_DT0315_SQLSupport_1.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_1.log
Machine         : DT0315
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\SQLSetup0007_DT0315_SQLSupport_2.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_1.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_2.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_2.log
Machine         : DT0315
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\SQLSetup0007_DT0315_SQLSupport_3.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_2.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_3.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_3.log
Machine         : DT0315
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\SQLSetup0007_DT0315_SQLSupport_4.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_3.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_4.log
Machine         : DT0315
Product         : Microsoft VSS Writer for SQL Server 2012
Product Version : 11.0.2100.60
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SqlWriter_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_4.log
Machine         : DT0315
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\SQLSetup0007_DT0315_SQLSupport_5.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_4.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_5.log
Machine         : DT0315
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\SQLSetup0007_DT0315_BOL_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_5.log
Machine         : DT0315
Product         : Integration Services
Error           : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Integration Services (64-bit)
Product Version : 9.00.1399.06
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_DTS.log
Last Action     : InstallFinalize
Error String    : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Error Number    : 29549
Machine         : DT0315
Product         : SQLXML4
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQL.log
Machine         : DT0315
Product         : SQLXML4
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_2.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Analysis Services (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_AS.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Notification Services (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_NS.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Tools (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_Tools.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

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

License type of SQL Server 2005 Best Practices Analyzer

Hi everybody.
I need to install in my organization the software "SQL Server 2005 Best Practices Analyzer" but I need to know if this application it's free licensing. I have seen on several web sites about this tool it's free but not in official microsoft
web page. So, where can I find the official microsoft information about the type of licensing of "SQL Server 2005 Best Practices Analyzer" ?
Thanks of your support

Hello Erland.
I followed your advice and I have read the terms of use of this software. I stop at point 3 (which I highlighted). Based on this point, I doubt it is about using this application. Furthermore nowhere says that this software is free to use.
Would appreciate if someone can clarify this to me.
=============================================================
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT SQL SERVER 2005 BEST PRACTICES ANALYZER:
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you.
Please read them. They apply to the software named above, which includes the media on which you received it, if any.
The terms also apply to any Microsoft
* updates,
* supplements,
* Internet-based services, and
* support services
for this software, unless other terms accompany those items.
If so, those terms apply.
BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS.
IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE.
If you comply with these license terms, you have the rights below.
1.
INSTALLATION AND USE RIGHTS. You may install and use any number of copies of the software on your devices.
2.
INTERNET-BASED SERVICES. Microsoft provides Internet-based services with the software.
It may change or cancel them at any time.
3.
SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software.
Microsoft reserves all other rights.
Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement.
In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways.
You may not
* work around any technical limitations in the software;
* reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;
* make more copies of the software than specified in this agreement or allowed by applicable law, despite this limitation;
* publish the software for others to copy;
* rent, lease or lend the software;
* transfer the software or this agreement to any third party; or
* use the software for commercial software hosting services.
4.
BACKUP COPY. You may make one backup copy of the software.
You may use it only to reinstall the software.
5.
DOCUMENTATION. Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes.
6.
EXPORT RESTRICTIONS. The software is subject to United States export laws and regulations.
You must comply with all domestic and international export laws and regulations that apply to the software.
These laws include restrictions on destinations, end users and end use.
For additional information, see www.microsoft.com/exporting.
7.
SUPPORT SERVICES. Because this software is "as is," we may not provide support services for it.
8.
ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services and support services that you use, are the entire agreement for the software and support services.
9.
APPLICABLE LAW.
a. United States. If you acquired the software in the United States, Washington state law governs the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles.
The laws of the state where you live govern all other claims, including claims under state consumer protection laws, unfair competition laws, and in tort.
b. Outside the United States. If you acquired the software in any other country, the laws of that country apply.
10.
LEGAL EFFECT. This agreement describes certain legal rights.
You may have other rights under the laws of your country.
You may also have rights with respect to the party from whom you acquired the software.
This agreement does not change your rights under the laws of your country if the laws of your country do not permit it to do so.
11.
DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED "AS-IS."
YOU BEAR THE RISK OF USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES OR CONDITIONS.
YOU MAY HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT CANNOT CHANGE.
TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT EXCLUDES THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
12.
LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00.
YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.
This limitation applies to
* anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and
* claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law.
It also applies even if Microsoft knew or should have known about the possibility of the damages.
The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages.
Please note: As this software is distributed in Quebec, Canada, some of the clauses in this agreement are provided below in French.

Free SQL server 2005 Database administration book

Hi,
From where we can download SQL server 2005 Database administration book
Thanks & Regards,
Raj

Hi,
This not the download forum for book, please don't post such query in this forum.
if you have any basis related query then post it here.
regards,
kaushal

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

Restoring a SQL Server 2005 DB to a SQL Server 2014 install, is there any way to prevent it from being upgraded

Does anyone know if there is a flag I can use to prevent a SQL Server 2005 database from being upgraded to SQL 2014 when it is restored to a 2014 instance?
Don't ask why, I just need to know if this is possible or if 2005/8 DB's are required to be upgraded if they are going to run on SQL 2012/2014 instances. The documentation seems to say this is so, I just want to verify that.

First: You cannot directly restore a 2005 database to
2014. MS supports migration over 3 SQL Server version steps; means you can restore 2005 to 2008/2008R2/2012, but not to 2014. You have to do a migration step between.
Olaf I was looking for this today, because I'm working with a new customer that have SQL 2005 and I have SQL 2014. And needed to restore a backup form the production server in my test server.
When I read what you write I think, oh no!! I have to install SQL 2012 in my server. But that it's not an option for me, and I say let me try to restore the DB first in 2014 and if not work install 2012.
You can restore a 2005 database to 2014 directly, and it works.
For reference the version number in the servers 2005 (9.0.4035 SP3) and 2014 (12.0.2000 RTM)
This is not related in any way to the original question that you answered (the file format will be upgraded to the new motor, that is sure).
I put this lines because in the future there will be some people searching about if possible to restore a 2005 DB to 2014, and like me will read your lines and think it's not possible and that can make a decision to buy 2012 and not 2014 to that new server they
will migrate.
Don't forget to mark the best replies as answers!

SSO in Microsoft Application, SQL Server 2005 & OBIEE 11g

Dear Gurus,
Any experienced how to enable SSO(Single Sign On) in OBIEE 11g, when the application platform is microsoft instead of Oracle EBS and the data source from SQL server 2005?
I am new on this.
Any help will be appreciated
Regards
JOE

Hi,
Try below link
http://sranka.wordpress.com/2008/06/06/enabling-sso-authentication-for-obiee/
http://gellio.wordpress.com/2009/10/23/enabling-oracle-single-sign-on-osso-with-obiee/
OBIEE, OAS, OID, SSO Integration
http://sranka.wordpress.com/2008/06/06/enabling-sso-authentication-for-obiee/
http://www.addidici.com/blog/?p=8
http://download.oracle.com/docs/cd/E12096_01/books/AnyDeploy/AnyDeploySSO3.html
Check the security guide here,
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10543/sso.htm#CEGJJFED
Hope thsi help's
Thanks
Satya

SQL Server 2008 R2 Std with SQL Server 2005 Express Subscriptions

If we have SQL Server 2005 Express Merge Replication Subscriptions that synch to a SQL Server 2008 R2 Standard Edition. Do
the Subscriptions still have same file size limitations even though they synch to a Proper Standard Version of SQL Server 2008?
If so what are these limitations?
What happens in the instance where by the server file becomes huge then the Subscriptions will not allow the data to replicate
as the Express Subscription engine has a file size limitation - or does this not matter??

You will get messages on your SQL Server Express servers that the merge agent cannot write to the SQL Express database. These messages are difficult to debug as you don't get a warning you have exceeded the size limit on the subscriber.
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

Crystal Report 8.5 with SQL SERVER 2005 problems

Post Author: AREVA
CA Forum: Data Connectivity and SQL
Hi All !We have some problems with Crystal Reports version 8.5 with SQL Server 2005: 1) When we want to generate a report (using data in SQL Server 2005) we have a popup message error : "impossible to loaded pdssql.dll".2) If we want to use SQL Server 2005, which Crystal Reports version we must used ? Is there any restrictions with this connectivity with 8.5 version ?Please, let me known, all informations about SQL Server 2005 and Crystal Report 8.5.Thanks for all !Best regards Anthony

Hello Kamlesh,
There is no expectation that the ActiveX viewer (RDC?) from CR8.5 will work in any version of Visual Studio .NET. There is also no expectation that the ActiveX viewer from CR8.5 will work on a machine with a 64 bit operating system.
You're using VS2008. You should migrate to the bundled edition of CR for VS2008 (v10.5), the ReportDocument object, and the .NET Windows form viewer or Web form viewer.
Sincerely,
Dan Kelleher

SQL Server 2005 SP2 install on Vista

Hi,
I have all updates for Vista, tried to install SQL Server 2005 SP2, the following log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version      : Professional (Build 6000)
Time            : Wed Mar 26 12:20:54 2008
USER-PC : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SqlWriter_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQL.log
Machine         : USER-PC
Product         : Workstation Components, Books Online and Development Tools
Warning         : Warning 28123.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Tools Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_Tools.log
Setup succeeded with the installation, inspect the log file completely for status on all the components.
Time            : Wed Mar 26 12:23:51 2008
==============================================================
When I try to start SQL Server it times out. SQL Server Express is running ok.
Can you help me get this started?
Thank you,
Lucy

This is the previous errorlog:
2008-04-09 11:47:06.27 Server      Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 6.0 (Build 6000: )
2008-04-09 11:47:06.27 Server      (c) 2005 Microsoft Corporation.
2008-04-09 11:47:06.27 Server      All rights reserved.
2008-04-09 11:47:06.27 Server      Server process ID is 240.
2008-04-09 11:47:06.27 Server      Authentication mode is WINDOWS-ONLY.
2008-04-09 11:47:06.27 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-04-09 11:47:06.27 Server      This instance of SQL Server last reported using a process ID of 4180 at 4/5/2008 11:17:36 AM (local) 4/5/2008 6:17:36 PM (UTC). This is an informational message only; no user action is required.
2008-04-09 11:47:06.27 Server      Registry startup parameters:
2008-04-09 11:47:06.27 Server      -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-04-09 11:47:06.27 Server      -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-04-09 11:47:06.27 Server      -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-04-09 11:47:06.32 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-04-09 11:47:06.32 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2008-04-09 11:47:06.50 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2008-04-09 11:47:06.55 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-04-09 11:47:06.64 Server      The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2008-04-09 11:47:06.64 Server      Database mirroring has been enabled on this instance of SQL Server.
2008-04-09 11:47:06.64 spid4s      Starting up database 'master'.
2008-04-09 11:47:06.80 spid4s      4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:07.06 spid4s      SQL Trace ID 1 was started by login "sa".
2008-04-09 11:47:07.10 spid4s      Starting up database 'mssqlsystemresource'.
2008-04-09 11:47:07.13 spid4s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid4s      Server name is 'USER-PC'. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid9s      Starting up database 'model'.
2008-04-09 11:47:07.53 spid9s      Clearing tempdb database.
2008-04-09 11:47:08.11 Server      A self-generated certificate was successfully loaded for encryption.
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv6> 1433].
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv4> 1433].
2008-04-09 11:47:08.17 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2008-04-09 11:47:08.17 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2008-04-09 11:47:08.17 Server      Server is listening on [ ::1 <ipv6> 1434].
2008-04-09 11:47:09.12 spid9s      Starting up database 'tempdb'.
2008-04-09 11:47:09.47 spid12s     The Service Broker protocol transport is disabled or not configured.
2008-04-09 11:47:09.47 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2008-04-09 11:47:09.53 spid12s     Service Broker manager has started.
2008-04-09 11:51:06.92 Server      CPU time stamp frequency has changed from 1662000 to 199683 ticks per millisecond. The new frequency will be used.
2008-04-09 11:55:07.29 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 11:55:07.29 Server      CPU time stamp frequency has changed from 199683 to 136029 ticks per millisecond. The new frequency will be used.
2008-04-09 12:23:09.84 Server      CPU time stamp frequency has changed from 136029 to 586928 ticks per millisecond. The new frequency will be used.
2008-04-09 12:59:13.12 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 13:07:13.85 Server      CPU time stamp frequency has changed from 586928 to 824822 ticks per millisecond. The new frequency will be used.
2008-04-09 13:47:17.50 Server      CPU time stamp frequency has changed from 824822 to 140502 ticks per millisecond. The new frequency will be used.
2008-04-09 14:07:19.33 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:07:24.80 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:11:25.16 Server      CPU time stamp frequency has changed from 140502 to 1413355 ticks per millisecond. The new frequency will be used.
2008-04-09 15:15:25.53 Server      CPU time stamp frequency has changed from 1413355 to 161989 ticks per millisecond. The new frequency will be used.
2008-04-09 15:19:25.89 Server      CPU time stamp frequency has changed from 161989 to 134822 ticks per millisecond. The new frequency will be used.
2008-04-09 16:23:31.73 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 17:23:37.20 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:11:41.58 Server      CPU time stamp frequency has changed from 134822 to 154257 ticks per millisecond. The new frequency will be used.
2008-04-09 18:23:42.67 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:23:42.67 Server      CPU time stamp frequency has changed from 154257 to 134721 ticks per millisecond. The new frequency will be used.
2008-04-09 18:35:43.79 Server      CPU time stamp frequency has changed from 134721 to 151448 ticks per millisecond. The new frequency will be used.
2008-04-09 18:43:44.51 Server      CPU time stamp frequency has changed from 151448 to 125134 ticks per millisecond. The new frequency will be used.
2008-04-09 19:15:47.35 Server      CPU time stamp frequency has changed from 125134 to 182297 ticks per millisecond. The new frequency will be used.
2008-04-09 19:23:48.08 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 19:27:48.45 Server      CPU time stamp frequency has changed from 182297 to 120770 ticks per millisecond. The new frequency will be used.
2008-04-09 19:47:50.27 Server      CPU time stamp frequency has changed from 120770 to 1370171 ticks per millisecond. The new frequency will be used.
2008-04-09 20:07:52.10 Server      CPU time stamp frequency has changed from 1370171 to 106932 ticks per millisecond. The new frequency will be used.
2008-04-09 20:23:53.56 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 20:35:54.65 Server      CPU time stamp frequency has changed from 106932 to 88924 ticks per millisecond. The new frequency will be used.
2008-04-09 20:51:56.11 Server      CPU time stamp frequency has changed from 88924 to 102106 ticks per millisecond. The new frequency will be used.
2008-04-09 20:59:56.84 Server      CPU time stamp frequency has changed from 102106 to 118592 ticks per millisecond. The new frequency will be used.

Issue with migration DB from SQL Server 2005 to Oracle 11.2 using SQL Developer Migration workbench

Hi,
We face an issue while migrating an SQL Server 2005 DB to Oracle 11.2. It fails during the process. I hope someone on the forum has seen this before and can give us some advice.
I use the latest version of SQL Developer with JRE included (3.2.20.09). The JDBC driver to connect to SQL Server 2005 is 1.2.0
Here are the steps we take in the Migration Workbench wizard:
I made an online extract of the SQL Server database.
Using the workbench in SQL Developer I created a migration repository in schema PDM_MIGRATION.
Next I start the migration, it captures the tables fine, but immediately after the start of the conversion I get a failed message without further explanations.
This is the content of the error xml:
<?xml version="1.0" encoding="windows-1252" standalone="no"?>
<log>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>SEVERE</level>
<class>oracle.dbtools.migration.workbench.core.logging.MigrationLogUtil</class>
<message>Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@4c12ab</param>
<exception>
    <message>oracle.dbtools.migration.convert.ConvertException: Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>1078</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>316</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>1002</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>303</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>205</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>159</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTask</class>
      <line>193</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask</class>
      <line>515</line>
    </frame>
    <frame>
      <class>java.util.concurrent.Executors$RunnableAdapter</class>
      <line>441</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>886</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>908</line>
    </frame>
    <frame>
      <class>java.lang.Thread</class>
      <line>662</line>
    </frame>
</exception>
</record>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>SEVERE</level>
<class>oracle.dbtools.migration.workbench.core.logging.MigrationLogUtil</class>
<message>Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
<param>oracle.dbtools.migration.convert.ConverterWorker.copyModel(ConverterWorker.java:1078)</param>
<param>oracle.dbtools.migration.convert.ConverterWorker.runConvert(ConverterWorker.java:316)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doConvert(FullMigrateTask.java:1002)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doMaskBasedActions(FullMigrateTask.java:303)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doWork(FullMigrateTask.java:205)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doWork(FullMigrateTask.java:159)</param>
<param>oracle.dbtools.raptor.backgroundTask.RaptorTask.call(RaptorTask.java:193)</param>
<param>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)</param>
<param>java.util.concurrent.FutureTask.run(FutureTask.java:138)</param>
<param>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:515)</param>
<param>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)</param>
<param>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)</param>
<param>java.util.concurrent.FutureTask.run(FutureTask.java:138)</param>
<param>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)</param>
<param>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)</param>
<param>java.lang.Thread.run(Thread.java:662)</param>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@5dc1bc</param>
<exception>
    <message>oracle.dbtools.migration.convert.ConvertException: Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>1078</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>316</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>1002</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>303</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>205</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>159</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTask</class>
      <line>193</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask</class>
      <line>515</line>
    </frame>
    <frame>
      <class>java.util.concurrent.Executors$RunnableAdapter</class>
      <line>441</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>886</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>908</line>
    </frame>
    <frame>
      <class>java.lang.Thread</class>
      <line>662</line>
    </frame>
</exception>
</record>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>WARNING</level>
<class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
<message>Building converted model: FAILED : Database Migration : FAILED</message>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@15a3779</param>
</record>
Does anybody know what this error means and what steps we should take to continue the migration?
I see the PDM_MIGRATION.MIGR_FILTER is a type.
Many thanks in advance,
Kris

Hi Wolfgang,
Thanks for your reply.
This is how the type MIGR_FILTER looks like:
create or replace
TYPE MIGR_FILTER IS OBJECT (
FILTER_TYPE INTEGER, -- Filter Types are 0-> ALL, 1->NAMELIST, 2->WHERE CLAUSE, 3->OBJECTID LIST
OBJTYPE VARCHAR2(40),
OBJECTIDS OBJECTIDLIST,
NAMES NAMELIST,
WHERECLAUSE VARCHAR2(1000));
I think the repository user has the correct privileges. This is the overview of privileges it has:
SQL> select * from dba_sys_privs where GRANTEE in ('PDM_MIGRATION') order by GRANTEE;
GRANTEE PRIVILEGE ADM
PDM_MIGRATION ALTER SESSION NO
PDM_MIGRATION CREATE CLUSTER NO
PDM_MIGRATION CREATE DATABASE LINK NO
PDM_MIGRATION CREATE PROCEDURE NO
PDM_MIGRATION CREATE SEQUENCE NO
PDM_MIGRATION CREATE SESSION NO
PDM_MIGRATION CREATE SYNONYM NO
PDM_MIGRATION CREATE TABLE NO
PDM_MIGRATION CREATE TRIGGER NO
PDM_MIGRATION CREATE VIEW NO
PDM_MIGRATION UNLIMITED TABLESPACE NO
SQL> select * from dba_role_privs where GRANTEE in ('PDM_MIGRATION') order by GRANTEE;
GRANTEE GRANTED_ROLE ADM DEF
PDM_MIGRATION CONNECT NO YES
PDM_MIGRATION RESOURCE NO YES
Best regards,
Kris

How to find the list of unused stored procedures in SQL Server 2005?

Hi,
I need to find out the list of stored procedures which are not in use.
I found there is something called "sys.dm_exec_procedure_stats " for SQL server 2008.
Can you please suggest your ides here to do the same job for SQL server 2005.
Many Thanks.

In SQL 2005 there is, sort of. This is query lists the last execution
time for all SQL modules in a database:
SELECT object_name(m.object_id), MAX(qs.last_execution_time)
FROM sys.sql_modules m
LEFT JOIN (sys.dm_exec_query_stats qs
CROSS APPLY sys.dm_exec_sql_text (qs.sql_handle) st)
ON m.object_id = st.objectid
AND st.dbid = db_id()
GROUP BY object_name(m.object_id)
But there are tons of caveats. The starting point of this query is
the dynamic management view dm_exec_query_stats, and the contents is
per *query plan*. If a stored procedure contains several queries,
there are more than one entry for the procedure in dm_exec_query_stats.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

How to attached a sql server 2008 database on sql server 2005

Hi,
I have a backup of database designed over sql server 2008. I need to attacched this on a machine where sql server 2005 is installed and I am getting the message while attaching the database.
"The database can not be opened because it is version 661.
the server supports version 611 and earlier"

You need to install/have another instance of SQL Server 2008, restore over there the database and perhaps create a SSIS package to move objects and data into SQL Server 2005
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Best SQL Server 2005 books

Similar Messages

Maybe you are looking for