Hello
we having SQL 2000 Ent in cluster enviornment (in SAN), now we are facing
dead lock issues.
any idea?
Regards
Gopi
Have you enabled
DBCC TRACEON (1204) ?
"Gopi" <gopi2it@.gmail.com> wrote in message
news:ett4icSeIHA.3940@.TK2MSFTNGP05.phx.gbl...
> Hello
> we having SQL 2000 Ent in cluster enviornment (in SAN), now we are facing
> dead lock issues.
> any idea?
> Regards
> Gopi
>
|||adding, error message.
Message
Save Profile Failed Transaction (Process ID 75) was deadlocked on lock
resources with another process and has been chosen as the deadlock victim.
Rerun the transaction.
Source
MicroClear.EnterpriseSolutions.DataProfileServices
Stack Trace
at
MicroClear.EnterpriseSolutions.DataProfileServices .ProfileService.SaveProfileFromXmlDocument(XmlDocu ment
profileDocument, ArrayList updateOtherProfiles, Boolean insertNotExist,
ProfileParam[] updateProfiles, String MainProfileFieldsList, Boolean
byPassSecurity) at
MicroClear.EnterpriseSolutions.Web.Services.Action Services.Actor.ProfileHelpers.SaveProfile(ArrayLis t
updateOtherProfiles, Boolean insertNotExist) at
MicroClear.Actors.eFormsAdmin.AdmSubmitRequest.New SetFlag() in
c:\eForms\Actors\eFormsAdmin\AdmSubmitRequest.cs:l ine 2528
Base Exception
Int32 SaveProfileFromXmlDocument(System.Xml.XmlDocument,
System.Collections.ArrayList, Boolean,
MicroClear.EnterpriseSolutions.DataProfileServices .ProfileParam[],
System.String, Boolean)
Actor
SetFlag_2
Module
SubmissionService
Framework Msg
"Gopi" <gopi2it@.gmail.com> wrote in message
news:ett4icSeIHA.3940@.TK2MSFTNGP05.phx.gbl...
> Hello
> we having SQL 2000 Ent in cluster enviornment (in SAN), now we are facing
> dead lock issues.
> any idea?
> Regards
> Gopi
>
|||No, we didnt trace but using SQL profiler, trying to identify.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uTBqxeSeIHA.4684@.TK2MSFTNGP06.phx.gbl...
> Have you enabled
> DBCC TRACEON (1204) ?
> "Gopi" <gopi2it@.gmail.com> wrote in message
> news:ett4icSeIHA.3940@.TK2MSFTNGP05.phx.gbl...
>
|||Gopi
http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/tracingdeadlocks/1324/
"Gopi" <gopi2it@.gmail.com> wrote in message
news:eH$LooSeIHA.3756@.TK2MSFTNGP06.phx.gbl...
> No, we didnt trace but using SQL profiler, trying to identify.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:uTBqxeSeIHA.4684@.TK2MSFTNGP06.phx.gbl...
>
Showing posts with label hellowe. Show all posts
Showing posts with label hellowe. Show all posts
Sunday, March 11, 2012
Tuesday, February 14, 2012
DB-Library and sp_dbcmptlevel in Sql Server 2005
Hello!
We are currently running SQL Server 7.0 with databases in 6.5-compatibility
mode for DB-Library.
- Will this still be supported in Sql Server 2005?
- If so, any changes in behaviour?
- What new features will we be "missing out of" by continuing with the above
setup (db-lib + 6.5-mode) also in Sql Server 2005?
- Any future plans of dropping the support for DB-Lib with Sql Server?
ThanxAFAIK, the dblib interface will be supported in the next version of sql
server. MS has indicated that they do intend to stop supporting it but they
have not announced when. MS has indicated that the dblib api is
feature-frozen and will not be enhanced to take advantage of any new
features introduced after sql server version 6.5.
The most important feature that dblib does not support is char columns > 255
characters. Beyond that, I don't know of any particular features that
cannot be accessed. It is NOT necessary to set the database into 6.5
compatibility mode when using the dblib interface; you may want to review
the process that lead you to this decision. BOL has a section that
discusses the changes between the most current versions of sql server - that
is what you are missing out of by setting the compatibility mode.
"Tomas" <Tomas@.discussions.microsoft.com> wrote in message
news:8694521C-0379-4B00-A5C0-36A98CE63191@.microsoft.com...
> Hello!
> We are currently running SQL Server 7.0 with databases in
6.5-compatibility
> mode for DB-Library.
> - Will this still be supported in Sql Server 2005?
> - If so, any changes in behaviour?
> - What new features will we be "missing out of" by continuing with the
above
> setup (db-lib + 6.5-mode) also in Sql Server 2005?
> - Any future plans of dropping the support for DB-Lib with Sql Server?
> Thanx|||SEE
http://msdn.microsoft.com/library/d...y/en-us/dnmdac/
html/data_mdacroadmap.asp
DB-Library: This is a SQL Server-specific programming model that
includes C APIs. There have been no feature enhancements to the
DB-Library since SQL Server 6.5. Its final release was with SQL Server
2000 and it will not be ported to the 64-bit Windows operating system.
Tim S
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
We are currently running SQL Server 7.0 with databases in 6.5-compatibility
mode for DB-Library.
- Will this still be supported in Sql Server 2005?
- If so, any changes in behaviour?
- What new features will we be "missing out of" by continuing with the above
setup (db-lib + 6.5-mode) also in Sql Server 2005?
- Any future plans of dropping the support for DB-Lib with Sql Server?
ThanxAFAIK, the dblib interface will be supported in the next version of sql
server. MS has indicated that they do intend to stop supporting it but they
have not announced when. MS has indicated that the dblib api is
feature-frozen and will not be enhanced to take advantage of any new
features introduced after sql server version 6.5.
The most important feature that dblib does not support is char columns > 255
characters. Beyond that, I don't know of any particular features that
cannot be accessed. It is NOT necessary to set the database into 6.5
compatibility mode when using the dblib interface; you may want to review
the process that lead you to this decision. BOL has a section that
discusses the changes between the most current versions of sql server - that
is what you are missing out of by setting the compatibility mode.
"Tomas" <Tomas@.discussions.microsoft.com> wrote in message
news:8694521C-0379-4B00-A5C0-36A98CE63191@.microsoft.com...
> Hello!
> We are currently running SQL Server 7.0 with databases in
6.5-compatibility
> mode for DB-Library.
> - Will this still be supported in Sql Server 2005?
> - If so, any changes in behaviour?
> - What new features will we be "missing out of" by continuing with the
above
> setup (db-lib + 6.5-mode) also in Sql Server 2005?
> - Any future plans of dropping the support for DB-Lib with Sql Server?
> Thanx|||SEE
http://msdn.microsoft.com/library/d...y/en-us/dnmdac/
html/data_mdacroadmap.asp
DB-Library: This is a SQL Server-specific programming model that
includes C APIs. There have been no feature enhancements to the
DB-Library since SQL Server 6.5. Its final release was with SQL Server
2000 and it will not be ported to the 64-bit Windows operating system.
Tim S
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
DB-Library and sp_dbcmptlevel in Sql Server 2005
Hello!
We are currently running SQL Server 7.0 with databases in 6.5-compatibility
mode for DB-Library.
- Will this still be supported in Sql Server 2005?
- If so, any changes in behaviour?
- What new features will we be "missing out of" by continuing with the above
setup (db-lib + 6.5-mode) also in Sql Server 2005?
- Any future plans of dropping the support for DB-Lib with Sql Server?
Thanx
AFAIK, the dblib interface will be supported in the next version of sql
server. MS has indicated that they do intend to stop supporting it but they
have not announced when. MS has indicated that the dblib api is
feature-frozen and will not be enhanced to take advantage of any new
features introduced after sql server version 6.5.
The most important feature that dblib does not support is char columns > 255
characters. Beyond that, I don't know of any particular features that
cannot be accessed. It is NOT necessary to set the database into 6.5
compatibility mode when using the dblib interface; you may want to review
the process that lead you to this decision. BOL has a section that
discusses the changes between the most current versions of sql server - that
is what you are missing out of by setting the compatibility mode.
"Tomas" <Tomas@.discussions.microsoft.com> wrote in message
news:8694521C-0379-4B00-A5C0-36A98CE63191@.microsoft.com...
> Hello!
> We are currently running SQL Server 7.0 with databases in
6.5-compatibility
> mode for DB-Library.
> - Will this still be supported in Sql Server 2005?
> - If so, any changes in behaviour?
> - What new features will we be "missing out of" by continuing with the
above
> setup (db-lib + 6.5-mode) also in Sql Server 2005?
> - Any future plans of dropping the support for DB-Lib with Sql Server?
> Thanx
|||SEE
http://msdn.microsoft.com/library/de.../en-us/dnmdac/
html/data_mdacroadmap.asp
DB-Library: This is a SQL Server-specific programming model that
includes C APIs. There have been no feature enhancements to the
DB-Library since SQL Server 6.5. Its final release was with SQL Server
2000 and it will not be ported to the 64-bit Windows operating system.
Tim S
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
We are currently running SQL Server 7.0 with databases in 6.5-compatibility
mode for DB-Library.
- Will this still be supported in Sql Server 2005?
- If so, any changes in behaviour?
- What new features will we be "missing out of" by continuing with the above
setup (db-lib + 6.5-mode) also in Sql Server 2005?
- Any future plans of dropping the support for DB-Lib with Sql Server?
Thanx
AFAIK, the dblib interface will be supported in the next version of sql
server. MS has indicated that they do intend to stop supporting it but they
have not announced when. MS has indicated that the dblib api is
feature-frozen and will not be enhanced to take advantage of any new
features introduced after sql server version 6.5.
The most important feature that dblib does not support is char columns > 255
characters. Beyond that, I don't know of any particular features that
cannot be accessed. It is NOT necessary to set the database into 6.5
compatibility mode when using the dblib interface; you may want to review
the process that lead you to this decision. BOL has a section that
discusses the changes between the most current versions of sql server - that
is what you are missing out of by setting the compatibility mode.
"Tomas" <Tomas@.discussions.microsoft.com> wrote in message
news:8694521C-0379-4B00-A5C0-36A98CE63191@.microsoft.com...
> Hello!
> We are currently running SQL Server 7.0 with databases in
6.5-compatibility
> mode for DB-Library.
> - Will this still be supported in Sql Server 2005?
> - If so, any changes in behaviour?
> - What new features will we be "missing out of" by continuing with the
above
> setup (db-lib + 6.5-mode) also in Sql Server 2005?
> - Any future plans of dropping the support for DB-Lib with Sql Server?
> Thanx
|||SEE
http://msdn.microsoft.com/library/de.../en-us/dnmdac/
html/data_mdacroadmap.asp
DB-Library: This is a SQL Server-specific programming model that
includes C APIs. There have been no feature enhancements to the
DB-Library since SQL Server 6.5. Its final release was with SQL Server
2000 and it will not be ported to the 64-bit Windows operating system.
Tim S
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Subscribe to:
Posts (Atom)