Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 53901
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 10, 20262026-05-10T17:08:09+00:00 2026-05-10T17:08:09+00:00

I’m a newbie when it comes to SQL. When creating a stored procedure with

  • 0

I’m a newbie when it comes to SQL. When creating a stored procedure with parameters as such:

@executed           bit, @failure            bit, @success            bit, @testID             int,     @time               float = 0, @name               varchar(200) = '', @description        varchar(200) = '', @executionDateTime  nvarchar(max) = '', @message            nvarchar(max) = '' 

This is the correct form for default values in T-SQL? I have tried to use NULL instead of ”.

When I attempted to execute this procedure through C# I get an error referring to the fact that description is expected but not provided. When calling it like this:

        cmd.Parameters['@description'].Value = result.Description; 

result.Description is null. Should this not default to NULL (well ” in my case right now) in SQL?

Here’s the calling command:

        cmd.CommandText = 'EXEC [dbo].insert_test_result @executed,                            @failure, @success, @testID, @time, @name,                             @description, @executionDateTime, @message;';          ...         cmd.Parameters.Add('@description', SqlDbType.VarChar);         cmd.Parameters.Add('@executionDateTime', SqlDbType.VarChar);         cmd.Parameters.Add('@message', SqlDbType.VarChar);          cmd.Parameters['@name'].Value = result.Name;         cmd.Parameters['@description'].Value = result.Description;         ...          try         {             connection.Open();             cmd.ExecuteNonQuery();         }         ...         finally         {             connection.Close();         } 
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. 2026-05-10T17:08:10+00:00Added an answer on May 10, 2026 at 5:08 pm

    A better approach would be to change the CommandText to just the name of the SP, and the CommandType to StoredProcedure – then the parameters will work much more cleanly:

    cmd.CommandText = 'insert_test_result'; cmd.CommandType = CommandType.StoredProcedure; 

    This also allows simpler passing by name, rather than position.

    In general, ADO.NET wants DBNull.Value, not null. I just use a handy method that loops over my args and replaces any nulls with DBNull.Value – as simple as (wrapped):

        foreach (IDataParameter param in command.Parameters)     {         if (param.Value == null) param.Value = DBNull.Value;     } 

    However! Specifying a value with null is different to letting it assume the default value. If you want it to use the default, don’t include the parameter in the command.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 57k
  • Answers 57k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • added an answer It is relevant if you have a place where data… May 11, 2026 at 8:30 am
  • added an answer Maybe one of these options will suit your needs (depending… May 11, 2026 at 8:30 am
  • added an answer Please, Try Using CPAN There's no reason you couldn't download… May 11, 2026 at 8:30 am

Top Members

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.

      Related Questions

      No related questions found