morechocolate
Technical User
I do not if anyone can shed light on this, but we have a stored procedure that runs fine, pershaps about 2 minutes, on our production server. However, when that same stored procedure is run on a different server, one that is to become our production server, the stored procedure seems to just sit there, running for hours. So far the programmer has not even let it finish it has taken so long.
The DBA says he has verfied that the settings are the same in both environments. They (the DBA and the programmer) are now thinking that underlying processes that our vendor has set up for their programming is causing the problem. I really do not know. I just think it is odd that the same exact stored procedure is taking so long to run.
Any thoughts? Sorry I cannot give anymore information than that.
Oh - the stored procedure is using the old ANSI standard for outer joins (don't ask), but I would not think that would cause a problem.
Thanks
The DBA says he has verfied that the settings are the same in both environments. They (the DBA and the programmer) are now thinking that underlying processes that our vendor has set up for their programming is causing the problem. I really do not know. I just think it is odd that the same exact stored procedure is taking so long to run.
Any thoughts? Sorry I cannot give anymore information than that.
Oh - the stored procedure is using the old ANSI standard for outer joins (don't ask), but I would not think that would cause a problem.
Thanks