deAttach database: standard

Showing posts with label standard. Show all posts

Thursday, March 8, 2012

Dead Lock

0x49C09530) Value:0x60540ac0 Cost

0/BC)
2006-04-12 10:57:05.31 spid4
2006-04-12 10:57:05.31 spid4 Node:2
2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:1 (b3016336158a)
CleanCnt:1 Mode: X Flags: 0x0
2006-04-12 10:57:05.31 spid4 Grant List 2::
2006-04-12 10:57:05.31 spid4 Owner:0x60541880 Mode: X Flg:0x0
Ref:0 Life:02000000 SPID:137 ECID:0
2006-04-12 10:57:05.31 spid4 SPID: 137 ECID: 0 Statement Type: UPDATE
Line #: 434
2006-04-12 10:57:05.31 spid4 Input Buf: RPC Event: sp_prepexec;1
2006-04-12 10:57:05.31 spid4 Requested By:
2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
SPID:528 ECID:0 Ec

0x7E0EB508) Value:0x675dfc20 Cost

0/0)
2006-04-12 10:57:05.31 spid4 Victim Resource Owner:
2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
SPID:528 ECID:0 Ec

0x7E0EB508) Value:0x675dfc20 Cost

0/0)
SPID 137 is updating the row which SPID 528 truying to access (This SP is
only selecting the rows no update) I specified the UPDLOCK lock hint in
update statment with no improvement.
Any help is appreciated.
--
Farhan"Farhan Soomro" <FarhanSoomro@.discussions.microsoft.com> wrote in message
news:E43DE237-5437-4BE0-AA3D-80B14FD67B9C@.microsoft.com...
> We are using SQLserver 2000 SP3 Standard Version. We are having dead lock
> and
> following is log about deadlock
> 2006-04-12 10:57:05.31 spid4 Wait-for graph
> 2006-04-12 10:57:05.31 spid4
> 2006-04-12 10:57:05.31 spid4 Node:1
> 2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:53 (480260485b26)
> CleanCnt:1 Mode: S Flags: 0x0
> 2006-04-12 10:57:05.31 spid4 Grant List 1::
> 2006-04-12 10:57:05.31 spid4 Owner:0x66a25520 Mode: S
> Flg:0x0
> Ref:0 Life:00000001 SPID:528 ECID:0
> 2006-04-12 10:57:05.31 spid4 SPID: 528 ECID: 0 Statement Type:
> SELECT
> Line #: 38
> 2006-04-12 10:57:05.31 spid4 Input Buf: Language Event: Exec
> dbo.VB_ConflictsAppointmentsByDate
> @.StartDate='04/12/2006',@.EndDate='04/12/2006',@.Discipline='',
> @.Location=,@.ResourceID='000150',@.S_Start
=156,@.S_End=168
> 2006-04-12 10:57:05.31 spid4 Requested By:
> 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: X
> SPID:137 ECID:0 Ec

0x49C09530) Value:0x60540ac0 Cost

0/BC)
> 2006-04-12 10:57:05.31 spid4
> 2006-04-12 10:57:05.31 spid4 Node:2
> 2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:1 (b3016336158a)
> CleanCnt:1 Mode: X Flags: 0x0
> 2006-04-12 10:57:05.31 spid4 Grant List 2::
> 2006-04-12 10:57:05.31 spid4 Owner:0x60541880 Mode: X
> Flg:0x0
> Ref:0 Life:02000000 SPID:137 ECID:0
> 2006-04-12 10:57:05.31 spid4 SPID: 137 ECID: 0 Statement Type:
> UPDATE
> Line #: 434
> 2006-04-12 10:57:05.31 spid4 Input Buf: RPC Event: sp_prepexec;1
> 2006-04-12 10:57:05.31 spid4 Requested By:
> 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
> SPID:528 ECID:0 Ec

0x7E0EB508) Value:0x675dfc20 Cost

0/0)
> 2006-04-12 10:57:05.31 spid4 Victim Resource Owner:
> 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
> SPID:528 ECID:0 Ec

0x7E0EB508) Value:0x675dfc20 Cost

0/0)
> SPID 137 is updating the row which SPID 528 truying to access (This SP is
> only selecting the rows no update) I specified the UPDLOCK lock hint in
> update statment with no improvement.
> Any help is appreciated.
> --
It's hard to suggest a change that resolves teh deadlock with minimal
degradation of concurrency or correctness without a complete picture of the
database structures, transactions and concurreny requirements of the
application.
However as a general matter, if you escalate the locks taken by one of the
transactions to a table lock, the deadlock should will go away. Again this
may cause an unacceptable degradation in the concurrency of the applciation.
Another aproach to simply optimize the SELECT. If it can read less, lock
less, or use a different index, etc you might resolve the deadlock and
improve appliction performance to boot.
David|||Thanks David.
I was thinking on same line, update sp is very complex and hard to adjust
versus select.
Appreciated.
--
Farhan
"David Browne" wrote:

> "Farhan Soomro" <FarhanSoomro@.discussions.microsoft.com> wrote in message
> news:E43DE237-5437-4BE0-AA3D-80B14FD67B9C@.microsoft.com...
> It's hard to suggest a change that resolves teh deadlock with minimal
> degradation of concurrency or correctness without a complete picture of th
e
> database structures, transactions and concurreny requirements of the
> application.
> However as a general matter, if you escalate the locks taken by one of the
> transactions to a table lock, the deadlock should will go away. Again th
is
> may cause an unacceptable degradation in the concurrency of the applciatio
n.
> Another aproach to simply optimize the SELECT. If it can read less, lock
> less, or use a different index, etc you might resolve the deadlock and
> improve appliction performance to boot.
> David
>
>

Dead Lock

We are using SQLserver 2000 SP3 Standard Version. We are having dead lock and
following is log about deadlock
2006-04-12 10:57:05.31 spid4 Wait-for graph
2006-04-12 10:57:05.31 spid4
2006-04-12 10:57:05.31 spid4 Node:1
2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:53 (480260485b26)
CleanCnt:1 Mode: S Flags: 0x0
2006-04-12 10:57:05.31 spid4 Grant List 1::
2006-04-12 10:57:05.31 spid4 Owner:0x66a25520 Mode: S Flg:0x0
Ref:0 Life:00000001 SPID:528 ECID:0
2006-04-12 10:57:05.31 spid4 SPID: 528 ECID: 0 Statement Type: SELECT
Line #: 38
2006-04-12 10:57:05.31 spid4 Input Buf: Language Event: Exec
dbo.VB_ConflictsAppointmentsByDate
@.StartDate='04/12/2006',@.EndDate='04/12/2006',@.Discipline='',
@.Location=,@.ResourceID='000150',@.S_Start=156,@.S_End=168
2006-04-12 10:57:05.31 spid4 Requested By:
2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: X
SPID:137 ECID:0 Ec:(0x49C09530) Value:0x60540ac0 Cost:(0/BC)
2006-04-12 10:57:05.31 spid4
2006-04-12 10:57:05.31 spid4 Node:2
2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:1 (b3016336158a)
CleanCnt:1 Mode: X Flags: 0x0
2006-04-12 10:57:05.31 spid4 Grant List 2::
2006-04-12 10:57:05.31 spid4 Owner:0x60541880 Mode: X Flg:0x0
Ref:0 Life:02000000 SPID:137 ECID:0
2006-04-12 10:57:05.31 spid4 SPID: 137 ECID: 0 Statement Type: UPDATE
Line #: 434
2006-04-12 10:57:05.31 spid4 Input Buf: RPC Event: sp_prepexec;1
2006-04-12 10:57:05.31 spid4 Requested By:
2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
SPID:528 ECID:0 Ec:(0x7E0EB508) Value:0x675dfc20 Cost:(0/0)
2006-04-12 10:57:05.31 spid4 Victim Resource Owner:
2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
SPID:528 ECID:0 Ec:(0x7E0EB508) Value:0x675dfc20 Cost:(0/0)
SPID 137 is updating the row which SPID 528 truying to access (This SP is
only selecting the rows no update) I specified the UPDLOCK lock hint in
update statment with no improvement.
Any help is appreciated.
--
Farhan"Farhan Soomro" <FarhanSoomro@.discussions.microsoft.com> wrote in message
news:E43DE237-5437-4BE0-AA3D-80B14FD67B9C@.microsoft.com...
> We are using SQLserver 2000 SP3 Standard Version. We are having dead lock
> and
> following is log about deadlock
> 2006-04-12 10:57:05.31 spid4 Wait-for graph
> 2006-04-12 10:57:05.31 spid4
> 2006-04-12 10:57:05.31 spid4 Node:1
> 2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:53 (480260485b26)
> CleanCnt:1 Mode: S Flags: 0x0
> 2006-04-12 10:57:05.31 spid4 Grant List 1::
> 2006-04-12 10:57:05.31 spid4 Owner:0x66a25520 Mode: S
> Flg:0x0
> Ref:0 Life:00000001 SPID:528 ECID:0
> 2006-04-12 10:57:05.31 spid4 SPID: 528 ECID: 0 Statement Type:
> SELECT
> Line #: 38
> 2006-04-12 10:57:05.31 spid4 Input Buf: Language Event: Exec
> dbo.VB_ConflictsAppointmentsByDate
> @.StartDate='04/12/2006',@.EndDate='04/12/2006',@.Discipline='',
> @.Location=,@.ResourceID='000150',@.S_Start=156,@.S_End=168
> 2006-04-12 10:57:05.31 spid4 Requested By:
> 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: X
> SPID:137 ECID:0 Ec:(0x49C09530) Value:0x60540ac0 Cost:(0/BC)
> 2006-04-12 10:57:05.31 spid4
> 2006-04-12 10:57:05.31 spid4 Node:2
> 2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:1 (b3016336158a)
> CleanCnt:1 Mode: X Flags: 0x0
> 2006-04-12 10:57:05.31 spid4 Grant List 2::
> 2006-04-12 10:57:05.31 spid4 Owner:0x60541880 Mode: X
> Flg:0x0
> Ref:0 Life:02000000 SPID:137 ECID:0
> 2006-04-12 10:57:05.31 spid4 SPID: 137 ECID: 0 Statement Type:
> UPDATE
> Line #: 434
> 2006-04-12 10:57:05.31 spid4 Input Buf: RPC Event: sp_prepexec;1
> 2006-04-12 10:57:05.31 spid4 Requested By:
> 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
> SPID:528 ECID:0 Ec:(0x7E0EB508) Value:0x675dfc20 Cost:(0/0)
> 2006-04-12 10:57:05.31 spid4 Victim Resource Owner:
> 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
> SPID:528 ECID:0 Ec:(0x7E0EB508) Value:0x675dfc20 Cost:(0/0)
> SPID 137 is updating the row which SPID 528 truying to access (This SP is
> only selecting the rows no update) I specified the UPDLOCK lock hint in
> update statment with no improvement.
> Any help is appreciated.
> --
It's hard to suggest a change that resolves teh deadlock with minimal
degradation of concurrency or correctness without a complete picture of the
database structures, transactions and concurreny requirements of the
application.
However as a general matter, if you escalate the locks taken by one of the
transactions to a table lock, the deadlock should will go away. Again this
may cause an unacceptable degradation in the concurrency of the applciation.
Another aproach to simply optimize the SELECT. If it can read less, lock
less, or use a different index, etc you might resolve the deadlock and
improve appliction performance to boot.
David|||Thanks David.
I was thinking on same line, update sp is very complex and hard to adjust
versus select.
Appreciated.
--
Farhan
"David Browne" wrote:
> "Farhan Soomro" <FarhanSoomro@.discussions.microsoft.com> wrote in message
> news:E43DE237-5437-4BE0-AA3D-80B14FD67B9C@.microsoft.com...
> > We are using SQLserver 2000 SP3 Standard Version. We are having dead lock
> > and
> > following is log about deadlock
> >
> > 2006-04-12 10:57:05.31 spid4 Wait-for graph
> > 2006-04-12 10:57:05.31 spid4
> > 2006-04-12 10:57:05.31 spid4 Node:1
> > 2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:53 (480260485b26)
> > CleanCnt:1 Mode: S Flags: 0x0
> > 2006-04-12 10:57:05.31 spid4 Grant List 1::
> > 2006-04-12 10:57:05.31 spid4 Owner:0x66a25520 Mode: S
> > Flg:0x0
> > Ref:0 Life:00000001 SPID:528 ECID:0
> > 2006-04-12 10:57:05.31 spid4 SPID: 528 ECID: 0 Statement Type:
> > SELECT
> > Line #: 38
> > 2006-04-12 10:57:05.31 spid4 Input Buf: Language Event: Exec
> > dbo.VB_ConflictsAppointmentsByDate
> > @.StartDate='04/12/2006',@.EndDate='04/12/2006',@.Discipline='',
> > @.Location=,@.ResourceID='000150',@.S_Start=156,@.S_End=168
> > 2006-04-12 10:57:05.31 spid4 Requested By:
> > 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: X
> > SPID:137 ECID:0 Ec:(0x49C09530) Value:0x60540ac0 Cost:(0/BC)
> > 2006-04-12 10:57:05.31 spid4
> > 2006-04-12 10:57:05.31 spid4 Node:2
> > 2006-04-12 10:57:05.31 spid4 KEY: 8:1221032277:1 (b3016336158a)
> > CleanCnt:1 Mode: X Flags: 0x0
> > 2006-04-12 10:57:05.31 spid4 Grant List 2::
> > 2006-04-12 10:57:05.31 spid4 Owner:0x60541880 Mode: X
> > Flg:0x0
> > Ref:0 Life:02000000 SPID:137 ECID:0
> > 2006-04-12 10:57:05.31 spid4 SPID: 137 ECID: 0 Statement Type:
> > UPDATE
> > Line #: 434
> > 2006-04-12 10:57:05.31 spid4 Input Buf: RPC Event: sp_prepexec;1
> > 2006-04-12 10:57:05.31 spid4 Requested By:
> > 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
> > SPID:528 ECID:0 Ec:(0x7E0EB508) Value:0x675dfc20 Cost:(0/0)
> > 2006-04-12 10:57:05.31 spid4 Victim Resource Owner:
> > 2006-04-12 10:57:05.31 spid4 ResType:LockOwner Stype:'OR' Mode: S
> > SPID:528 ECID:0 Ec:(0x7E0EB508) Value:0x675dfc20 Cost:(0/0)
> >
> > SPID 137 is updating the row which SPID 528 truying to access (This SP is
> > only selecting the rows no update) I specified the UPDLOCK lock hint in
> > update statment with no improvement.
> > Any help is appreciated.
> > --
> It's hard to suggest a change that resolves teh deadlock with minimal
> degradation of concurrency or correctness without a complete picture of the
> database structures, transactions and concurreny requirements of the
> application.
> However as a general matter, if you escalate the locks taken by one of the
> transactions to a table lock, the deadlock should will go away. Again this
> may cause an unacceptable degradation in the concurrency of the applciation.
> Another aproach to simply optimize the SELECT. If it can read less, lock
> less, or use a different index, etc you might resolve the deadlock and
> improve appliction performance to boot.
> David
>
>

Wednesday, March 7, 2012

DCOM Error, Event ID 10016, DTS Server

Hi all,
I have a new SQL Server 2005 Standard SP2 install with just database
services and workstation components installed.
I've noticed the following system event error that appears twice each
time a maintenance task runs (the maintenance tasks do run
successfully):
--
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 20/12/2007
Time: 11:00:00
User: [domain sql agent account]
Computer: [server name]
Description:
The application-specific permission settings do not grant Local Launch
permission for the COM Server application with CLSID
{SID}
to the user [domain sql agent account] SID (SID). This security
permission can be modified using the Component Services administrative
tool.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
I've matched the CLSID given in the error to an entry an entry in the
registry that identifies Microsoft.SqlServer.Dts.Server.DtsServer. In
Component Services, there's a MsDtsServer listed under DCOM config.
Giving the domain sql agent account Local Launch access to this sorts
the error.
I'm a bit confused about this and am tempted to rebuild the server,
but would obviously like to avoid that if possible. I don't have SSIS
installed, so I don't understand why DTS is being used. I'd rather not
have an unnecessary service running, but I also don't want errors
showing up in the event log.
Any idea why this is happening? Does DTS need to be running even
though SSIS isn't installed? Any insight/suggestions are appreciated.
Regards.Hi
Have you checked out http://support.microsoft.com/kb/931355/en-us
John
"RJGiskard" wrote:
> Hi all,
> I have a new SQL Server 2005 Standard SP2 install with just database
> services and workstation components installed.
> I've noticed the following system event error that appears twice each
> time a maintenance task runs (the maintenance tasks do run
> successfully):
> --
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10016
> Date: 20/12/2007
> Time: 11:00:00
> User: [domain sql agent account]
> Computer: [server name]
> Description:
> The application-specific permission settings do not grant Local Launch
> permission for the COM Server application with CLSID
> {SID}
> to the user [domain sql agent account] SID (SID). This security
> permission can be modified using the Component Services administrative
> tool.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> --
> I've matched the CLSID given in the error to an entry an entry in the
> registry that identifies Microsoft.SqlServer.Dts.Server.DtsServer. In
> Component Services, there's a MsDtsServer listed under DCOM config.
> Giving the domain sql agent account Local Launch access to this sorts
> the error.
> I'm a bit confused about this and am tempted to rebuild the server,
> but would obviously like to avoid that if possible. I don't have SSIS
> installed, so I don't understand why DTS is being used. I'd rather not
> have an unnecessary service running, but I also don't want errors
> showing up in the event log.
> Any idea why this is happening? Does DTS need to be running even
> though SSIS isn't installed? Any insight/suggestions are appreciated.
> Regards.
>|||On 20 Dec, 16:41, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Have you checked outhttp://support.microsoft.com/kb/931355/en-us
No, hadn't found that one. We are running SP2 on the W2K3 server, but
I gave that a go. I reveresed the changes I made earlier, tried the
changes suggested, but still get the error.
So is DTS required even though I don't have SSIS isn't installed? I
thought SSIS was the SQL Server 2005 replacement for DTS and that this
DTS Server was just a legacy naming thing but that it's actually SSIS.|||Hi
DTS is still the name behind the scenes.
I think Maintenance plans will use SSIS components, you could replace them
with the T-SQL scripts that do the equivalent tasks if you are using
Maintenance tasks.
John
"RJGiskard" wrote:
> On 20 Dec, 16:41, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > Have you checked outhttp://support.microsoft.com/kb/931355/en-us
> No, hadn't found that one. We are running SP2 on the W2K3 server, but
> I gave that a go. I reveresed the changes I made earlier, tried the
> changes suggested, but still get the error.
> So is DTS required even though I don't have SSIS isn't installed? I
> thought SSIS was the SQL Server 2005 replacement for DTS and that this
> DTS Server was just a legacy naming thing but that it's actually SSIS.
>

DCOM Error, Event ID 10016, DTS Server

Hi all,
I have a new SQL Server 2005 Standard SP2 install with just database
services and workstation components installed.
I've noticed the following system event error that appears twice each
time a maintenance task runs (the maintenance tasks do run
successfully):
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 20/12/2007
Time: 11:00:00
User: [domain sql agent account]
Computer: [server name]
Description:
The application-specific permission settings do not grant Local Launch
permission for the COM Server application with CLSID
{SID}
to the user [domain sql agent account] SID (SID). This security
permission can be modified using the Component Services administrative
tool.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
I've matched the CLSID given in the error to an entry an entry in the
registry that identifies Microsoft.SqlServer.Dts.Server.DtsServer. In
Component Services, there's a MsDtsServer listed under DCOM config.
Giving the domain sql agent account Local Launch access to this sorts
the error.
I'm a bit confused about this and am tempted to rebuild the server,
but would obviously like to avoid that if possible. I don't have SSIS
installed, so I don't understand why DTS is being used. I'd rather not
have an unnecessary service running, but I also don't want errors
showing up in the event log.
Any idea why this is happening? Does DTS need to be running even
though SSIS isn't installed? Any insight/suggestions are appreciated.
Regards.Hi
Have you checked out http://support.microsoft.com/kb/931355/en-us
John
"RJGiskard" wrote:

> Hi all,
> I have a new SQL Server 2005 Standard SP2 install with just database
> services and workstation components installed.
> I've noticed the following system event error that appears twice each
> time a maintenance task runs (the maintenance tasks do run
> successfully):
> --
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10016
> Date: 20/12/2007
> Time: 11:00:00
> User: [domain sql agent account]
> Computer: [server name]
> Description:
> The application-specific permission settings do not grant Local Launch
> permission for the COM Server application with CLSID
> {SID}
> to the user [domain sql agent account] SID (SID). This security
> permission can be modified using the Component Services administrative
> tool.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> --
> I've matched the CLSID given in the error to an entry an entry in the
> registry that identifies Microsoft.SqlServer.Dts.Server.DtsServer. In
> Component Services, there's a MsDtsServer listed under DCOM config.
> Giving the domain sql agent account Local Launch access to this sorts
> the error.
> I'm a bit confused about this and am tempted to rebuild the server,
> but would obviously like to avoid that if possible. I don't have SSIS
> installed, so I don't understand why DTS is being used. I'd rather not
> have an unnecessary service running, but I also don't want errors
> showing up in the event log.
> Any idea why this is happening? Does DTS need to be running even
> though SSIS isn't installed? Any insight/suggestions are appreciated.
> Regards.
>|||On 20 Dec, 16:41, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Have you checked outhttp://support.microsoft.com/kb/931355/en-us
No, hadn't found that one. We are running SP2 on the W2K3 server, but
I gave that a go. I reveresed the changes I made earlier, tried the
changes suggested, but still get the error.
So is DTS required even though I don't have SSIS isn't installed? I
thought SSIS was the SQL Server 2005 replacement for DTS and that this
DTS Server was just a legacy naming thing but that it's actually SSIS.|||Hi
DTS is still the name behind the scenes.
I think Maintenance plans will use SSIS components, you could replace them
with the T-SQL scripts that do the equivalent tasks if you are using
Maintenance tasks.
John
"RJGiskard" wrote:

> On 20 Dec, 16:41, John Bell <jbellnewspo...@.hotmail.com> wrote:
> No, hadn't found that one. We are running SP2 on the W2K3 server, but
> I gave that a go. I reveresed the changes I made earlier, tried the
> changes suggested, but still get the error.
> So is DTS required even though I don't have SSIS isn't installed? I
> thought SSIS was the SQL Server 2005 replacement for DTS and that this
> DTS Server was just a legacy naming thing but that it's actually SSIS.
>

Thursday, March 8, 2012

Dead Lock

Dead Lock

Wednesday, March 7, 2012

DCOM Error, Event ID 10016, DTS Server

DCOM Error, Event ID 10016, DTS Server

deAttach database

Blog Archive

About Me