mssql 2000 v/s raid 5ee

Hallo all
I know mssql2000 v/s raid 5 is dont work (very slowly). Who knows if i
install mssql 2000 on raid 5ee (win 2003server standard) i will have
better performance or not ? I know the best performance is no raid 10
but i dont have.
Hi,
The performance depends up on the volume of data and amount of access. Take
a look into the below URL .
http://www-03.ibm.com/support/techdo...Index/WP100350
Thanks
Hari
<ebolasty@.op.pl> wrote in message
news:1160926718.834857.267660@.k70g2000cwa.googlegr oups.com...
> Hallo all
> I know mssql2000 v/s raid 5 is dont work (very slowly). Who knows if i
> install mssql 2000 on raid 5ee (win 2003server standard) i will have
> better performance or not ? I know the best performance is no raid 10
> but i dont have.
>
sql

mssql 2000 v/s raid 5ee

Hallo all
I know mssql2000 v/s raid 5 is dont work (very slowly). Who knows if i
install mssql 2000 on raid 5ee (win 2003server standard) i will have
better performance or not ? I know the best performance is no raid 10
but i dont have.Hi,
The performance depends up on the volume of data and amount of access. Take
a look into the below URL .
http://www-03.ibm.com/support/techd...bIndex/WP100350
Thanks
Hari
<ebolasty@.op.pl> wrote in message
news:1160926718.834857.267660@.k70g2000cwa.googlegroups.com...
> Hallo all
> I know mssql2000 v/s raid 5 is dont work (very slowly). Who knows if i
> install mssql 2000 on raid 5ee (win 2003server standard) i will have
> better performance or not ? I know the best performance is no raid 10
> but i dont have.
>

mssql 2000 v/s raid 5ee

Hallo all
I know mssql2000 v/s raid 5 is dont work (very slowly). Who knows if i
install mssql 2000 on raid 5ee (win 2003server standard) i will have
better performance or not ? I know the best performance is no raid 10
but i dont have.Hi,
The performance depends up on the volume of data and amount of access. Take
a look into the below URL .
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100350
Thanks
Hari
<ebolasty@.op.pl> wrote in message
news:1160926718.834857.267660@.k70g2000cwa.googlegroups.com...
> Hallo all
> I know mssql2000 v/s raid 5 is dont work (very slowly). Who knows if i
> install mssql 2000 on raid 5ee (win 2003server standard) i will have
> better performance or not ? I know the best performance is no raid 10
> but i dont have.
>

MSDTC Cannot Create Dependencies

Using MS-Article Q301600 I was able to create MSDTC group on a Windows 2003
server with SQL Server 2000 Cluster.
Next step is trying to add resources to the MSDTC group. I tried to add IP
Address, Network Name, or Physical disk to the dependeny list. Everytime I
get to dependency list it is empty.
Please help me add the dependencies to the MSDTC group.
Thanks,
Are the resources you are trying to add in the dependencies in a different
cluster group? You can only add resources to your dependency list if these
resources are in the SAME cluster group.
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

MSDTC

Hello Everyone,
Has anyone had any experience with the following error
message on a win2k standard edition, running on a win 2003
server?
"The XA Transaction Manager cannot load the requested XA
Dll since a registry entry is required for this operation.
Please create a string value in the registry under
HKLM\Software\Microsoft\MSDTC\XADLL where the value name
is the name of the dll in the format dllname.dll and the
value is the full path of the Dll. If you are not sure
about the name or path of your XA Dll then please check
the documentation for your XA provider. If this machine is
part of a cluster please note that this registry entry
needs to be made for each node in the cluster. cwbodbc.dll"
ANy help would be greatly appreciated.
TIA
Chris
Which data access API are you using, ODBC?
Which resource manager (database)?
The ODBC driver exposes the XA Switch entrypoints, that is the DLL you need
to register. If you are running on a cluster you need to repeat this on
every node of the cluster.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Chris Bellizzi" <anonymous@.discussions.microsoft.com> wrote in message
news:082101c49a54$be0956f0$a601280a@.phx.gbl...
> Hello Everyone,
> Has anyone had any experience with the following error
> message on a win2k standard edition, running on a win 2003
> server?
> "The XA Transaction Manager cannot load the requested XA
> Dll since a registry entry is required for this operation.
> Please create a string value in the registry under
> HKLM\Software\Microsoft\MSDTC\XADLL where the value name
> is the name of the dll in the format dllname.dll and the
> value is the full path of the Dll. If you are not sure
> about the name or path of your XA Dll then please check
> the documentation for your XA provider. If this machine is
> part of a cluster please note that this registry entry
> needs to be made for each node in the cluster. cwbodbc.dll"
> ANy help would be greatly appreciated.
> TIA
> Chris
>

MSDTC

Not 100% sure this is the right pace to post, but anyway...
We're having some problems with MSDTC. I have servers running Windows 2003
Server Standard Edition (no service packs) and each running SQL Server 2000.
We are using MSDTC to manage distributed transactions involving the
databases on these servers. The application kicks of a distributed
transaction using a class derived from ServiceComponent and then calls a
number of SQL Stored Procedures on the 3 servers. These stored procedures ca
n
access any of the 3 servers.
Most of the time this is working fine, but we seem to be getting some
intermittent problem. Looking in the MSDTC part of Componet Services, we've
noticed some transactions not resolving themselves after serveral hours. The
only way we can seem to resolve them one way or another is to kill the SQL
Server process associated with that transaction. In addition to this the siz
e
of tempdb keeps growing and only reduces once we've killed the offending
processes.
How is it that MSDTC allows these transactions to hang around for so long?I forgot to add, that when viewed in Componet Services, the stubborn
transactions appear as "INSERTEXEC (aborting)". Don't know if it relevant...
"Stevo" wrote:

> Not 100% sure this is the right pace to post, but anyway...
> We're having some problems with MSDTC. I have servers running Windows 2003
> Server Standard Edition (no service packs) and each running SQL Server 200
0.
> We are using MSDTC to manage distributed transactions involving the
> databases on these servers. The application kicks of a distributed
> transaction using a class derived from ServiceComponent and then calls a
> number of SQL Stored Procedures on the 3 servers. These stored procedures
can
> access any of the 3 servers.
> Most of the time this is working fine, but we seem to be getting some
> intermittent problem. Looking in the MSDTC part of Componet Services, we'v
e
> noticed some transactions not resolving themselves after serveral hours. T
he
> only way we can seem to resolve them one way or another is to kill the SQL
> Server process associated with that transaction. In addition to this the s
ize
> of tempdb keeps growing and only reduces once we've killed the offending
> processes.
> How is it that MSDTC allows these transactions to hang around for so long?
>
>|||Probably because they are not committed nor aborted. Use the DTC tracing
facility in Windows Server 2003 in combination with SQL Profiler and you can
see the transaction conversation.
Or get a copy of AppMetrics for Transactions from ExtremeSoft
http://www.extremesoft.com/
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Stevo" <Stevo@.discussions.microsoft.com> wrote in message
news:19C771DC-D8A4-413A-A33E-E3F13C189FBE@.microsoft.com...
> Not 100% sure this is the right pace to post, but anyway...
> We're having some problems with MSDTC. I have servers running Windows 2003
> Server Standard Edition (no service packs) and each running SQL Server
> 2000.
> We are using MSDTC to manage distributed transactions involving the
> databases on these servers. The application kicks of a distributed
> transaction using a class derived from ServiceComponent and then calls a
> number of SQL Stored Procedures on the 3 servers. These stored procedures
> can
> access any of the 3 servers.
> Most of the time this is working fine, but we seem to be getting some
> intermittent problem. Looking in the MSDTC part of Componet Services,
> we've
> noticed some transactions not resolving themselves after serveral hours.
> The
> only way we can seem to resolve them one way or another is to kill the SQL
> Server process associated with that transaction. In addition to this the
> size
> of tempdb keeps growing and only reduces once we've killed the offending
> processes.
> How is it that MSDTC allows these transactions to hang around for so long?
>
>