x

sql errors

select * from sysmessages
gives me lots of error messages.
How I can relate the actual errors I face during maintenance plan/back up restore with above list of errors?

what is common parameter on which I can identify that this is relavent error message in the list,also is there is any solution list also available?

Aj

more ▼

asked Jul 21, 2010 at 12:28 AM in Default

avatar image

user-1930 (yahoo)
12 4 4 4

(comments are locked)
10|1200 characters needed characters left

4 answers: sort voted first

When an error occurs, SQL server offers you the error message along with errorcode (corresponds to an entry in sysmessages).

All error messages have their relevance - they are errors after all ;-)

If you are facing a specific issue, then I suggest that you look here or on your favourite search engine for possible solutions to that problem.

Looking for solutions to problems that are included in sysmessages may not be the best use of your time.

more ▼

answered Jul 21, 2010 at 12:34 AM

avatar image

WilliamD
26.2k 18 37 48

(comments are locked)
10|1200 characters needed characters left

First of all, sysmessages contains messages in many languages.. For English you can filter them by mslangid = 1033.

Also messages with severity 10 is always error.

But to search for possible errors and their meaning for particular operation or command, take a look in the BOL. There are mostly described scenarios which leads to errors.

Grant Fritchey already posted an answer to your previous question ist of sql server errors with link to the Handling database engine errorrs

more ▼

answered Jul 21, 2010 at 01:02 AM

avatar image

Pavel Pawlowski
22.7k 10 15 26

(comments are locked)
10|1200 characters needed characters left

Thank you pavel for your help again,I have already given you one thumbs up,please let me know if you have any email id,great to keep in sync with you.

more ▼

answered Jul 21, 2010 at 02:04 AM

avatar image

user-1930 (yahoo)
12 4 4 4

If you liked @Pavel's answer, in addition to giving him the +1 or thumbs up, check the answer using the little check mark. This makes it the "Answer" to the question, as opposed to one of many possible suggested answers. Also, where possible, respond to people using the "Add new comment" button, not typing another answer in using the answer box below. It helps to keep the conversation focused. Thanks.

Jul 21, 2010 at 05:26 AM Grant Fritchey ♦♦
(comments are locked)
10|1200 characters needed characters left

Assuming you're looking at the SQL Server Error Log for the messages, you should see two messages per incident - one giving the error code, severity and "state", and the other giving a more detailed description.

If you're not looking at the SQL Error Logs, but just at the error message returned to your application, then have a look at the SQL Error Logs. They do (sometimes) have the answers. if you need some code to do that programmatically, then just ask!

more ▼

answered Jul 21, 2010 at 01:32 PM

avatar image

ThomasRushton ♦♦
42.2k 20 57 53

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x1095

asked: Jul 21, 2010 at 12:28 AM

Seen: 591 times

Last Updated: Jul 21, 2010 at 12:54 AM

Copyright 2018 Redgate Software. Privacy Policy