I'm working my way through Beginning SQL Server 2005 Administration and I'm in Chapter 8, page 306. The exercise includes creating a stored proc for inserting a credit card that will cause an error to be raised. The code is:
CREATE PROCEDURE AddNewCreditCard
@CardType nvarchar(50),
@CardNumber nvarchar(25),
@ExpMonth tinyint,
@ExpYear smallint
AS
DECLARE @username varchar(60)
DECLARE @loginame varchar(60)
DECLARE @CreditCardInfo Table(CreditCardID INT)
DECLARE @CreditCardID INT
SET @loginame = suser_sname()
SET @username = user_name()

I keep getting the following error:
Msg 8152, Level 16, State 2, Procedure RecordDDL, Line 8
String or binary data would be truncated.
The statement has been terminated.

Everything looks good. The sizes for card type and number match the table and creditcardinfo is INT.

Why is the code getting an error? I feel silly asking this, but that's life.

B

Ummm...look at the error message.

It says the error is in
    Procedure RecordDDL

Doesn't say anything about the SP you are showing.

Thanks. I was blanking out on the error message. The stored Proc worked when I deleted the trigger RecordDDL. Not sure why it was failing when it worked in Chapter 5, but stuff happens. Thank you for your help.

Well, the error message is pretty clear: The SP is trying to shove data into some DB field or even some procedure variable that is longer than the field/variable.

Most often, this happens with VARCHAR/NVARCHAR fields. You declare one to hold, say, 30 characters (e.g., VARCHAR(30)) and then your code (or the data you are handling) tries to put 31 or more characters into that field/variable. Kablooey.

Chances are, if you can figure out WHAT field or variable is too short, just increasing its size will fix all. And the code may have accidentally worked for the author of the book because the data he tested with was shorter than your data. (Which just shows that even the code in books could stand to go through a QA process.)