Frustrating Installation Error

I was installing SQL Server on my machine and during installation my PC
freezed. It happens frequently on my machine as my bad luck sticks frequenctly to my side. So i tried after
restarting to install it again and since then i always get the same
error message:
"An error occurred while creating one or more registry entries. Please
see C:\WINDOWS\sqlstp.log for details. The problem could be caused by a
low registry quota condition"
I have tried to clean the registry during the installation bt chosing "advanced options" -> "Rebuild registry" and i don't know what else i could
do to solve this issue. I'd like to remark that i also deleted the SQL Server keys from Registry as suggested from Microsoft to delete default and special named instances.

I also deleted every thing under %TEMP%; I even installed third pary registry tools to clean the registry such as RegistryFix, Registry Mechanic and AMUST.

Finally, i'm using Windows XP Professional SP2.

Any help?

The log file lists the following:

14:22:27 Begin Setup
14:22:27 8.00.194
14:22:27 Mode = Normal
14:22:27 ModeType = NORMAL
14:22:27 GetDefinitionEx returned: 0, Extended: 0x0
14:22:27 ValueFTS returned: 1
14:22:27 ValuePID returned: 1
14:22:27 ValueLic returned: 0
14:22:27 System: Windows NT WorkStation
14:22:27 SQL Server ProductType: Developer Edition [0x3]
14:22:27 Begin Action: SetupInitialize
14:22:27 End Action SetupInitialize
14:22:27 Begin Action: SetupInstall
14:22:27 Reading
Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ...
14:22:27 CommonFilesDir=C:\Programme\Gemeinsame Dateien
14:22:27 Windows Directory=C:\WINDOWS\
14:22:27 Program Files=C:\Programme\
14:22:27 TEMPDIR=C:\WINDOWS\TEMP\
14:22:27 Begin Action: SetupInstall
14:22:27 digpid size : 256
14:22:27 digpid size : 164
14:22:27 Begin Action: CheckFixedRequirements
14:22:27 Platform ID: 0xf000000
14:22:27 Version: 5.1.2600
14:22:27 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.2900.2805
14:22:27 End Action: CheckFixedRequirements
14:22:27 Begin Action: ShowDialogs
14:22:27 Initial Dialog Mask: 0x83000f7, Disable Back=0x1
14:22:27 Begin Action ShowDialogsHlpr: 0x1
14:22:27 Begin Action: DialogShowSdWelcome
14:22:28 End Action DialogShowSdWelcome
14:22:28 Dialog 0x1 returned: 1
14:22:28 End Action ShowDialogsHlpr
14:22:28 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
14:22:28 Begin Action ShowDialogsHlpr: 0x2
14:22:28 Begin Action: DialogShowSdMachineName
14:22:30 ShowDlgMachine returned: 1
14:22:30 Name = COOSA, Type = 0x1
14:22:30 Begin Action: CheckRequirements
14:22:30 Processor Architecture: x86 (Pentium)
14:22:30 Service Pack: 512
14:22:30 ComputerName: COOSA
14:22:30 User Name: admin
14:22:30 IsAllAccessAllowed returned: 1
14:22:30 OS Language: 0x401
14:22:30 End Action CheckRequirements
14:22:30 This combination of Package and Operating System allows a full
product install.
14:22:30 CreateSetupTopology(COOSA), Handle : 0x1b04098, returned : 0
14:22:30 CreateSetupTopology returned : 0, Handle : 0x1b04098
14:22:30 Topology Type : 1, Return Value : 0
14:22:30 ST_GetPhysicalNode returned : 0, PNHandle : 0x1b040c0
14:22:30 PN_EnumerateEx returned : 0
14:22:30 PN_GetSQLStates returned : 0, SqlStates : 0x80000000
14:22:30 PN_StartScan [0x1b040c0] returned : 0
14:22:30 PN_GetNext [0x1b040c0] returned : 18, Handle: [0x0]
14:22:30 No more items in enumeration.
14:22:30 ReleaseSetupTopology
14:22:30 Named instance limit: 100, quota: 0
14:22:30 End Action DialogShowSdMachineName
14:22:30 begin ShowDialogsUpdateMask
14:22:30 nFullMask = 0x83000f7, nCurrent = 0x2, nDirection = 0
14:22:30 Updated Dialog Mask: 0xbf00037, Disable Back = 0x1
14:22:30 Dialog 0x2 returned: 0
14:22:30 End Action ShowDialogsHlpr
14:22:30 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
14:22:30 Begin Action ShowDialogsHlpr: 0x4
14:22:30 Begin Action: DialogShowSdInstallMode
14:22:36 ShowDlgInstallMode returned: 1
14:22:36 InstallMode : 0x1
14:22:36 End Action DialogShowSdInstallMode
14:22:36 begin ShowDialogsUpdateMask
14:22:36 nFullMask = 0xbf00037, nCurrent = 0x4, nDirection = 1
14:22:36 Updated Dialog Mask: 0xbf40037, Disable Back = 0x1
14:22:36 Dialog 0x4 returned: 1
14:22:36 End Action ShowDialogsHlpr
14:22:36 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
14:22:36 Begin Action ShowDialogsHlpr: 0x10
14:22:36 Begin Action: DialogShowSdRegisterUserEx
14:22:42 End Action DialogShowSdRegisterUserEx
14:22:42 Dialog 0x10 returned: 1
14:22:42 End Action ShowDialogsHlpr
14:22:42 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
14:22:42 Begin Action ShowDialogsHlpr: 0x20
14:22:42 Begin Action: DialogShowSdLicense
14:22:43 End Action DialogShowSdLicense
14:22:43 Dialog 0x20 returned: 1
14:22:43 End Action ShowDialogsHlpr
14:22:43 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
14:22:43 Begin Action ShowDialogsHlpr: 0x40000
14:22:43 Begin Action: DialogShowSdCliSvr
14:22:43 DisplaySystemPreReq
14:22:45 ShowDlgClientServerSelect returned: 1
14:22:45 Type : 0x2
14:22:45 End Action DialogShowSdCliSvr
14:22:45 begin ShowDialogsUpdateMask
14:22:45 nFullMask = 0xbf40037, nCurrent = 0x40000, nDirection = 1
14:22:45 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
14:22:45 Dialog 0x40000 returned: 1
14:22:45 End Action ShowDialogsHlpr
14:22:45 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
14:22:45 Begin Action ShowDialogsHlpr: 0x80000
14:22:45 Begin Action: DialogShowSdInstanceName
14:22:45 Begin Action: ShowDlgInstanceName
14:22:47 End Action: ShowDlgInstanceName
14:22:47 ShowDlgInstanceName returned : 1
14:22:47 InstanceName : MSSQLSERVER
14:22:47 CreateSetupTopology(COOSA), Handle : 0x1b04098, returned : 0
14:22:47 CreateSetupTopology returned : 0, Handle : 0x1b04098
14:22:47 Topology Type : 1, Return Value : 0
14:22:47 ST_GetPhysicalNode returned : 0, PNHandle : 0x1b040c0
14:22:47 PN_EnumerateEx returned : 0
14:22:47 PN_GetSQLStates returned : 0, SqlStates : 0x80000000
14:22:47 PN_StartScan [0x1b040c0] returned : 0
14:22:47 PN_GetNext [0x1b040c0] returned : 18, Handle: [0x0]
14:22:47 No more items in enumeration.
14:22:47 ReleaseSetupTopology
14:22:47 End Action DialogShowSdInstanceName
14:22:47 begin ShowDialogsUpdateMask
14:22:47 nFullMask = 0xbfc0037, nCurrent = 0x80000, nDirection = 1
14:22:47 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
14:22:47 Dialog 0x80000 returned: 1
14:22:47 End Action ShowDialogsHlpr
14:22:47 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
14:22:47 Begin Action ShowDialogsHlpr: 0x100000
14:22:47 Begin Action: DialogShowSdSetupType
14:22:47 Begin Action: Setup Type
14:23:05 SQL program folder: C:\Programme\Microsoft SQL Server
14:23:05 SQL data folder: C:\Programme\Microsoft SQL Server
14:23:05 Windows system folder: C:\WINDOWS\system32\
14:23:05 Prog req: 38073, Data req: 34432, Sys req: 158694
14:23:05 Prog avail: 1481708, Data avail: 1481708, Sys avail: 1481708
14:23:05 Prog req vs. avail, 231199, 1481708
14:23:05 Data req vs. avail, 34432, 1481708
14:23:05 Sys req vs. avail, 193126, 1481708
14:23:05 DisplaySystemPreReq
14:23:05 [SetupTypeSQL]
14:23:05 szDir = C:\Programme\Microsoft SQL Server
14:23:05 szDir = %PROGRAMFILES%\Microsoft SQL Server
14:23:05 Result = 301
14:23:05 szDataDir = C:\Programme\Microsoft SQL Server
14:23:05 szDataDir = %PROGRAMFILES%\Microsoft SQL Server
14:23:05 End Action: Setup Type
14:23:05 Setup Type: Typical (301)
14:23:05 End Action DialogShowSdSetupType
14:23:05 begin ShowDialogsUpdateMask
14:23:05 nFullMask = 0xbfc0037, nCurrent = 0x100000, nDirection = 301
14:23:05 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:05 Dialog 0x100000 returned: 301
14:23:05 End Action ShowDialogsHlpr
14:23:05 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
14:23:05 Begin Action ShowDialogsHlpr: 0x400000
14:23:05 Begin Action: DlgServices
14:23:10 ShowDlgServices returned: 1
14:23:10 [DlgServices]
14:23:10 Local-Domain = 3855
14:23:10 AutoStart = 15
14:23:10 Result = 1
14:23:10 End Action DlgServices
14:23:10 begin ShowDialogsUpdateMask
14:23:10 nFullMask = 0xbdc0037, nCurrent = 0x400000, nDirection = 1
14:23:10 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:10 Dialog 0x400000 returned: 1
14:23:10 End Action ShowDialogsHlpr
14:23:10 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
14:23:10 Begin Action ShowDialogsHlpr: 0x800000
14:23:10 Begin Action: DlgSQLSecurity
14:23:12 ShowDlgSQLSecurity returned: 1
14:23:12 LoginMode = 1,szPwd
14:23:12 End Action DlgSQLSecurity
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x800000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x800000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
14:23:12 Begin Action ShowDialogsHlpr: 0x1000000
14:23:12 Begin Action: DlgCollation
14:23:12 ShowDlgCollation returned: 1
14:23:12 collation_name = Arabic_CI_AS,locale_name = Arabic,lcid =
0x401,SortId = 0,dwCompFlags = 0x30001
14:23:12 End Action DlgCollation
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x1000000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x1000000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
14:23:12 Begin Action ShowDialogsHlpr: 0x2000000
14:23:12 Begin Action: DlgNetwork
14:23:12 ShowDlgNetwork returned: 1
14:23:12 [DlgServerNetwork]
14:23:12 NetworkLibs = 255
14:23:12 TCPPort = 1433
14:23:12 TCPPrxy = Default
14:23:12 NMPPipeName = \\.\pipe\sql\query
14:23:12 Result = 1
14:23:12 End Action DlgNetwork
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x2000000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x2000000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
14:23:12 Begin Action ShowDialogsHlpr: 0x8000000
14:23:12 Begin Action: DialogShowSdStartCopy
14:23:13 End Action DialogShowSdStartCopy
14:23:13 begin ShowDialogsUpdateMask
14:23:13 nFullMask = 0xbdc0037, nCurrent = 0x8000000, nDirection = 1
14:23:13 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:13 Dialog 0x8000000 returned: 1
14:23:13 End Action ShowDialogsHlpr
14:23:13 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
14:23:13 End Action ShowDialogs
14:23:13 Begin Action ProcessBeforeDataMove:
14:23:13 DeinstallStart returned (C:\Programme\Microsoft SQL
Server\MSSQL): 0
14:23:13 End Action ProcessBeforeDataMove:
14:23:13 Begin Action SetToolsComponentSelection:
14:23:13 End Action SetToolsComponentSelection:
14:23:13 Begin Action ProcessComponentSelection:
14:23:13 End Action ProcessComponentSelection
14:23:13 Begin Action LogSelectedComponents:
14:23:13 SQLProg
14:23:13 SQLProg\SQLServr
14:23:13 SQLProg\SQLServr\Help
14:23:13 SQLProg\SQLServr\SCMDev
14:23:13 SQLProg\SQLServr\SCMDev\SCMh
14:23:13 SQLProg\SQLServr\SCMDev\SCMX86Lb
14:23:13 SQLProg\SQLServr\SCMDev\SCMALb
14:23:13 SQLProg\SQLServr\Rs1033
14:23:13 SQLProg\SQLServr\RsIntl
14:23:13 SQLProg\SQLServr\ActiveX
14:23:13 SQLProg\SQLServr\System
14:23:13 SQLProg\UpgTools
14:23:13 SQLProg\UpgTools\UpgSys
14:23:13 SQLProg\UpgTools\ActiveX
14:23:13 SQLProg\UpgTools\Res1033
14:23:13 SQLProg\UpgTools\ResOther
14:23:13 SQLProg\UpgTools\Resld
14:23:13 SQLProg\ReplSupp
14:23:13 SQLProg\ReplSupp\ReplDat
14:23:13 SQLProg\ReplSupp\RepComm
14:23:13 SQLProg\ReplSupp\RepNoDk
14:23:13 SQLProg\ReplSupp\ActiveX
14:23:13 SQLProg\Install
14:23:13 SQLProg\System
14:23:13 SQLProg\SvrExt
14:23:13 SQLProg\SvrExt\Help
14:23:13 SQLProg\SvrExt\SvrExtRs
14:23:13 SQLProg\SvrExt\ResIntl
14:23:13 SQLProg\Dat
14:23:13 SQLProg\DatSmpl
14:23:13 SQLProg\BaseSys
14:23:13 SQLProg\BaseBinn
14:23:13 SQLProg\BaseInst
14:23:13 SQLProg\Symbols
14:23:13 SQLProg\Symbols\EXE
14:23:13 SQLProg\Symbols\DLL
14:23:13 SQLProg\Perfmon
14:23:13 SQLProg\Perfmon\System
14:23:13 SQLProg\Root
14:23:13 MgtTool
14:23:13 MgtTool\SEM
14:23:13 MgtTool\SEM\HTML
14:23:13 MgtTool\SEM\MSD98
14:23:13 MgtTool\SEM\MSD98SYS
14:23:13 MgtTool\SEM\MSD98Res
14:23:13 MgtTool\SEM\MSD98Hlp
14:23:13 MgtTool\SEM\Help
14:23:13 MgtTool\SEM\Res1033
14:23:13 MgtTool\SEM\ResIntl
14:23:13 MgtTool\SEM\MSD98RsI
14:23:13 MgtTool\SEM\ActiveX
14:23:13 MgtTool\SEM\ActiveX\Res1033
14:23:13 MgtTool\SEM\ActiveX\ResIntl
14:23:13 MgtTool\SEM\Scripts
14:23:13 MgtTool\SEM\OLEDB
14:23:13 MgtTool\SEM\OLEDB\Res1033
14:23:13 MgtTool\SEM\OLEDB\ResIntl
14:23:13 MgtTool\Profiler
14:23:13 MgtTool\Profiler\Help
14:23:13 MgtTool\Profiler\Res1033
14:23:13 MgtTool\Profiler\ResIntl
14:23:13 MgtTool\Qryanlz
14:23:13 MgtTool\Qryanlz\Help
14:23:13 MgtTool\Qryanlz\Res1033
14:23:13 MgtTool\Qryanlz\ResIntl
14:23:13 MgtTool\DTCCLi
14:23:13 MgtTool\Wzcnflct
14:23:13 MgtTool\Wzcnflct\WzcnHlp
14:23:13 MgtTool\Wzcnflct\Wzcn1033
14:23:13 MgtTool\Wzcnflct\WzcnOthr
14:23:13 MgtTool\Wzcnflct\WzcnCmn
14:23:13 MgtTool\UtilSys
14:23:13 MgtTool\UtilBinn
14:23:13 Connect
14:23:13 Connect\ConnSys
14:23:13 Books
14:23:13 Books\Bookso
14:23:13 Books\Bookso\Utils
14:23:13 DevTools
14:23:13 DevTools\Dbg Int
14:23:13 DevTools\Dbg Int\Dbg Int Common
14:23:13 DevTools\Dbg Int\EXE
14:23:13 CoreRepl
14:23:13 CoreRepl\Res1033
14:23:13 CoreRepl\ResIntl
14:23:13 Core
14:23:13 Core\Res1033
14:23:13 Core\ResOther
14:23:13 Repostry
14:23:13 Repostry\RepstSys
14:23:13 Repostry\Res1033
14:23:13 Repostry\ResIntl
14:23:13 CoreMisc
14:23:13 CoreMisc\ActiveX
14:23:13 CoreMisc\ActiveX\Res1033
14:23:13 CoreMisc\ActiveX\ResIntl
14:23:13 CoreMisc\Res1033
14:23:13 Monarch
14:23:13 Monarch\Monr1033
14:23:13 Monarch\MonrIntl
14:23:13 Jet
14:23:13 CoreInst
14:23:13 CoreCOM
14:23:13 CoreCOM\Res1033
14:23:13 CoreCOM\ResIntl
14:23:13 CoreTool
14:23:13 CoreTool\Res1033
14:23:13 CoreTool\ResOther
14:23:13 DBLibCli
14:23:13 SFExt
14:23:13 SFExt\ActiveX
14:23:13 SFExt\ActiveX\Res1033
14:23:13 SFExt\ActiveX\ResIntl
14:23:13 SFExt\Res1033
14:23:13 SFExt\ResIntl
14:23:13 Trace
14:23:13 Trace\Res1033
14:23:13 Trace\ResOther
14:23:13 MiscCore
14:23:13 MC
14:23:13 MC\MC1033
14:23:13 MC\MCIntl
14:23:13 MC\Help
14:23:13 SQLMgr
14:23:13 SQLMgr\Res1033
14:23:13 SQLMgr\ResIntl
14:23:13 SvrTool
14:23:13 SvrTool\Res1033
14:23:13 SvrTool\ResIntl
14:23:13 DTSUI
14:23:13 DTSUI\Res1033
14:23:13 DTSUI\ResIntl
14:23:13 MSOlap
14:23:13 MSOlap\Res1033
14:23:13 MSOlap\ResIntl
14:23:13 ATL
14:23:13 ATL\winnt
14:23:13 ATL\win9x
14:23:13 MFC42U
14:23:13 VC
14:23:13 VB
14:23:13 OCX1
14:23:13 SQLAdHlp
14:23:13 SQLAdHlp\Res1033
14:23:13 SQLAdHlp\ResOther
14:23:13 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
14:23:13 End Action LogSelectedComponents
14:23:13 Begin Action InstallPkgs:
14:23:13 Begin Action: Locked Connectivity Files Check
14:23:13 ConnectivityLocked returned: 0
14:23:13 Der Vorgang wurde erfolgreich beendet.

14:23:13 End Action: Locked Connectivity Files Check
14:23:13 Setup is installing Microsoft Data Access Components (MDAC)
...
14:23:13 E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Other\sqlredis.exe /q:a
/C:"setupre.exe WARN=1 -s -SMS"
14:23:24 ExitCode: 0
14:23:24 Setup is installing Microsoft Distributed Transaction
Coordinator (MSDTC) ...
14:23:24 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir
"C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg
"E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Other\dtcsetup.exe" -LogFile
"C:\WINDOWS\sqlstp.log"
14:23:24 Process Exit Code: (0)
14:23:24 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
14:23:24 Setup is installing HTML Help ...
14:23:24 HTML Help installer exit code: 0
14:23:45 End Action InstallPkgs
14:23:45 Begin Action MoveFileData:
14:23:45 Enabled SELFREGISTERBATCH
14:23:45 Enabled CORECOMPONENTHANDLING
14:24:11 Begin Action: MoveFileDataSpecial
14:24:11 End Action: MoveFileDataSpecial
14:24:11 End Action MoveFileData
14:24:11 Begin Action ProcessAfterDataMove:
14:24:11 E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Binn\hhcol.exe
C:\Programme\Microsoft SQL Server\80\Tools\Books
14:24:11 End Action ProcessAfterDataMove
14:24:11 Begin Action BuildServer:
14:24:11 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 5
-ExePath "C:\Programme\Microsoft SQL Server\MSSQL\binn\sqlservr.exe"
-Service "MSSQLSERVER"
14:24:12 Process Exit Code: (0)
14:24:12 Begin Action: CreateRegistrySetSQL
14:24:12 End Action: CreateRegistrySetSQL
14:24:12 Begin Action: RegWriteSetupEntry
14:24:12 End Action: RegWriteSetupEntry
14:24:12 Begin Action: CreateSer
14:24:12 End Action: CreateSer
14:24:12 Begin Action: SkuIt
14:24:12 End Action: SkuIt
14:24:12 SetFileSecuritySQLAndAdmin for C:\Programme\Microsoft SQL
Server\MSSQL returned: 0, 0
14:24:12 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
14:24:12 Begin Action: UpdateSystemPath
14:24:12 Path successfully updated.
14:24:12
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Programme\­Java\jdk1.5.0_04\bin;C:\Borland\BCC55\bin;"C:\Programme\Symantec\Norton
Ghost 2003\";C:\Programme\Microsoft SQL
Server\80\Tools\BINN;C:\Programme\MySQL\MySQL Server 5.0\bin
14:24:12 End Action: UpdateSystemPath
14:24:13 C:\Programme\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "Arabic_CI_AS"
-H 459924 -U sa -P
###########################################################################­####

Starting Service ...

Arabic_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=COOSA;UID=sa;PWD=;database=master

Configuring Server ...

EXEC sp_grantlogin N'VORDEFINIERT\Administratoren'

[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to
'VORDEFINIERT\Administratoren'.

EXEC sp_addsrvrolemember N'VORDEFINIERT\Administratoren', 'sysadmin'

[Microsoft][ODBC SQL Server Driver][SQL
Server]'VORDEFINIERT\Administratoren' added to role 'sysadmin'.

update master.dbo.spt_server_info set attribute_value = @.@.version where
attribute_id = 2

EXEC sp_addserver N'COOSA', local

EXEC sp_configure 'allow updates', 1

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution
completed. If DBCC printed error messages, contact your system
administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option
'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to
install.

reconfigure with override

update master.dbo.sysaltfiles set size=1024 where name=N'tempdev'

EXEC sp_configure 'allow updates', 0

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution
completed. If DBCC printed error messages, contact your system
administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option
'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to
install.

reconfigure with override

Disconnecting from Server ...

Stopping Service ...

SQL Server has been successfully configured!

###########################################################################­####

14:24:42 Process Exit Code: (0)
14:24:42 End Action BuildServer
14:24:42 Begin Action SelfRegiser
14:24:42 DLLRegisterServer atl.dll: 0, 0x0
14:24:50 Return code: 0
14:24:50 Begin Action SelfRegisterOnCluster
14:24:50 End Action SelfRegisterOnCluster
14:24:50 Begin Action RegisterSvrReplFiles
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\snapshot.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\distrib.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\replmerg.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\logread.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\qrdrsvc.exe-unregserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\snapshot.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\distrib.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\replmerg.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\logread.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\qrdrsvc.exe-regserver
14:24:51 End Action RegisterSvrReplFiles
14:24:51 Begin Action SelfRegisterCOMShared
14:24:51 End Action SelfRegisterCOMShared
14:24:51 End Action SelfRegister
14:24:51 Begin Action SetupRegistry:
14:24:51 SNMP service has been detected.
14:24:51 Begin Action RegWriteInstalledInstances:
14:24:51 End Action RegWriteInstalledInstances
14:24:51 Register this installation of SQL Server with MDAC
14:24:51 Completed registering this installation of SQL Server with
MDAC
14:25:07 An error occurred while creating one or more registry entries.
Please see C:\WINDOWS\\\sqlstp.log for details. The problem could be
caused by a low registry quota condition.
14:25:07 Action CleanUpInstall:
14:25:07 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4
-Service SQLSERVERAGENT
14:25:07 Process Exit Code: (1060) Der angegebene Dienst ist kein
installierter Dienst.

14:25:07 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4
-Service MSSQLSERVER
14:25:07 Process Exit Code: (0)
14:25:07 StatsGenerate returned: 2
14:25:07 StatsGenerate
(0x80000000,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
14:25:07 StatsGenerate -1,admin)
14:25:07 Installation Failed.

I got the indentical error when I attempted to install SQL 2000 Developer's Edition on XP Pro. My log file failure occurred at the same place yours did.

I had recently installed .Net framework, .Net SDK, and ASP Web Matrix. I made a lucky guess that they were causing the problem.

I did an uninstall of:
.Net framework
.Net SDK
ASP Web Matrix

I deleted the sub folders in c:\Program Files\Microsoft SQL Server.

Then SQL 2000 DE installed successfully, and I reinstalled the .Net framework & ASP Web Matrix.

Hope this helps.

Frustrating Installation Error

I was installing SQL Server on my machine and during installation my PC
freezed. It happens frequently on my machine as my bad luck sticks frequenctly to my side. So i tried after
restarting to install it again and since then i always get the same
error message:
"An error occurred while creating one or more registry entries. Please
see C:\WINDOWS\sqlstp.log for details. The problem could be caused by a
low registry quota condition"
I have tried to clean the registry during the installation bt chosing "advanced options" -> "Rebuild registry" and i don't know what else i could
do to solve this issue. I'd like to remark that i also deleted the SQL Server keys from Registry as suggested from Microsoft to delete default and special named instances.

I also deleted every thing under %TEMP%; I even installed third pary registry tools to clean the registry such as RegistryFix, Registry Mechanic and AMUST.

Finally, i'm using Windows XP Professional SP2.

Any help?

The log file lists the following:

14:22:27 Begin Setup
14:22:27 8.00.194
14:22:27 Mode = Normal
14:22:27 ModeType = NORMAL
14:22:27 GetDefinitionEx returned: 0, Extended: 0x0
14:22:27 ValueFTS returned: 1
14:22:27 ValuePID returned: 1
14:22:27 ValueLic returned: 0
14:22:27 System: Windows NT WorkStation
14:22:27 SQL Server ProductType: Developer Edition [0x3]
14:22:27 Begin Action: SetupInitialize
14:22:27 End Action SetupInitialize
14:22:27 Begin Action: SetupInstall
14:22:27 Reading
Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ...
14:22:27 CommonFilesDir=C:\Programme\Gemeinsame Dateien
14:22:27 Windows Directory=C:\WINDOWS\
14:22:27 Program Files=C:\Programme\
14:22:27 TEMPDIR=C:\WINDOWS\TEMP\
14:22:27 Begin Action: SetupInstall
14:22:27 digpid size : 256
14:22:27 digpid size : 164
14:22:27 Begin Action: CheckFixedRequirements
14:22:27 Platform ID: 0xf000000
14:22:27 Version: 5.1.2600
14:22:27 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.2900.2805
14:22:27 End Action: CheckFixedRequirements
14:22:27 Begin Action: ShowDialogs
14:22:27 Initial Dialog Mask: 0x83000f7, Disable Back=0x1
14:22:27 Begin Action ShowDialogsHlpr: 0x1
14:22:27 Begin Action: DialogShowSdWelcome
14:22:28 End Action DialogShowSdWelcome
14:22:28 Dialog 0x1 returned: 1
14:22:28 End Action ShowDialogsHlpr
14:22:28 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
14:22:28 Begin Action ShowDialogsHlpr: 0x2
14:22:28 Begin Action: DialogShowSdMachineName
14:22:30 ShowDlgMachine returned: 1
14:22:30 Name = COOSA, Type = 0x1
14:22:30 Begin Action: CheckRequirements
14:22:30 Processor Architecture: x86 (Pentium)
14:22:30 Service Pack: 512
14:22:30 ComputerName: COOSA
14:22:30 User Name: admin
14:22:30 IsAllAccessAllowed returned: 1
14:22:30 OS Language: 0x401
14:22:30 End Action CheckRequirements
14:22:30 This combination of Package and Operating System allows a full
product install.
14:22:30 CreateSetupTopology(COOSA), Handle : 0x1b04098, returned : 0
14:22:30 CreateSetupTopology returned : 0, Handle : 0x1b04098
14:22:30 Topology Type : 1, Return Value : 0
14:22:30 ST_GetPhysicalNode returned : 0, PNHandle : 0x1b040c0
14:22:30 PN_EnumerateEx returned : 0
14:22:30 PN_GetSQLStates returned : 0, SqlStates : 0x80000000
14:22:30 PN_StartScan [0x1b040c0] returned : 0
14:22:30 PN_GetNext [0x1b040c0] returned : 18, Handle: [0x0]
14:22:30 No more items in enumeration.
14:22:30 ReleaseSetupTopology
14:22:30 Named instance limit: 100, quota: 0
14:22:30 End Action DialogShowSdMachineName
14:22:30 begin ShowDialogsUpdateMask
14:22:30 nFullMask = 0x83000f7, nCurrent = 0x2, nDirection = 0
14:22:30 Updated Dialog Mask: 0xbf00037, Disable Back = 0x1
14:22:30 Dialog 0x2 returned: 0
14:22:30 End Action ShowDialogsHlpr
14:22:30 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
14:22:30 Begin Action ShowDialogsHlpr: 0x4
14:22:30 Begin Action: DialogShowSdInstallMode
14:22:36 ShowDlgInstallMode returned: 1
14:22:36 InstallMode : 0x1
14:22:36 End Action DialogShowSdInstallMode
14:22:36 begin ShowDialogsUpdateMask
14:22:36 nFullMask = 0xbf00037, nCurrent = 0x4, nDirection = 1
14:22:36 Updated Dialog Mask: 0xbf40037, Disable Back = 0x1
14:22:36 Dialog 0x4 returned: 1
14:22:36 End Action ShowDialogsHlpr
14:22:36 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
14:22:36 Begin Action ShowDialogsHlpr: 0x10
14:22:36 Begin Action: DialogShowSdRegisterUserEx
14:22:42 End Action DialogShowSdRegisterUserEx
14:22:42 Dialog 0x10 returned: 1
14:22:42 End Action ShowDialogsHlpr
14:22:42 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
14:22:42 Begin Action ShowDialogsHlpr: 0x20
14:22:42 Begin Action: DialogShowSdLicense
14:22:43 End Action DialogShowSdLicense
14:22:43 Dialog 0x20 returned: 1
14:22:43 End Action ShowDialogsHlpr
14:22:43 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
14:22:43 Begin Action ShowDialogsHlpr: 0x40000
14:22:43 Begin Action: DialogShowSdCliSvr
14:22:43 DisplaySystemPreReq
14:22:45 ShowDlgClientServerSelect returned: 1
14:22:45 Type : 0x2
14:22:45 End Action DialogShowSdCliSvr
14:22:45 begin ShowDialogsUpdateMask
14:22:45 nFullMask = 0xbf40037, nCurrent = 0x40000, nDirection = 1
14:22:45 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
14:22:45 Dialog 0x40000 returned: 1
14:22:45 End Action ShowDialogsHlpr
14:22:45 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
14:22:45 Begin Action ShowDialogsHlpr: 0x80000
14:22:45 Begin Action: DialogShowSdInstanceName
14:22:45 Begin Action: ShowDlgInstanceName
14:22:47 End Action: ShowDlgInstanceName
14:22:47 ShowDlgInstanceName returned : 1
14:22:47 InstanceName : MSSQLSERVER
14:22:47 CreateSetupTopology(COOSA), Handle : 0x1b04098, returned : 0
14:22:47 CreateSetupTopology returned : 0, Handle : 0x1b04098
14:22:47 Topology Type : 1, Return Value : 0
14:22:47 ST_GetPhysicalNode returned : 0, PNHandle : 0x1b040c0
14:22:47 PN_EnumerateEx returned : 0
14:22:47 PN_GetSQLStates returned : 0, SqlStates : 0x80000000
14:22:47 PN_StartScan [0x1b040c0] returned : 0
14:22:47 PN_GetNext [0x1b040c0] returned : 18, Handle: [0x0]
14:22:47 No more items in enumeration.
14:22:47 ReleaseSetupTopology
14:22:47 End Action DialogShowSdInstanceName
14:22:47 begin ShowDialogsUpdateMask
14:22:47 nFullMask = 0xbfc0037, nCurrent = 0x80000, nDirection = 1
14:22:47 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
14:22:47 Dialog 0x80000 returned: 1
14:22:47 End Action ShowDialogsHlpr
14:22:47 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
14:22:47 Begin Action ShowDialogsHlpr: 0x100000
14:22:47 Begin Action: DialogShowSdSetupType
14:22:47 Begin Action: Setup Type
14:23:05 SQL program folder: C:\Programme\Microsoft SQL Server
14:23:05 SQL data folder: C:\Programme\Microsoft SQL Server
14:23:05 Windows system folder: C:\WINDOWS\system32\
14:23:05 Prog req: 38073, Data req: 34432, Sys req: 158694
14:23:05 Prog avail: 1481708, Data avail: 1481708, Sys avail: 1481708
14:23:05 Prog req vs. avail, 231199, 1481708
14:23:05 Data req vs. avail, 34432, 1481708
14:23:05 Sys req vs. avail, 193126, 1481708
14:23:05 DisplaySystemPreReq
14:23:05 [SetupTypeSQL]
14:23:05 szDir = C:\Programme\Microsoft SQL Server
14:23:05 szDir = %PROGRAMFILES%\Microsoft SQL Server
14:23:05 Result = 301
14:23:05 szDataDir = C:\Programme\Microsoft SQL Server
14:23:05 szDataDir = %PROGRAMFILES%\Microsoft SQL Server
14:23:05 End Action: Setup Type
14:23:05 Setup Type: Typical (301)
14:23:05 End Action DialogShowSdSetupType
14:23:05 begin ShowDialogsUpdateMask
14:23:05 nFullMask = 0xbfc0037, nCurrent = 0x100000, nDirection = 301
14:23:05 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:05 Dialog 0x100000 returned: 301
14:23:05 End Action ShowDialogsHlpr
14:23:05 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
14:23:05 Begin Action ShowDialogsHlpr: 0x400000
14:23:05 Begin Action: DlgServices
14:23:10 ShowDlgServices returned: 1
14:23:10 [DlgServices]
14:23:10 Local-Domain = 3855
14:23:10 AutoStart = 15
14:23:10 Result = 1
14:23:10 End Action DlgServices
14:23:10 begin ShowDialogsUpdateMask
14:23:10 nFullMask = 0xbdc0037, nCurrent = 0x400000, nDirection = 1
14:23:10 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:10 Dialog 0x400000 returned: 1
14:23:10 End Action ShowDialogsHlpr
14:23:10 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
14:23:10 Begin Action ShowDialogsHlpr: 0x800000
14:23:10 Begin Action: DlgSQLSecurity
14:23:12 ShowDlgSQLSecurity returned: 1
14:23:12 LoginMode = 1,szPwd
14:23:12 End Action DlgSQLSecurity
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x800000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x800000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
14:23:12 Begin Action ShowDialogsHlpr: 0x1000000
14:23:12 Begin Action: DlgCollation
14:23:12 ShowDlgCollation returned: 1
14:23:12 collation_name = Arabic_CI_AS,locale_name = Arabic,lcid =
0x401,SortId = 0,dwCompFlags = 0x30001
14:23:12 End Action DlgCollation
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x1000000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x1000000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
14:23:12 Begin Action ShowDialogsHlpr: 0x2000000
14:23:12 Begin Action: DlgNetwork
14:23:12 ShowDlgNetwork returned: 1
14:23:12 [DlgServerNetwork]
14:23:12 NetworkLibs = 255
14:23:12 TCPPort = 1433
14:23:12 TCPPrxy = Default
14:23:12 NMPPipeName = \\.\pipe\sql\query
14:23:12 Result = 1
14:23:12 End Action DlgNetwork
14:23:12 begin ShowDialogsUpdateMask
14:23:12 nFullMask = 0xbdc0037, nCurrent = 0x2000000, nDirection = 1
14:23:12 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:12 Dialog 0x2000000 returned: 1
14:23:12 End Action ShowDialogsHlpr
14:23:12 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
14:23:12 Begin Action ShowDialogsHlpr: 0x8000000
14:23:12 Begin Action: DialogShowSdStartCopy
14:23:13 End Action DialogShowSdStartCopy
14:23:13 begin ShowDialogsUpdateMask
14:23:13 nFullMask = 0xbdc0037, nCurrent = 0x8000000, nDirection = 1
14:23:13 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
14:23:13 Dialog 0x8000000 returned: 1
14:23:13 End Action ShowDialogsHlpr
14:23:13 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
14:23:13 End Action ShowDialogs
14:23:13 Begin Action ProcessBeforeDataMove:
14:23:13 DeinstallStart returned (C:\Programme\Microsoft SQL
Server\MSSQL): 0
14:23:13 End Action ProcessBeforeDataMove:
14:23:13 Begin Action SetToolsComponentSelection:
14:23:13 End Action SetToolsComponentSelection:
14:23:13 Begin Action ProcessComponentSelection:
14:23:13 End Action ProcessComponentSelection
14:23:13 Begin Action LogSelectedComponents:
14:23:13 SQLProg
14:23:13 SQLProg\SQLServr
14:23:13 SQLProg\SQLServr\Help
14:23:13 SQLProg\SQLServr\SCMDev
14:23:13 SQLProg\SQLServr\SCMDev\SCMh
14:23:13 SQLProg\SQLServr\SCMDev\SCMX86Lb
14:23:13 SQLProg\SQLServr\SCMDev\SCMALb
14:23:13 SQLProg\SQLServr\Rs1033
14:23:13 SQLProg\SQLServr\RsIntl
14:23:13 SQLProg\SQLServr\ActiveX
14:23:13 SQLProg\SQLServr\System
14:23:13 SQLProg\UpgTools
14:23:13 SQLProg\UpgTools\UpgSys
14:23:13 SQLProg\UpgTools\ActiveX
14:23:13 SQLProg\UpgTools\Res1033
14:23:13 SQLProg\UpgTools\ResOther
14:23:13 SQLProg\UpgTools\Resld
14:23:13 SQLProg\ReplSupp
14:23:13 SQLProg\ReplSupp\ReplDat
14:23:13 SQLProg\ReplSupp\RepComm
14:23:13 SQLProg\ReplSupp\RepNoDk
14:23:13 SQLProg\ReplSupp\ActiveX
14:23:13 SQLProg\Install
14:23:13 SQLProg\System
14:23:13 SQLProg\SvrExt
14:23:13 SQLProg\SvrExt\Help
14:23:13 SQLProg\SvrExt\SvrExtRs
14:23:13 SQLProg\SvrExt\ResIntl
14:23:13 SQLProg\Dat
14:23:13 SQLProg\DatSmpl
14:23:13 SQLProg\BaseSys
14:23:13 SQLProg\BaseBinn
14:23:13 SQLProg\BaseInst
14:23:13 SQLProg\Symbols
14:23:13 SQLProg\Symbols\EXE
14:23:13 SQLProg\Symbols\DLL
14:23:13 SQLProg\Perfmon
14:23:13 SQLProg\Perfmon\System
14:23:13 SQLProg\Root
14:23:13 MgtTool
14:23:13 MgtTool\SEM
14:23:13 MgtTool\SEM\HTML
14:23:13 MgtTool\SEM\MSD98
14:23:13 MgtTool\SEM\MSD98SYS
14:23:13 MgtTool\SEM\MSD98Res
14:23:13 MgtTool\SEM\MSD98Hlp
14:23:13 MgtTool\SEM\Help
14:23:13 MgtTool\SEM\Res1033
14:23:13 MgtTool\SEM\ResIntl
14:23:13 MgtTool\SEM\MSD98RsI
14:23:13 MgtTool\SEM\ActiveX
14:23:13 MgtTool\SEM\ActiveX\Res1033
14:23:13 MgtTool\SEM\ActiveX\ResIntl
14:23:13 MgtTool\SEM\Scripts
14:23:13 MgtTool\SEM\OLEDB
14:23:13 MgtTool\SEM\OLEDB\Res1033
14:23:13 MgtTool\SEM\OLEDB\ResIntl
14:23:13 MgtTool\Profiler
14:23:13 MgtTool\Profiler\Help
14:23:13 MgtTool\Profiler\Res1033
14:23:13 MgtTool\Profiler\ResIntl
14:23:13 MgtTool\Qryanlz
14:23:13 MgtTool\Qryanlz\Help
14:23:13 MgtTool\Qryanlz\Res1033
14:23:13 MgtTool\Qryanlz\ResIntl
14:23:13 MgtTool\DTCCLi
14:23:13 MgtTool\Wzcnflct
14:23:13 MgtTool\Wzcnflct\WzcnHlp
14:23:13 MgtTool\Wzcnflct\Wzcn1033
14:23:13 MgtTool\Wzcnflct\WzcnOthr
14:23:13 MgtTool\Wzcnflct\WzcnCmn
14:23:13 MgtTool\UtilSys
14:23:13 MgtTool\UtilBinn
14:23:13 Connect
14:23:13 Connect\ConnSys
14:23:13 Books
14:23:13 Books\Bookso
14:23:13 Books\Bookso\Utils
14:23:13 DevTools
14:23:13 DevTools\Dbg Int
14:23:13 DevTools\Dbg Int\Dbg Int Common
14:23:13 DevTools\Dbg Int\EXE
14:23:13 CoreRepl
14:23:13 CoreRepl\Res1033
14:23:13 CoreRepl\ResIntl
14:23:13 Core
14:23:13 Core\Res1033
14:23:13 Core\ResOther
14:23:13 Repostry
14:23:13 Repostry\RepstSys
14:23:13 Repostry\Res1033
14:23:13 Repostry\ResIntl
14:23:13 CoreMisc
14:23:13 CoreMisc\ActiveX
14:23:13 CoreMisc\ActiveX\Res1033
14:23:13 CoreMisc\ActiveX\ResIntl
14:23:13 CoreMisc\Res1033
14:23:13 Monarch
14:23:13 Monarch\Monr1033
14:23:13 Monarch\MonrIntl
14:23:13 Jet
14:23:13 CoreInst
14:23:13 CoreCOM
14:23:13 CoreCOM\Res1033
14:23:13 CoreCOM\ResIntl
14:23:13 CoreTool
14:23:13 CoreTool\Res1033
14:23:13 CoreTool\ResOther
14:23:13 DBLibCli
14:23:13 SFExt
14:23:13 SFExt\ActiveX
14:23:13 SFExt\ActiveX\Res1033
14:23:13 SFExt\ActiveX\ResIntl
14:23:13 SFExt\Res1033
14:23:13 SFExt\ResIntl
14:23:13 Trace
14:23:13 Trace\Res1033
14:23:13 Trace\ResOther
14:23:13 MiscCore
14:23:13 MC
14:23:13 MC\MC1033
14:23:13 MC\MCIntl
14:23:13 MC\Help
14:23:13 SQLMgr
14:23:13 SQLMgr\Res1033
14:23:13 SQLMgr\ResIntl
14:23:13 SvrTool
14:23:13 SvrTool\Res1033
14:23:13 SvrTool\ResIntl
14:23:13 DTSUI
14:23:13 DTSUI\Res1033
14:23:13 DTSUI\ResIntl
14:23:13 MSOlap
14:23:13 MSOlap\Res1033
14:23:13 MSOlap\ResIntl
14:23:13 ATL
14:23:13 ATL\winnt
14:23:13 ATL\win9x
14:23:13 MFC42U
14:23:13 VC
14:23:13 VB
14:23:13 OCX1
14:23:13 SQLAdHlp
14:23:13 SQLAdHlp\Res1033
14:23:13 SQLAdHlp\ResOther
14:23:13 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
14:23:13 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
14:23:13 End Action LogSelectedComponents
14:23:13 Begin Action InstallPkgs:
14:23:13 Begin Action: Locked Connectivity Files Check
14:23:13 ConnectivityLocked returned: 0
14:23:13 Der Vorgang wurde erfolgreich beendet.

14:23:13 End Action: Locked Connectivity Files Check
14:23:13 Setup is installing Microsoft Data Access Components (MDAC)
...
14:23:13 E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Other\sqlredis.exe /q:a
/C:"setupre.exe WARN=1 -s -SMS"
14:23:24 ExitCode: 0
14:23:24 Setup is installing Microsoft Distributed Transaction
Coordinator (MSDTC) ...
14:23:24 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir
"C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg
"E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Other\dtcsetup.exe" -LogFile
"C:\WINDOWS\sqlstp.log"
14:23:24 Process Exit Code: (0)
14:23:24 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
14:23:24 Setup is installing HTML Help ...
14:23:24 HTML Help installer exit code: 0
14:23:45 End Action InstallPkgs
14:23:45 Begin Action MoveFileData:
14:23:45 Enabled SELFREGISTERBATCH
14:23:45 Enabled CORECOMPONENTHANDLING
14:24:11 Begin Action: MoveFileDataSpecial
14:24:11 End Action: MoveFileDataSpecial
14:24:11 End Action MoveFileData
14:24:11 Begin Action ProcessAfterDataMove:
14:24:11 E:\SOFTWA~1\DEV\DB\SQL200~1\x86\Binn\hhcol.exe
C:\Programme\Microsoft SQL Server\80\Tools\Books
14:24:11 End Action ProcessAfterDataMove
14:24:11 Begin Action BuildServer:
14:24:11 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 5
-ExePath "C:\Programme\Microsoft SQL Server\MSSQL\binn\sqlservr.exe"
-Service "MSSQLSERVER"
14:24:12 Process Exit Code: (0)
14:24:12 Begin Action: CreateRegistrySetSQL
14:24:12 End Action: CreateRegistrySetSQL
14:24:12 Begin Action: RegWriteSetupEntry
14:24:12 End Action: RegWriteSetupEntry
14:24:12 Begin Action: CreateSer
14:24:12 End Action: CreateSer
14:24:12 Begin Action: SkuIt
14:24:12 End Action: SkuIt
14:24:12 SetFileSecuritySQLAndAdmin for C:\Programme\Microsoft SQL
Server\MSSQL returned: 0, 0
14:24:12 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
14:24:12 Begin Action: UpdateSystemPath
14:24:12 Path successfully updated.
14:24:12
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Programme\­Java\jdk1.5.0_04\bin;C:\Borland\BCC55\bin;"C:\Programme\Symantec\Norton
Ghost 2003\";C:\Programme\Microsoft SQL
Server\80\Tools\BINN;C:\Programme\MySQL\MySQL Server 5.0\bin
14:24:12 End Action: UpdateSystemPath
14:24:13 C:\Programme\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "Arabic_CI_AS"
-H 459924 -U sa -P
###########################################################################­####

Starting Service ...

Arabic_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=COOSA;UID=sa;PWD=;database=master

Configuring Server ...

EXEC sp_grantlogin N'VORDEFINIERT\Administratoren'

[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to
'VORDEFINIERT\Administratoren'.

EXEC sp_addsrvrolemember N'VORDEFINIERT\Administratoren', 'sysadmin'

[Microsoft][ODBC SQL Server Driver][SQL
Server]'VORDEFINIERT\Administratoren' added to role 'sysadmin'.

update master.dbo.spt_server_info set attribute_value = @.@.version where
attribute_id = 2

EXEC sp_addserver N'COOSA', local

EXEC sp_configure 'allow updates', 1

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution
completed. If DBCC printed error messages, contact your system
administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option
'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to
install.

reconfigure with override

update master.dbo.sysaltfiles set size=1024 where name=N'tempdev'

EXEC sp_configure 'allow updates', 0

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution
completed. If DBCC printed error messages, contact your system
administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option
'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to
install.

reconfigure with override

Disconnecting from Server ...

Stopping Service ...

SQL Server has been successfully configured!

###########################################################################­####

14:24:42 Process Exit Code: (0)
14:24:42 End Action BuildServer
14:24:42 Begin Action SelfRegiser
14:24:42 DLLRegisterServer atl.dll: 0, 0x0
14:24:50 Return code: 0
14:24:50 Begin Action SelfRegisterOnCluster
14:24:50 End Action SelfRegisterOnCluster
14:24:50 Begin Action RegisterSvrReplFiles
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\snapshot.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\distrib.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\replmerg.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\logread.exe-unregserver
14:24:50 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\qrdrsvc.exe-unregserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\snapshot.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\distrib.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\replmerg.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\logread.exe-regserver
14:24:51 **** File registered: C:\Programme\Microsoft SQL
Server\80\COM\qrdrsvc.exe-regserver
14:24:51 End Action RegisterSvrReplFiles
14:24:51 Begin Action SelfRegisterCOMShared
14:24:51 End Action SelfRegisterCOMShared
14:24:51 End Action SelfRegister
14:24:51 Begin Action SetupRegistry:
14:24:51 SNMP service has been detected.
14:24:51 Begin Action RegWriteInstalledInstances:
14:24:51 End Action RegWriteInstalledInstances
14:24:51 Register this installation of SQL Server with MDAC
14:24:51 Completed registering this installation of SQL Server with
MDAC
14:25:07 An error occurred while creating one or more registry entries.
Please see C:\WINDOWS\\\sqlstp.log for details. The problem could be
caused by a low registry quota condition.
14:25:07 Action CleanUpInstall:
14:25:07 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4
-Service SQLSERVERAGENT
14:25:07 Process Exit Code: (1060) Der angegebene Dienst ist kein
installierter Dienst.

14:25:07 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4
-Service MSSQLSERVER
14:25:07 Process Exit Code: (0)
14:25:07 StatsGenerate returned: 2
14:25:07 StatsGenerate
(0x80000000,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
14:25:07 StatsGenerate -1,admin)
14:25:07 Installation Failed.

I got the indentical error when I attempted to install SQL 2000 Developer's Edition on XP Pro. My log file failure occurred at the same place yours did.

I had recently installed .Net framework, .Net SDK, and ASP Web Matrix. I made a lucky guess that they were causing the problem.

I did an uninstall of:
.Net framework
.Net SDK
ASP Web Matrix

I deleted the sub folders in c:\Program Files\Microsoft SQL Server.

Then SQL 2000 DE installed successfully, and I reinstalled the .Net framework & ASP Web Matrix.

Hope this helps.

frequently updated tables

Hi
I have a transaction table that is very frequently updated, so I have no
indexes on it. I also need to be able to run queries against this data on,
for example, a date range. I think the easiest solution would be to extract
data on a daily basis onto another table with indexes. Or should I be looking
at some sort of data warehousing/data cube approach? Any ideas/resources?
Thanks
if your just updating the table i dont see any reason why you couldnt
index that table and run data off of it. and if you would be able to
export it to a different table once a day i'm guess the data your
viewing isnt live data you need to see right away. i'd just index that
table and run queries off of it. just set all the tables your
selecting from 'WITH (NOLOCK)' then it wont matter if a record is
being access at that time. it doesnt sound like your worried about any
type of dirty reads. if it is being inserted into quite frequently you
might have to take another approach or run a job to reindex at night.
i'm not 100% sure of your exact situation. hope that helps.
|||We have been advised in the past that it wasn't a good idea to have indexes
on the transaction table that is being frequently written too i.e. less than
a second between inserts, but I'd still like to query the data. Without some
sort of index, the query ends up doing a full table scan on a massive table,
so I think I need some sort of extract to an indexed version to make these
queries manageable.
"GlennThomas5" wrote:

> if your just updating the table i dont see any reason why you couldnt
> index that table and run data off of it. and if you would be able to
> export it to a different table once a day i'm guess the data your
> viewing isnt live data you need to see right away. i'd just index that
> table and run queries off of it. just set all the tables your
> selecting from 'WITH (NOLOCK)' then it wont matter if a record is
> being access at that time. it doesnt sound like your worried about any
> type of dirty reads. if it is being inserted into quite frequently you
> might have to take another approach or run a job to reindex at night.
> i'm not 100% sure of your exact situation. hope that helps.
>
|||Who ever told you that certainly didn't know what they were talking about.
If you are going to update a row you need to know which row to update
otherwise you scan and most likely lock the entire table. If you need to
query it (which that is what tables are for) and don't want all the rows you
also need an index. The trick is to pick the right column(s) to index and
the correct index type. If you post the DDL for the table and a sample of
the queries you run against it we can help you decide on the proper
indexing.
Andrew J. Kelly SQL MVP
"Gary Homewood" <GaryHomewood@.discussions.microsoft.com> wrote in message
news:AE25E15B-FC19-4FDF-BEF1-DEAAA4671C5D@.microsoft.com...[vbcol=seagreen]
> We have been advised in the past that it wasn't a good idea to have
> indexes
> on the transaction table that is being frequently written too i.e. less
> than
> a second between inserts, but I'd still like to query the data. Without
> some
> sort of index, the query ends up doing a full table scan on a massive
> table,
> so I think I need some sort of extract to an indexed version to make these
> queries manageable.
>
> "GlennThomas5" wrote:
|||OK here's what I'm doing. My transaction table is written to potentially
several times a second; this is just an insert, not an update. I was under
the impression that if I had an index on such a large and rapidly expanding
table, there would be a performance hit when the index was recalculated as
rows are written to the table. I would subsequently like to retrieve results
from this table for a particular date range, in which case I do really need
an index on date to avoid doing a full table scan. Is there a way to get SQL
Server to maybe ignore the date index as rows are being inserted, and then
perhaps do a reindexing of the table once a day? Or do I need to extract data
to some sort of warehouse or data cube with a date index? In which case I'd
still have the same problem, because I'd need to extract entries from my very
large transaction table for a particular date.
Thanks for your replies so far. Hope I've phrased my problem a bit more
clearly this time.
"Andrew J. Kelly" wrote:

> Who ever told you that certainly didn't know what they were talking about.
> If you are going to update a row you need to know which row to update
> otherwise you scan and most likely lock the entire table. If you need to
> query it (which that is what tables are for) and don't want all the rows you
> also need an index. The trick is to pick the right column(s) to index and
> the correct index type. If you post the DDL for the table and a sample of
> the queries you run against it we can help you decide on the proper
> indexing.
> --
> Andrew J. Kelly SQL MVP
>
> "Gary Homewood" <GaryHomewood@.discussions.microsoft.com> wrote in message
> news:AE25E15B-FC19-4FDF-BEF1-DEAAA4671C5D@.microsoft.com...
>
>

frequently updated tables

Hi
I have a transaction table that is very frequently updated, so I have no
indexes on it. I also need to be able to run queries against this data on,
for example, a date range. I think the easiest solution would be to extract
data on a daily basis onto another table with indexes. Or should I be looking
at some sort of data warehousing/data cube approach? Any ideas/resources?
Thanksif your just updating the table i dont see any reason why you couldnt
index that table and run data off of it. and if you would be able to
export it to a different table once a day i'm guess the data your
viewing isnt live data you need to see right away. i'd just index that
table and run queries off of it. just set all the tables your
selecting from 'WITH (NOLOCK)' then it wont matter if a record is
being access at that time. it doesnt sound like your worried about any
type of dirty reads. if it is being inserted into quite frequently you
might have to take another approach or run a job to reindex at night.
i'm not 100% sure of your exact situation. hope that helps.|||We have been advised in the past that it wasn't a good idea to have indexes
on the transaction table that is being frequently written too i.e. less than
a second between inserts, but I'd still like to query the data. Without some
sort of index, the query ends up doing a full table scan on a massive table,
so I think I need some sort of extract to an indexed version to make these
queries manageable.
"GlennThomas5" wrote:
> if your just updating the table i dont see any reason why you couldnt
> index that table and run data off of it. and if you would be able to
> export it to a different table once a day i'm guess the data your
> viewing isnt live data you need to see right away. i'd just index that
> table and run queries off of it. just set all the tables your
> selecting from 'WITH (NOLOCK)' then it wont matter if a record is
> being access at that time. it doesnt sound like your worried about any
> type of dirty reads. if it is being inserted into quite frequently you
> might have to take another approach or run a job to reindex at night.
> i'm not 100% sure of your exact situation. hope that helps.
>|||Who ever told you that certainly didn't know what they were talking about.
If you are going to update a row you need to know which row to update
otherwise you scan and most likely lock the entire table. If you need to
query it (which that is what tables are for) and don't want all the rows you
also need an index. The trick is to pick the right column(s) to index and
the correct index type. If you post the DDL for the table and a sample of
the queries you run against it we can help you decide on the proper
indexing.
--
Andrew J. Kelly SQL MVP
"Gary Homewood" <GaryHomewood@.discussions.microsoft.com> wrote in message
news:AE25E15B-FC19-4FDF-BEF1-DEAAA4671C5D@.microsoft.com...
> We have been advised in the past that it wasn't a good idea to have
> indexes
> on the transaction table that is being frequently written too i.e. less
> than
> a second between inserts, but I'd still like to query the data. Without
> some
> sort of index, the query ends up doing a full table scan on a massive
> table,
> so I think I need some sort of extract to an indexed version to make these
> queries manageable.
>
> "GlennThomas5" wrote:
>> if your just updating the table i dont see any reason why you couldnt
>> index that table and run data off of it. and if you would be able to
>> export it to a different table once a day i'm guess the data your
>> viewing isnt live data you need to see right away. i'd just index that
>> table and run queries off of it. just set all the tables your
>> selecting from 'WITH (NOLOCK)' then it wont matter if a record is
>> being access at that time. it doesnt sound like your worried about any
>> type of dirty reads. if it is being inserted into quite frequently you
>> might have to take another approach or run a job to reindex at night.
>> i'm not 100% sure of your exact situation. hope that helps.
>>|||OK here's what I'm doing. My transaction table is written to potentially
several times a second; this is just an insert, not an update. I was under
the impression that if I had an index on such a large and rapidly expanding
table, there would be a performance hit when the index was recalculated as
rows are written to the table. I would subsequently like to retrieve results
from this table for a particular date range, in which case I do really need
an index on date to avoid doing a full table scan. Is there a way to get SQL
Server to maybe ignore the date index as rows are being inserted, and then
perhaps do a reindexing of the table once a day? Or do I need to extract data
to some sort of warehouse or data cube with a date index? In which case I'd
still have the same problem, because I'd need to extract entries from my very
large transaction table for a particular date.
Thanks for your replies so far. Hope I've phrased my problem a bit more
clearly this time.
"Andrew J. Kelly" wrote:
> Who ever told you that certainly didn't know what they were talking about.
> If you are going to update a row you need to know which row to update
> otherwise you scan and most likely lock the entire table. If you need to
> query it (which that is what tables are for) and don't want all the rows you
> also need an index. The trick is to pick the right column(s) to index and
> the correct index type. If you post the DDL for the table and a sample of
> the queries you run against it we can help you decide on the proper
> indexing.
> --
> Andrew J. Kelly SQL MVP
>
> "Gary Homewood" <GaryHomewood@.discussions.microsoft.com> wrote in message
> news:AE25E15B-FC19-4FDF-BEF1-DEAAA4671C5D@.microsoft.com...
> > We have been advised in the past that it wasn't a good idea to have
> > indexes
> > on the transaction table that is being frequently written too i.e. less
> > than
> > a second between inserts, but I'd still like to query the data. Without
> > some
> > sort of index, the query ends up doing a full table scan on a massive
> > table,
> > so I think I need some sort of extract to an indexed version to make these
> > queries manageable.
> >
> >
> >
> > "GlennThomas5" wrote:
> >
> >> if your just updating the table i dont see any reason why you couldnt
> >> index that table and run data off of it. and if you would be able to
> >> export it to a different table once a day i'm guess the data your
> >> viewing isnt live data you need to see right away. i'd just index that
> >> table and run queries off of it. just set all the tables your
> >> selecting from 'WITH (NOLOCK)' then it wont matter if a record is
> >> being access at that time. it doesnt sound like your worried about any
> >> type of dirty reads. if it is being inserted into quite frequently you
> >> might have to take another approach or run a job to reindex at night.
> >> i'm not 100% sure of your exact situation. hope that helps.
> >>
> >>
>
>

frequently updated tables

Hi
I have a transaction table that is very frequently updated, so I have no
indexes on it. I also need to be able to run queries against this data on,
for example, a date range. I think the easiest solution would be to extract
data on a daily basis onto another table with indexes. Or should I be lookin
g
at some sort of data warehousing/data cube approach? Any ideas/resources?
Thanksif your just updating the table i dont see any reason why you couldnt
index that table and run data off of it. and if you would be able to
export it to a different table once a day i'm guess the data your
viewing isnt live data you need to see right away. i'd just index that
table and run queries off of it. just set all the tables your
selecting from 'WITH (NOLOCK)' then it wont matter if a record is
being access at that time. it doesnt sound like your worried about any
type of dirty reads. if it is being inserted into quite frequently you
might have to take another approach or run a job to reindex at night.
i'm not 100% sure of your exact situation. hope that helps.|||We have been advised in the past that it wasn't a good idea to have indexes
on the transaction table that is being frequently written too i.e. less than
a second between inserts, but I'd still like to query the data. Without some
sort of index, the query ends up doing a full table scan on a massive table,
so I think I need some sort of extract to an indexed version to make these
queries manageable.
"GlennThomas5" wrote:

> if your just updating the table i dont see any reason why you couldnt
> index that table and run data off of it. and if you would be able to
> export it to a different table once a day i'm guess the data your
> viewing isnt live data you need to see right away. i'd just index that
> table and run queries off of it. just set all the tables your
> selecting from 'WITH (NOLOCK)' then it wont matter if a record is
> being access at that time. it doesnt sound like your worried about any
> type of dirty reads. if it is being inserted into quite frequently you
> might have to take another approach or run a job to reindex at night.
> i'm not 100% sure of your exact situation. hope that helps.
>|||Who ever told you that certainly didn't know what they were talking about.
If you are going to update a row you need to know which row to update
otherwise you scan and most likely lock the entire table. If you need to
query it (which that is what tables are for) and don't want all the rows you
also need an index. The trick is to pick the right column(s) to index and
the correct index type. If you post the DDL for the table and a sample of
the queries you run against it we can help you decide on the proper
indexing.
Andrew J. Kelly SQL MVP
"Gary Homewood" <GaryHomewood@.discussions.microsoft.com> wrote in message
news:AE25E15B-FC19-4FDF-BEF1-DEAAA4671C5D@.microsoft.com...[vbcol=seagreen]
> We have been advised in the past that it wasn't a good idea to have
> indexes
> on the transaction table that is being frequently written too i.e. less
> than
> a second between inserts, but I'd still like to query the data. Without
> some
> sort of index, the query ends up doing a full table scan on a massive
> table,
> so I think I need some sort of extract to an indexed version to make these
> queries manageable.
>
> "GlennThomas5" wrote:
>|||OK here's what I'm doing. My transaction table is written to potentially
several times a second; this is just an insert, not an update. I was under
the impression that if I had an index on such a large and rapidly expanding
table, there would be a performance hit when the index was recalculated as
rows are written to the table. I would subsequently like to retrieve results
from this table for a particular date range, in which case I do really need
an index on date to avoid doing a full table scan. Is there a way to get SQL
Server to maybe ignore the date index as rows are being inserted, and then
perhaps do a reindexing of the table once a day? Or do I need to extract dat
a
to some sort of warehouse or data cube with a date index? In which case I'd
still have the same problem, because I'd need to extract entries from my ver
y
large transaction table for a particular date.
Thanks for your replies so far. Hope I've phrased my problem a bit more
clearly this time.
"Andrew J. Kelly" wrote:

> Who ever told you that certainly didn't know what they were talking about.
> If you are going to update a row you need to know which row to update
> otherwise you scan and most likely lock the entire table. If you need to
> query it (which that is what tables are for) and don't want all the rows y
ou
> also need an index. The trick is to pick the right column(s) to index and
> the correct index type. If you post the DDL for the table and a sample of
> the queries you run against it we can help you decide on the proper
> indexing.
> --
> Andrew J. Kelly SQL MVP
>
> "Gary Homewood" <GaryHomewood@.discussions.microsoft.com> wrote in message
> news:AE25E15B-FC19-4FDF-BEF1-DEAAA4671C5D@.microsoft.com...
>
>

Frequently update and select Table Locking Problem

Hi guys,

I faced problem related to Locking and Isolation Level on Table(s).

My problems is there r some tables which r frequently updated, and I also want to fire select query over those tables every 1 seconds and want to get only committed records.

In current scenario we start transactions with Read Committed Lock for updating records. But in this scenario I can’t get select query result because of some of recourses r used by transactions so after some time it gives Deadlock error.

So I want solution like both operation run simultaneously and get only committed records at a time of transaction running.

Please help me for solving my problem.

It seems to me that a deadlock error would only happen if you were trying to update the same tables in different orders at the same time - i.e., Update tableA, tableB running at the same time as Update tableB, tableA. Txn1 would be waiting for Txn2 to finish, and Txn2 would be waiting for Txn1 to finish.

If what you are getting is just a locking block, it might be a different story.

|||

No in my scenario not happen as u told. In that only one trans running but by default the isolation level is READ_COMMITTED and in that when i trying to run select query it is going in waiting mode till trans is committed or roleback.

but i want to run both simultaniously and get only committed data

|||

Which version you are using 2000 or 2005? If you are using 2005, then i think you could use Snapshot isolation level.

|||

I am use 2005 .

I also found Snapshot Isolation solutions from google, but now my confusation is related to which of belowing two r better for my problem.

ALLOW_SNAPSHOT_ISOLATION

READ_COMMITTED_SNAPSHOT

Also I don't know differance about both of them. Please if u have any idea about them then tell me.

Thanks for giving this hint to solve my problem

|||

There is an excellent article about SQL Server 2005 Row Versioning Based Transaction Isolation.Here is the URL:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2k5snapshotisol.asp

Please go through the article carefully and workout the examples specified in it.It would work for u.

Let me know if have any problems.

Frequently update and select Table Locking Problem

Hi guys,

I faced problem related to Locking and Isolation Level on Table(s).

My problems is there r some tables which r frequently updated, and I also want to fire select query over those tables every 1 seconds and want to get only committed records.

In current scenario we start transactions with ReadCommitted Lock for updating records. But in this scenario I can’t get select query result because of some of recourses r used by transactions so after some time it gives Deadlock error.

So I want solution like both operation run simultaneously and get only committed records at a time of transaction running

Please help me for solving my problem.

have you tried explicit dirty-read options in the select query ?

select * from mytable with (nolock) where mycolumn = 'hahaha'|||Yes I tried with that option, but it also return uncommitted data which i don't want.|||You cannot read "commited records" only of a transaction since those records actually does not exists untile the tran is closed: updated records are commited all together when you issue a commit transaction.|||

That's thing i knw, but the problem is when any trans for update or insert start on table I can't fire select query on that resources (means that table(s)) and it is going in waiting mode till trans is not committed or roleback.

So i resolve only this problems....

|||That's exactly the expected behavior if you use transactions.
You can use the 'with (rowlock)' option on the update (avoiding transactions) if you don't want other users to be put in wait, in that case a dirty read is allowed.|||

I got one solutions for resolving my problem using Snapshot Isolation.

But there are two types of Isolation READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION

so If u have any idea about them please inform me.

Is this resolve my problem or not?

what is the differance between them?

|||

Try use

select * from SomeTable with(READPAST)

Quote from Server Books:

READPAST

Skip locked rows. This option causes a transaction to skip rows locked by other transactions that would ordinarily appear in the result set, rather than block the transaction waiting for the other transactions to release their locks on these rows. The READPAST lock hint applies only to transactions operating at READ COMMITTED isolation and will read only past row-level locks. Applies only to the SELECT statement.

|||

Two possibilities that I know of, and the one you suggest is one of them. Using snapshot you will get the way the row looked before it was in the process of being edited.

Using readpast, as Alexander suggests is the other.

The question is what the purpose of your read queries is:

If you want a periodic count of where you are in a process, use snapshot

If you want to fetch the next, unlocked row for editing, then use readpast. A common use of this might be a set of rows that you have clerks working on. So you might execute a query like:

select <columns>
from workToDo
where status = 'NOTSTARTED'

In this case it is desirous to skip exclusively locked rows as they might be in the process of being updated. Using snapshot in this case would stink because you never want the user to collide with itself.

|||

Snapshot isolation level is not available in MS SQL 2000.

>> select <columns>
>> from workToDo
>> where status = 'NOTSTARTED'

If there is no index on "status" field then deadlock may occur anyway. Even if there is index on "status" field deadlock may occur because if table is updated with large amount of data and distribution of key values has changed then server may ignore index until UPDATE STATISTICS executed (explicitly or due to it is marked as auto-updatable).

|||Thanks to all for giving different solution. I finally solved my problem using snapshot.

frequent timeouts on SQL Server 2000

I have been receiving timeout errors frequently form our database. Any
suggestions as to the cause?
Thanks.
Usarian
Hi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>

frequent timeouts on SQL Server 2000

I have been receiving timeout errors frequently form our database. Any
suggestions as to the cause?
Thanks.
UsarianHi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>

frequent timeouts on SQL Server 2000

I have been receiving timeout errors frequently form our database. Any
suggestions as to the cause?
Thanks.
UsarianHi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>