To store Error details occurring at every column
I have created two Table's called Test and TestError. Any error at any of the columns while inserting data into Test, i want error description to be logged in TestError table.
Create Table Test
(Id int,
Name varchar(5),
Isdeleted bit)
Create Table TestError
(Id int identity(1,1),
ErrorDescription Nvarchar(max)
)
For example while trying to execute the following insert statement:
Insert into Test values('a','abcdef',1)
I get an error 'Conversion failed when converting the varchar value 'a' to data type int.' which is fine. but, if you look at the data i am trying to insert into 'Name' column which exceeds length of column, i am expecting another error like 'String or binary data would be truncated.'. However, sql server just give error information for one column, whereas i need error information at all columns.
I want Table TestError to look something like this:
Id ErrorDescription
1 Error at column Id:Conversion failed when converting the
varchar value 'a' to data type int. | Error at column Name:
String or Binary data would be truncated
sql-server asked Jan 20 at 12:13
Prathamesh shindePrathamesh shinde
92
add a comment |
I have created two Table's called Test and TestError. Any error at any of the columns while inserting data into Test, i want error description to be logged in TestError table.
Create Table Test
(Id int,
Name varchar(5),
Isdeleted bit)
Create Table TestError
(Id int identity(1,1),
ErrorDescription Nvarchar(max)
)
For example while trying to execute the following insert statement:
Insert into Test values('a','abcdef',1)
I get an error 'Conversion failed when converting the varchar value 'a' to data type int.' which is fine. but, if you look at the data i am trying to insert into 'Name' column which exceeds length of column, i am expecting another error like 'String or binary data would be truncated.'. However, sql server just give error information for one column, whereas i need error information at all columns.
I want Table TestError to look something like this:
Id ErrorDescription
1 Error at column Id:Conversion failed when converting the
varchar value 'a' to data type int. | Error at column Name:
String or Binary data would be truncated
asked Jan 20 at 12:13
Prathamesh shindePrathamesh shinde
92
1
Very difficult. SQL won't continue after the first error. So what you would have to do is catch the first error, fix it automatically somehow, then retry. That seems like a massive undertaking.
– Max♦
Jan 20 at 12:22
1
A possible approach might be to limit this to one error per column. Create a bunch of tests transactions first, each trying only one of the new column values, valid dummy values for the others. Each test transaction rolls back. See if they all pass, if not record all the errors.
– Max♦
Jan 20 at 12:26
add a comment |
I have created two Table's called Test and TestError. Any error at any of the columns while inserting data into Test, i want error description to be logged in TestError table.
Create Table Test
(Id int,
Name varchar(5),
Isdeleted bit)
Create Table TestError
(Id int identity(1,1),
ErrorDescription Nvarchar(max)
)
For example while trying to execute the following insert statement:
Insert into Test values('a','abcdef',1)
I get an error 'Conversion failed when converting the varchar value 'a' to data type int.' which is fine. but, if you look at the data i am trying to insert into 'Name' column which exceeds length of column, i am expecting another error like 'String or binary data would be truncated.'. However, sql server just give error information for one column, whereas i need error information at all columns.
I want Table TestError to look something like this:
Id ErrorDescription
1 Error at column Id:Conversion failed when converting the
varchar value 'a' to data type int. | Error at column Name:
String or Binary data would be truncated
asked Jan 20 at 12:13
Prathamesh shindePrathamesh shinde
92
I have created two Table's called Test and TestError. Any error at any of the columns while inserting data into Test, i want error description to be logged in TestError table.
Create Table Test
(Id int,
Name varchar(5),
Isdeleted bit)
Create Table TestError
(Id int identity(1,1),
ErrorDescription Nvarchar(max)
)
For example while trying to execute the following insert statement:
Insert into Test values('a','abcdef',1)
I get an error 'Conversion failed when converting the varchar value 'a' to data type int.' which is fine. but, if you look at the data i am trying to insert into 'Name' column which exceeds length of column, i am expecting another error like 'String or binary data would be truncated.'. However, sql server just give error information for one column, whereas i need error information at all columns.
I want Table TestError to look something like this:
Id ErrorDescription
1 Error at column Id:Conversion failed when converting the
varchar value 'a' to data type int. | Error at column Name:
String or Binary data would be truncated
asked Jan 20 at 12:13
Prathamesh shindePrathamesh shinde
92
asked Jan 20 at 12:13
Prathamesh shindePrathamesh shinde
92
asked Jan 20 at 12:13
Prathamesh shindePrathamesh shinde
92
asked Jan 20 at 12:13
Prathamesh shindePrathamesh shinde
92
asked Jan 20 at 12:13
Prathamesh shindePrathamesh shinde
92
92
1
Very difficult. SQL won't continue after the first error. So what you would have to do is catch the first error, fix it automatically somehow, then retry. That seems like a massive undertaking.
– Max♦
Jan 20 at 12:22
1
A possible approach might be to limit this to one error per column. Create a bunch of tests transactions first, each trying only one of the new column values, valid dummy values for the others. Each test transaction rolls back. See if they all pass, if not record all the errors.
– Max♦
Jan 20 at 12:26
add a comment |
1
Very difficult. SQL won't continue after the first error. So what you would have to do is catch the first error, fix it automatically somehow, then retry. That seems like a massive undertaking.
– Max♦
Jan 20 at 12:22
1
A possible approach might be to limit this to one error per column. Create a bunch of tests transactions first, each trying only one of the new column values, valid dummy values for the others. Each test transaction rolls back. See if they all pass, if not record all the errors.
– Max♦
Jan 20 at 12:26
1
1
Very difficult. SQL won't continue after the first error. So what you would have to do is catch the first error, fix it automatically somehow, then retry. That seems like a massive undertaking.
– Max♦
Jan 20 at 12:22
Very difficult. SQL won't continue after the first error. So what you would have to do is catch the first error, fix it automatically somehow, then retry. That seems like a massive undertaking.
– Max♦
Jan 20 at 12:22
1
1
A possible approach might be to limit this to one error per column. Create a bunch of tests transactions first, each trying only one of the new column values, valid dummy values for the others. Each test transaction rolls back. See if they all pass, if not record all the errors.
– Max♦
Jan 20 at 12:26
A possible approach might be to limit this to one error per column. Create a bunch of tests transactions first, each trying only one of the new column values, valid dummy values for the others. Each test transaction rolls back. See if they all pass, if not record all the errors.
– Max♦
Jan 20 at 12:26
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54276302%2fto-store-error-details-occurring-at-every-column%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54276302%2fto-store-error-details-occurring-at-every-column%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Very difficult. SQL won't continue after the first error. So what you would have to do is catch the first error, fix it automatically somehow, then retry. That seems like a massive undertaking.
– Max♦
Jan 20 at 12:22
1
A possible approach might be to limit this to one error per column. Create a bunch of tests transactions first, each trying only one of the new column values, valid dummy values for the others. Each test transaction rolls back. See if they all pass, if not record all the errors.
– Max♦
Jan 20 at 12:26