July 27, 2012 at 7:07 am
Doubt it.
Not handling the error in sQL does not mean you're ignoring it. It means SQL throws the error to the application. Hence you should see the error in the app. However that is not an error from SQL. I suggest you debug the app first.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 30, 2012 at 1:30 am
Hi ,
I have seen an article regarding transaction Isolation.. may be the same is happening in this case and I have also found that "SET TRANSACTION" would also set to one of the isolation levels.
I am thinking to use the same and set the transaction to "Serializable" so that dirty read, non repeated read issues can be eliminated.
COuld you help me how i can set a particuralar transaction isolation level to "Serializable".
July 30, 2012 at 2:14 am
Books Online: Transaction Isolation Level
Be sure to read up on the downsides of it too.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 1, 2012 at 2:26 am
I have modified my process in the application to recall for one time if it got failed for this specific error (50000) and now it is all set . Juntwanted to update you.
Thank you all very much for your help and time in this case...
Regards,
Mohan
April 2, 2015 at 7:01 am
Hi Grasshopper,
Did you get the answer for this question. Because I am facing the same problem .If got the answer, please let me know
Thank you
sandy
April 2, 2015 at 7:06 am
sandeep1553 (4/2/2015)
Did you get the answer for this question. Because I am facing the same problem .If got the answer, please let me know
Error 50000 is a user-defined error. It means that somewhere in the procedure there's a RAISERROR command which is raising a user-defined error. It's not something that there's a generic solution to, you need to look at your procedure and see why the RAISERROR command is run.
It is not system-generated, it is not something that someone unfamiliar with your code can answer.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 2, 2015 at 7:59 am
sandeep1553 (4/2/2015)
Hi Grasshopper,Did you get the answer for this question. Because I am facing the same problem .If got the answer, please let me know
Thank you
sandy
look in your code for RAISERROR
that is where the error is generated, and what you need to concentrate on, i think.
RAISERROR('Obscure,poorly written message from developer',16,1)
Msg 50000, Level 16, State 1, Line 1
Obscure,poorly written message from developer
Lowell
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply