Deadlock Issue

Hi ,
I always face the Deadlock issue in our production DB.We are not running any
Profiler nor any the Error Flag is set ON.The job fails and we trace the LOG
file to check the error. We are not supposed to run any of these.Is there an
y
way to check the DEADLOCK Issue after it has occured,such as to Trace back
the issue.Like, from the SQL Mgmt option from Ent Manager,or SQL Server LOGs
or any other option.
KINDLY HELP ME ON THIS ASAP!
Thanks in advance.
Regards,
ShyamIf you haven't set anything up to capture the deadlock info, I'm afraid ther
e
is not much you can do to analyze the deadlocks that already took place. One
of the most effective ways to capture and analyze deadlocks is set up trace
falg 1204 at startup (i.e. add -T1204 as a startup parameter from Enterprise
Manager).

> We are not supposed to run any of these.
Well, I'm not sure who set the rule. But if you are expected to solve
problems, you've got to have access to proper tools.
Linchi
"Shyam" wrote:

> Hi ,
> I always face the Deadlock issue in our production DB.We are not running a
ny
> Profiler nor any the Error Flag is set ON.The job fails and we trace the L
OG
> file to check the error. We are not supposed to run any of these.Is there
any
> way to check the DEADLOCK Issue after it has occured,such as to Trace back
> the issue.Like, from the SQL Mgmt option from Ent Manager,or SQL Server LO
Gs
> or any other option.
> KINDLY HELP ME ON THIS ASAP!
> Thanks in advance.
> Regards,
> Shyam

Deadlock Issue

Hi ,
I always face the Deadlock issue in our production DB.We are not running any
Profiler nor any the Error Flag is set ON.The job fails and we trace the LOG
file to check the error. We are not supposed to run any of these.Is there any
way to check the DEADLOCK Issue after it has occured,such as to Trace back
the issue.Like, from the SQL Mgmt option from Ent Manager,or SQL Server LOGs
or any other option.
KINDLY HELP ME ON THIS ASAP!
Thanks in advance.
Regards,
ShyamIf you haven't set anything up to capture the deadlock info, I'm afraid there
is not much you can do to analyze the deadlocks that already took place. One
of the most effective ways to capture and analyze deadlocks is set up trace
falg 1204 at startup (i.e. add -T1204 as a startup parameter from Enterprise
Manager).
> We are not supposed to run any of these.
Well, I'm not sure who set the rule. But if you are expected to solve
problems, you've got to have access to proper tools.
Linchi
"Shyam" wrote:
> Hi ,
> I always face the Deadlock issue in our production DB.We are not running any
> Profiler nor any the Error Flag is set ON.The job fails and we trace the LOG
> file to check the error. We are not supposed to run any of these.Is there any
> way to check the DEADLOCK Issue after it has occured,such as to Trace back
> the issue.Like, from the SQL Mgmt option from Ent Manager,or SQL Server LOGs
> or any other option.
> KINDLY HELP ME ON THIS ASAP!
> Thanks in advance.
> Regards,
> Shyam

dbo prefix

When I try to do a remote query as follow
select * from server1.retail..customers
the query fails, but if ran the same query with dbo
select * from server1.retail.dbo.customers, then it works.
Why is this happening, I thought dbo. or .. was the same.
Thanks in advanceTom,
>> Why is this happening, I thought dbo. or .. was the same.
No.If you login to SQL Server using the login 'tom' and then you say select
* from server1.retail..customers, it looks for 'customers' which is created
by the objectowner 'tom'.Normally, all database objects should be created by
'dbo' in order to avoid this confusion.Even otherwise, its a good practice
to prefix the objectowner name explicitly as in select * from dbo.customers.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"tom" <tom@.hotmail.com> wrote in message
news:0d9401c36e47$15161d10$a501280a@.phx.gbl...
> When I try to do a remote query as follow
> select * from server1.retail..customers
> the query fails, but if ran the same query with dbo
> select * from server1.retail.dbo.customers, then it works.
> Why is this happening, I thought dbo. or .. was the same.
> Thanks in advance
>|||I am sa on the server and all the objects are owned by dbo.
thanks for you help
>--Original Message--
>Tom,
>> Why is this happening, I thought dbo. or .. was the
same.
>No.If you login to SQL Server using the login 'tom' and
then you say select
>* from server1.retail..customers, it looks
for 'customers' which is created
>by the objectowner 'tom'.Normally, all database objects
should be created by
>'dbo' in order to avoid this confusion.Even otherwise,
its a good practice
>to prefix the objectowner name explicitly as in select *
from dbo.customers.
>--
>Dinesh.
>SQL Server FAQ at
>http://www.tkdinesh.com
>"tom" <tom@.hotmail.com> wrote in message
>news:0d9401c36e47$15161d10$a501280a@.phx.gbl...
>> When I try to do a remote query as follow
>> select * from server1.retail..customers
>> the query fails, but if ran the same query with dbo
>> select * from server1.retail.dbo.customers, then it
works.
>> Why is this happening, I thought dbo. or .. was the
same.
>> Thanks in advance
>>
>
>.
>|||Tom,
Its because you are querying a remote server.Always use fully qualified
names when working with objects on linked servers including the object owner
name,in this case, 'dbo'.In linked servers, there is no support for implicit
resolution of .. to the dbo owner name for tables .
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"tom" <tom@.hotmail.com> wrote in message
news:011e01c36e49$c1123610$a301280a@.phx.gbl...
> I am sa on the server and all the objects are owned by dbo.
> thanks for you help
>
> >--Original Message--
> >Tom,
> >
> >> Why is this happening, I thought dbo. or .. was the
> same.
> >
> >No.If you login to SQL Server using the login 'tom' and
> then you say select
> >* from server1.retail..customers, it looks
> for 'customers' which is created
> >by the objectowner 'tom'.Normally, all database objects
> should be created by
> >'dbo' in order to avoid this confusion.Even otherwise,
> its a good practice
> >to prefix the objectowner name explicitly as in select *
> from dbo.customers.
> >
> >--
> >Dinesh.
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"tom" <tom@.hotmail.com> wrote in message
> >news:0d9401c36e47$15161d10$a501280a@.phx.gbl...
> >> When I try to do a remote query as follow
> >>
> >> select * from server1.retail..customers
> >>
> >> the query fails, but if ran the same query with dbo
> >>
> >> select * from server1.retail.dbo.customers, then it
> works.
> >>
> >> Why is this happening, I thought dbo. or .. was the
> same.
> >>
> >> Thanks in advance
> >>
> >>
> >
> >
> >.
> >