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

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

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

Similar Messages

Sql server 2012 Logon trigger not working for certain logins

Hello. I created a login trigger to insert data for each login in a table, and it works for all logins except one that is format domain\login
and the login ends with the dollar sign(actual name is domain\CTXDEVDCSI1$).
I had been using varchar, but after reading other forum posts, I changed the varchar's to nvarchar's, but it still fails for that id.
The errors written to the sql server error log were the usual "login failed due to trigger execution".
I had granted insert on the rvvlogindata table in dsa to public, and only one id wasn't able to login after that.
Any suggestions would be much appreciated!
Here's the modified table ddl:
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[rvvlogindata](
[sessionId] [int] NULL,
[LoginTime] [datetime] NULL,
[HostName] [nvarchar](50) NULL,
[ProgramName] [nvarchar](300) NULL,
[LoginName] [nvarchar](50) NULL,
[ClientHost] [nvarchar](50) NULL
) ON [PRIMARY]
GO
Here's the logon trigger code:
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
create trigger [LOGIN_IP_RESTRICTION] on all server for logon
as
Begin
Declare @LogonTriggerData xml,
@EventTime datetime,
@LoginName nvarchar(50),
@ClientHost nvarchar(50),
@HostName nvarchar(50),
@AppName nvarchar(300)
Set @LogonTriggerData = eventdata()
set @EventTime = @LogonTriggerData.value('(/EVENT_INSTANCE/PostTime)[1]', 'datetime')
set @LoginName = @LogonTriggerData.value('(/EVENT_INSTANCE/LoginName)[1]', 'varchar(50)')
set @ClientHost = @LogonTriggerData.value('(/EVENT_INSTANCE/ClientHost)[1]', 'varchar(50)')
set @HostName = HOST_NAME()
set @AppName = APP_NAME()
insert into dsa.dbo.rvvlogindata
sessionId,
LoginTime,
HostName,
ProgramName,
LoginName,
ClientHost
select @@spid,
@EventTime,
convert(nvarchar(50),@HostName),
convert(nvarchar(300),@AppName),
convert(nvarchar(50),@LoginName),
convert(nvarchar(50),@ClientHost)
END
GO
SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER OFF
GO
ENABLE TRIGGER [LOGIN_IP_RESTRICTION] ON ALL SERVER
GO

Erland, I wanted to add more info to my reply earlier today.
sp_who2 showed no blocking, activity monitor from my local PC SSMS showed no major waits or high i/o or cpu activity.
I was wondering if you have any suggestions on how to find out what was the cause of the 5+ minute wait for SSMS on the remote desktop to respond and fully come up.
I definitely can't put this in production with this hanging delay possibly occurring there.
I was connecting as read_user when it hung.
sp_who2 output at the time was:
1    BACKGROUND                    sa   .   . NULL LOG WRITER      54631 0 04/10
06:59:43
1    0
2    BACKGROUND                    sa   .   . NULL RECOVERY WRITER 8673 0 04/10 06:59:43
2    0
3    BACKGROUND                    sa   .   . NULL LAZY WRITER     300691 0 04/10
06:59:43
3    0
4    BACKGROUND                    sa   .   . NULL RESOURCE MONITOR 1207010 0 04/10 06:59:43
4    0
5    BACKGROUND                    sa   .   . NULL XE TIMER        38828 0 04/10
06:59:43
5    0
6    BACKGROUND                    sa   .   . NULL XE DISPATCHER   1404 0 04/10
06:59:43
6    0
7    BACKGROUND                    sa   .   . master SIGNAL HANDLER 0 0 04/10 06:59:43
7    0
8    BACKGROUND                    sa   .   . NULL LOCK MONITOR    179978 0 04/10
06:59:43
8    0
9    sleeping                      sa   .   . master TASK MANAGER    0 11 04/21
08:37:04
9    0
10   sleeping                      sa   .   . master TASK MANAGER    0 0 04/10
06:59:44
10   0
11   BACKGROUND                    sa   .   . master TRACE QUEUE TASK 546 0 04/10 06:59:44
11   0
12   BACKGROUND                    sa   .   . NULL SYSTEM_HEALTH_MO 4930 0 04/10 06:59:44
12   0
13   BACKGROUND                    sa   .   . NULL RECEIVE         422 0 04/10
06:59:45
13   0
14   BACKGROUND                    sa   .   . master CHECKPOINT      79137 31811 04/10
06:59:46
14   0
15   BACKGROUND                    sa   .   . master TASK MANAGER    1606 0 04/10
06:59:46
15   0
16   BACKGROUND                    sa   .   . NULL UNKNOWN TOKEN   0 0 04/10 06:59:46
16   0
17   sleeping                      sa   .   . master TASK MANAGER    0 74 04/21
08:37:04
17   0
18   sleeping                      sa   .   . master TASK MANAGER    0 0 04/21
08:18:49
18   0
19   sleeping                      sa   .   . master TASK MANAGER    0 0 04/21
08:30:29
19   0
20   sleeping                      sa   .   . master TASK MANAGER    0 1 04/21
08:37:14
20   0
21   sleeping                      sa   .   . master TASK MANAGER    0 7 04/21
08:30:59
21   0
22   sleeping                      sa   .   . master TASK MANAGER    16 4 04/21
08:37:44
22   0
23   sleeping                      sa   .   . master TASK MANAGER    0 15 04/21
08:39:24
23   0
25   BACKGROUND                    sa   .   . master BRKR EVENT HNDLR 0 95 04/10 06:59:48
25   0
30   BACKGROUND                    sa   .   . master BRKR TASK       0 0 04/10
06:59:48
30   0
31   BACKGROUND                    sa   .   . master BRKR TASK       16926 0 04/10
06:59:48
31   0
32   BACKGROUND                    sa   .   . master BRKR TASK       0 0 04/10
06:59:48
32   0
34   BACKGROUND                    sa   .   . master BRKR TASK       10701 0 04/10
06:59:48
34   0
51   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
03:16:56
51   0
52   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
52   0
53   sleeping                      NT AUTHORITY\SYSTEM SQLDEV2012      . msdb AWAITING COMMAND 0 0 04/10
06:59:58 SQLAgent - Email Logger                       53   0
54   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:51 Citrix:Broker#1                               54   0
55   sleeping                      edit_user ASDEV1          . dsa AWAITING
COMMAND 0 0 04/21 08:55:27 jTDS
55   0
56   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
56   0
57   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
57   0
58   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
58   0
59   sleeping                      NT AUTHORITY\SYSTEM SQLDEV2012      . msdb AWAITING COMMAND 124 242 04/10
06:59:59 SQLAgent - Generic Refresher                  59   0
60   sleeping                      NT AUTHORITY\SYSTEM SQLDEV2012      . msdb AWAITING COMMAND 2790 1160 04/21
08:55:00 SQLAgent - Job invocation engine              60   0
61   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
61   0
62   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
62   0
63   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
63   0
64   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
64   0
65   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
65   0
66   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
03:16:56
66   0
67   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
67   0
68   sleeping                      edit_user DCMA10685       . dsa AWAITING COMMAND 0 0 04/21
08:56:47 jTDS
68   0
69   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:49 Citrix:Configuration                          69   0
70   sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 1794 7120 04/21
08:51:37 Microsoft SQL Server Management Studio        70   0
71   sleeping                      xsp_user XSPDEVSI2       . xspv5 AWAITING COMMAND 0 0 04/21
08:58:52 .Net SqlClient Data Provider                  71   0
72   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:56:01 Citrix:Monitor                                72   0
73   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:30 Citrix:Monitor                                73   0
74   sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 16 2 04/21
08:53:37 Microsoft SQL Server Management Studio - Query 74   0
75   sleeping                      rvanveen DCMA8460        . loginaudit AWAITING COMMAND 0 22 04/21
08:50:29 Microsoft SQL Server Management Studio - Query 75   0
76   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:07
76   0
77   sleeping                      adm_jbossportal ASDEV1          . jbossportal AWAITING
COMMAND 0 0 04/21 08:40:27 jTDS
77   0
78   sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 110 542 04/21
08:46:17 Microsoft SQL Server Management Studio - Query 78   0
79   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:56
79   0
80   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:54 Citrix:MachineCreation                        80   0
81   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
08:08:29
81   0
82   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:02:13
82   0
83   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:02:15
83   0
84   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:44 Citrix:Monitor                                84   0
85   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:11:05
85   0
86   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:53 Citrix:AdIdentity                             86   0
87   sleeping                      DAIWA_USA\admsql SQLDEV2012      . master AWAITING COMMAND 15 2 04/21
08:56:20 Microsoft SQL Server Management Studio - Query 87   0
88   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:36 Citrix:SiteServices                           88   0
89   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:42 Citrix:Host                                   89   0
90   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:47 Citrix:ConfigurationLogging                   90   0
91   RUNNABLE                      rvanveen DCMA8460        . master SELECT INTO
15 51 04/21 08:58:46 Microsoft SQL Server Management Studio - Query 91   0
92   sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 63 30 04/21
08:52:34 Microsoft SQL Server Management Studio - Query 92   0
94   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:53 Citrix:DelegatedAdmin                         94   0
95   sleeping                      DAIWA_USA\admsql SQLDEV2012      . loginaudit AWAITING COMMAND 173 27 04/21
08:56:10 Microsoft SQL Server Management Studio        95   0
96   sleeping                      xsp_user XSPDEVSI2       . xspv5 AWAITING COMMAND 0 0 04/21
08:58:33 .Net SqlClient Data Provider                  96   0
97   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
08:10:07
97   0
98   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 31 38 04/21
08:00:31
98   0
99   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
08:10:12
99   0
100 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 282 04/21
08:10:14
100 0
101 sleeping                      DAIWA_USA\admsql SQLDEV2012      . master AWAITING COMMAND 0 8 04/21
08:56:50 Microsoft SQL Server Management Studio        101 0
102 sleeping                      DAIWA_USA\admsql SQLDEV2012      . master AWAITING COMMAND 31 0 04/21
08:54:57 Microsoft SQL Server Management Studio        102 0
103 sleeping                      read_user SQLDEV2012      . master AWAITING COMMAND 0 8 04/21
08:57:09 Microsoft SQL Server Management Studio        103 0
104 sleeping                      read_user SQLDEV2012      . dsa AWAITING COMMAND 0 0 04/21
08:57:09 Microsoft SQL Server Management Studio        104 0
105 sleeping                      rvanveen DCMA8460        . tempdb AWAITING COMMAND 8875 336 04/21
08:58:54 Microsoft SQL Server Management Studio        105 0
106 sleeping                      read_user SQLDEV2012      . master AWAITING COMMAND 16 0 04/21
08:57:39 Microsoft SQL Server Management Studio        106 0
107 sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:47 Citrix:EnvTest                                107 0
108 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 2200 8514 04/21
08:00:31
108 0
109 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:56
109 0
110 sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 0 0 04/21
08:58:48 Microsoft SQL Server Management Studio        110 0
113 sleeping                      Citrix_adm CTXDEVSI1       . XenApp6 AWAITING COMMAND 284 777 04/21
08:51:33 Citrix IMA                                    113 0
119 sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:42 Citrix:ConfigurationLoggingData               119 0
120 sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:26 Citrix:Storefront                             120 0
125 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/16
13:55:16
125 0
126 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 16 0 04/16
11:25:30
126 0
131 sleeping                      echouliak DCMA10685       . master AWAITING COMMAND 139 8 04/14
15:26:55 Microsoft SQL Server Management Studio        131 0
135 sleeping                      echouliak DCMA10685       . dsa AWAITING COMMAND 0 0 04/14
15:24:52 Microsoft SQL Server Management Studio - Query 135 0
136 sleeping                      echouliak DCMA10685       . dsa AWAITING COMMAND 0 0 04/14
15:00:17 Microsoft SQL Server Management Studio - Query 136 0
140 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:56
140 0
145 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:56
145 0

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

SQL Server 2005 Error Message - when Right Clicking a DB Properties

Hi
We are running SQL Server 2005 SP03, we have x15 databases (excluding SBO-COMMON, RSP, Coresuite), all x15 databases have Maintenance Plans setup, tasks ticked:
- Shrink Database
- Clean Up History
- Back up Database (Full)
- Maintenance Clean-up task
These Maintenance Plans have been running for over 5 months now, we have recently changed our VMware Virtual Server over to a Hosted VMware Virtual Server, now when I right click on a certain database and select "Properties" I get the following error message with SQL Server:
Property Owner is not available for Database '[Turquoise_Moon_Live]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)
Could the Maintenance Plan be preventing me to run the Properties against a relevant DB (I have tested this by restoring a DB that doe not have a Maintenance Plan and the Properties works, tested this on SBO-COMMON and it works as well)
Can anyone agree with me or let me know what else might be the issue as I have checked the Server Roles & the Users Credentials for SQL and all seems well.
Regards
Kurt Walters

Hi Gordon
This solution did not work, but I needed to delete the Maintenance Plans anyway to set it for 1 month instead of 2 Months. I am thinking as we have changed Domains, were the last one was IS Domain and the new one is Hosted Domain, the security issues are probably coming from this (as I am able to access the Properties of the IS Domain SQL Server even with the Maintenance Plans running).
Any thoughts on correcting this as we have changed Domains? (I have created a user as HOSTED\example, the old one was IS\example)
Regards
Kurt Walters

How to calculate the HFM Cube size in SQL Server-2005

Hi
How to calculate the HFM Cube size in SQL Server-2005 ?
Below query used for Oracle. Then what is query for SQL Server?
SQL> select sum(bytes/1024/1024) from dba_segments where segment_name like 'FINANCIAL_%' and owner='HFM';
SUM(BYTES/1024/1024)
SQL> select sum(bytes/1024/1024) from dba_segments where segment_name like 'HSV FINANCIAL%' and owner='HFM';
SUM(BYTES/1024/1024)
Regards
Smilee

What is your objective? The subcube in HFM is a concept which applies to the application tier - not so much to the database tier. The size of the subcube is the unique number of data strips (data values for January - December inclusive, for example) for the given entity, currency triplet or Parent.Child node. You have to account for parent accounts and customs which don't exist in the database but are generated in RAM in the application tier.
So, if your objective is to find the largest subcubes, you could do this by querying the database and counting the number of records per entity/value (DCE tables) or parent.child entity combination (DCN tables). I'm not versed in SQL, but I think the script below would just tell you the schema size and not the subcube sizes.
Check out Accelatis.com for a third party software product that can do this for you. The feature is called the Subcube Analyzer and was written by the same team that wrote HFM, so they ought to know how this works :-)
--chris

How do you compare Oracle 10G with SQL Server 2005?

exept for performance and pricing...
We haven't decide to upgrade SQL Server 2000 to SQL Server 2005 or buy more license for Oracle 10G...
Any comments are welcome!

OK I only came here because of APC's referral down the piece (I was curious where all the hits came from - cheers Andrew). Comments embedded anyway
Thanks Gaff!
* Staff Experience with product - how flexible is
your staff?
--Staff need to learn sth. new...:)That's a fair motivation if recruitment and retention of staff is an issue - if you want reliability giving business systems to people who don't know the tech is a rather foolish move.
* Current product use Corporation/group - if you have
15 SQL Server boxes and no Oracle, what is the
impetus for change? Same if you have 15 Oracle boxes
and no SQL Server ones.
--80% SQL server and 20% Oracle. We are thinking to
balance to 50%-50%.I'm curious as to the reasoning behind this? I don't really see what the benefit is.
* Features - Do you want/need text handling
capabilities? Data mining? Storage of non-text
records? XML?
--I think both of DB system can do these.They can
* Scalability - Is one Windows box going to meet your
needs or do you need to scale (now or eventually) to
multiple boxes of multiple CPUs?
--This is really a benefit feature of Oracle better
than SQL Server.SQLServer scales - it just scales in a different way (federated databases vs RAC).
Thank u for ur US$.02Are you evaluating the platform for an in-house development or a database neutral application - if the latter I'd be sorely tempted to find out what the development platform is or read the docs for clues. For example we are looking at a product that supports SQLServer,MSDE and Oracle. In the FAQ "how do I choose between SQLServer and MSDE?", if we do implement it will be on an MS platform.
I consider this probably the most crucial factor since SQLServer and Oracle have different architectural features they tend to generate different development approaches - porting one to the other nearly always hurts the new platform. Plus if I need support I'd be hoping that I got a bug fix from a developer and not from a developer whose fix was then ported.
The same applies to in-house dev obviously, but there at least you can hire people with the right skillset for the app development.
Cheers
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com

SQL Server 2005 Database connecting problem

Hi,
I have installed MDM 5.5 SP06 - 64bit servers, 32bit clients and SQL server 2005 in Vista 64 bit operating system.
But I can't able to connect the server...
I believe sa is reserved user name but in SQL server management studio I couldn't able to connect the server and registered the Server.
Can you guys please guide me in this regard how to fix this problem ASAP?
Thanks,
Pooja

Hi,
Thanks for your time and help, but I couldn't able to see the database itself.
as I know my computer name is database name but SQL Server is not providing that.
and its showing network data base names.
If I type the database name and user is sa...but there is no luck in connecting...
is there any way that we can define server name and user names??? also it doesn't ask for any database name or user name during installation of SQL Server 2005
I'm not a SQL person so, please help me in this regard.
Thanks, Pooja

SQL SERVER 2005 - part of the tables where migrated

Hello.
I'm trying to convert a SQL SERVER2005 DB to ORACLE 10g.
The sql-developer is converting all the objects from the DB, but builds DDL comands for 43 table insted of 320 tables .
All the tables are on schema dbo.
The user connecting to the sql server 2005 is data base owner (dbo).
After building the repository, on MD_TABLES there are only 43 records.
Any idea where to search the problem?
Thanks
Reuven
Message was edited by: reuven
user533419
Message was edited by: reuven
user533419
Message was edited by: reuven
user533419

Reuven,
We are finalizing our production release and would like to get to the bottom of the problem.
-You can run the workbench/SQLDeveloper so that you can see Java 'Stack traces' from exceptions (errors) in the output:
[from the SQLDeveloper forum under Unable to start sql developer :]
There is another [sqldeveloper.exe] that you should try from the command line:
<sqldevroot>\sqldeveloper\sqldeveloper\bin\sqldeveloper.exe
This will run in debug mode.
If all else fails, try the .bat file in that same folder.
-Are you using a case sensitive database?
-For the pre-production release workbench currently uses SQL Server 2000 views rather than SQL Server 2005 altered to take allowance for the user/schema separation, this may cause unforeseen problems.
-Can you send a test database to us with this problem?
Regards,
Turloch
Oracle Migration Workbench Team

Configuration note of SQL SERVER 2005

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

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

DB mail not working in sql server 2005

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

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

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

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

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

XP_DELETE_FILE NOT WORKING IN SQL SERVER 2005 SP2

Hi All,
I have one job in sql 2005 sp2 that deletes backup older than one week.It is not working.I have checked service account permissions on backup folder and all required permissions and authentications are in place.Please let me know how to troubleshoot the
same.
Regards
Rahul

Check the following:
http://stackoverflow.com/questions/212603/sql-server-xp-delete-file-not-deleting-files
QUOTE: "Note that xp_delete_file is broken in SP2 and won't work on report files;"
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

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

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

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

App not versioned error in JDeveloper - ADF with SQL Server 2005

Hello All,
I am developing a sample ADF application. Database is MS SQL Server 2005 SP2. I get below error message. I am trying in parallel to google it... However trying here if any encountered such an issue and had resolved it.
Thanks in advance for your time.
Cheers,
Vagic.
[02:06:19 PM] Deploying Application...
<Feb 23, 2010 2:06:20 PM PST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application ExmReports is not versioned.>
<Feb 23, 2010 2:06:20 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266962779600' for task '0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)

You might need to add the JDBC jar file for SQL Server to the classpath of the integrated WebLogic. See minute 8 here: http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/NBtoJDevProject/NBtoJDevProject.html

Addon in Client is not connecting to SQL Server 2005

Hi, we have an add-on, which is working in SBO 2005 with SQL Server 2000.
When the addon tries to connect to the same DB, restored on a SQL Server 2005, the addon is hanging up on the oCompany.Connect method. But this only happens when we try a remote connection from a SBO client.
If we run the addon from the SBO server, where the SQL Server is running too, the addon completes the connection in the expected way.
The SBO Client is connecting to the server, and works fine, but the addon is not connecting to the server.
We try to connect to the server from the client, using SQL Query Analizer from SQL Server 2000, and it works fine too.
Does anyone knows how to fix this issue?
Thanks

Hi Alejandro, thanks for your response.
After installing SBO Patch 20 the add-on is now connecting fine, so I think it must be an upgrade on the new DI API. I noticed the version changes from 6.80.318 to 6.80.319
I had checked the SQL to confirm is was allowing remote connections.
Thank you guys.

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

Similar Messages

Maybe you are looking for