Passing parameters to a stored procedure from C#

I have a stored procedure in SQLServer that wants a numeric(5,0) as the passed in parameter.  If I go to query analyzer and type in the value -179.73288 for this parameter, the stored procedure executes properly and the value is rounded in the table.  If I make a SqlParameter with this value and try and pass it into the stored procedure, I get the error "{"Parameter value '-179.73288' is out of range." } and the procedure doesn't execute.

I need to be able to pass parameters like that into the stored procedure from C# - how can I get it to put that parameter into the database?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Just convert parameter into string using ToString method.
bluedaisydawgAuthor Commented:
The parameter is already in the format of a string when it is added to the SqlParameter

Ahh, don't add the parameter to SQL parameters..
Create a string consisting of the name of the stored procedure and necessary parameters, exactly like you would use in query analizer.
Something like this, for example:

public SqlDataAdapter CallSqlDataProcedure(string procedure, string[] val)
      SqlConnection sqlConnection = new SqlConnection("bla-bla-bla")
      string proc = "EXECUTE " + procedure + " ";
      for (int k=0; k<val.Length; k++)
            if (val[k].Length == 0) proc += "''";
            else proc += val[k];
            if (k != val.Length-1) proc += ", ";

      SqlDataAdapter command = new SqlDataAdapter(proc,sqlConnection);
      return command;
Become a Certified Penetration Testing Engineer

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

bluedaisydawgAuthor Commented:
What I have is a C# DLL that gets the stored procedures and their parameters from the database.  Then when I call the DLL, I pass in the procedure name and the parameters that I have from my app.  It loops through and compares parameters and assigns the value from the calling program (in string format) to the parameters that match.  
"..and assigns the value from the calling program (in string format) to the parameters that match"

Sorry, didn't get it.
bluedaisydawgAuthor Commented:
There is a function in my C# DLL callStoredProcedure(spName, spParams)

Then in the C# DLL there is also an array of structs that look like:
struct paramArray
    string procedureName;
    SqlParameters[] params;
which has been loaded with all the stored procedures and their associated parameters in the database.  When the function is called - the function loops through it's array of parameters that it got from the database and assigns the value passed in (which is of type string) to the value.  Then it executes the stored procedure...

bluedaisydawgAuthor Commented:
I forgot to add - I tried in the calling code to just make the parameters whole numbers and it works fine.  So I think it must be something with the rounding.  
I think the conversion rules used by Transact-SQL (i.e. Query Analyzer) are less strict than those used by the SqlParameter class.  

Here are a couple of workarounds

1.  You could modify your DLL to do an explicit conversion based on the datatype of the SqlParameter object
2.  You could change the datatype of the stored proc parameter to something a little more generic (e.g. Numeric (10,5) or even Varchar(20)) and perform the conversion in the stored proc

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ok, got it.
First: you still can use the method I described in C# DLL right after assigning the values to Params.

Second and offtopic:
you could use SQL statement to retrieve all possible combinations of parameters from the database and after call stored procedures. In such case you
1. don't need  SqlParameters[] params
2. don't need to compose params you want to pass in procedure
3. you have all possible combinations of existing parameters
bluedaisydawgAuthor Commented:
I picked that comment as the answer because suggestion numer 2 was what I actually did.  I don't have any more points or I would have definitly upped the points on the question and given some to you WiB for working so hard on my question.  Thanks so much for your help!

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.