I have a quick question, I have a production sql server 2005 box and one of
the client is having problem to access the one of our application module and
I want to debug the problem but i don't want to hurt production database
peformance, is there any way how I can fulfill this, is there any other
approach which I can taken place in real time enviornment.

Thanks

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote:

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote:

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote:

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote:

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote:

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote:

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote:

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote:

There is almost always a way to find what a problem may be without hurting a
production system. But you may want to be a bit more specific about the
nature of your problem. Can you elaborate on what you meant by 'having
problem to access the one of our application module'? Did the client have a
problem accessing SQL Server? Any error message from SQL Server?

Linchi

"Smith" wrote: