performance

#11

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:

Quote:

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

#12

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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

#13

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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

#14

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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

#15

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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

#16

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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

#17

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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

#18

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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

#19

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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

#20

This is just a general question if the cilent is having database any object
problem and we don't want to touch production box, is there any way we can
produce the database problem to point on another box which is a snapshort of
primary database or any other solution which doesn't point the production
server, hope you understand what I am trying to say.

Thanks

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote

Quote:

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:

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