How to Connect to a SQL Database in C# Using ADO.NET

Connecting to a SQL database in C# is easier than you think, and thanks to ADO.NET, you can do it with just a few lines of code.

Whether you're building a robust enterprise app or just tinkering with databases for fun, understanding how to make this connection is essential. Let’s break it down!

Step 1: Install the Required Package

First things first, make sure you have the System.Data.SqlClient namespace available.

This is built into .NET Framework, but if you're using .NET Core or later, you should install the Microsoft.Data.SqlClient package via NuGet:

Install-Package Microsoft.Data.SqlClient

Step 2: Define Your Connection String

A connection string contains all the necessary information to connect to your database. Here’s an example of a basic connection string for SQL Server:

string connectionString = "Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;";
  • Server: The name of your SQL Server instance (e.g., localhost, 127.0.0.1, or a remote server).
  • Database: The name of the database you want to connect to.
  • User Id & Password: Your SQL Server credentials (if using SQL authentication). If you’re using Windows Authentication, replace these with Integrated Security=True;.

Step 3: Create the Connection

Now, let’s connect to the database using SqlConnection:

using System;
using System.Data.SqlClient;

class Program
{
    static void Main()
    {
        string connectionString = "Server=myServer;Database=myDB;User Id=myUser;Password=myPass;";
        
        using (SqlConnection connection = new SqlConnection(connectionString))
        {
            try
            {
                connection.Open();
                Console.WriteLine("Connection successful!");
            }
            catch (Exception ex)
            {
                Console.WriteLine("Connection failed: " + ex.Message);
            }
        }
    }
}

Breaking It Down:

  • We wrap our SqlConnection in a using block to ensure proper disposal after use.
  • connection.Open(); establishes the connection.
  • We catch any errors to avoid app crashes (always a good practice).

Step 4: Execute a Simple Query

Now that we’re connected, let’s run a basic SQL query:

using (SqlCommand command = new SqlCommand("SELECT TOP 5 * FROM Users", connection))
{
    using (SqlDataReader reader = command.ExecuteReader())
    {
        while (reader.Read())
        {
            Console.WriteLine($"User: {reader["Name"]}, Email: {reader["Email"]}");
        }
    }
}

What’s Happening Here?

  • We use SqlCommand to define our query.
  • ExecuteReader() fetches the data.
  • We iterate through the SqlDataReader to display the results.

Wrapping Up

And there you have it! You’ve successfully connected to a SQL database in C# using ADO.NET. Now you can run queries, fetch data, and build amazing database-driven applications.

Feeling adventurous? Try inserting, updating, or deleting records using ExecuteNonQuery(). Happy coding! 🚀

0
141

Related

String interpolation, introduced in C# 6.0, provides a more readable and concise way to format strings compared to traditional concatenation (+) or string.Format(). Instead of manually inserting variables or placeholders, you can use the $ symbol before a string to directly embed expressions inside brackets.

string name = "Walt";
string job = 'Software Engineer';

string message = $"Hello, my name is {name} and I am a {job}";
Console.WriteLine(message);

This would produce the final output of:

Hello, my name is Walt and I am a Software Engineer

String interpolation can also be chained together into a multiline string (@) for even cleaner more concise results:

string name = "Walt";
string html = $@"
    <div>
        <h1>Welcome, {name}!</h1>
    </div>";
36
142

Primary constructors, introduced in C# 12, offer a more concise way to define class parameters and initialize fields.

This feature reduces boilerplate code and makes classes more readable.

Traditional Approach vs Primary Constructor

Before primary constructors, you would likely write something like the following:

public class UserService
{
    private readonly ILogger _logger;
    private readonly IUserRepository _repository;

    public UserService(ILogger logger, IUserRepository repository)
    {
        _logger = logger;
        _repository = repository;
    }

    public async Task<User> GetUserById(int id)
    {
        _logger.LogInformation("Fetching user {Id}", id);
        return await _repository.GetByIdAsync(id);
    }
}

With primary constructors, this becomes:

public class UserService(ILogger logger, IUserRepository repository)
{
    public async Task<User> GetUserById(int id)
    {
        logger.LogInformation("Fetching user {Id}", id);
        return await repository.GetByIdAsync(id);
    }
}

Key Benefits

  1. Reduced Boilerplate: No need to declare private fields and write constructor assignments
  2. Parameters Available Throughout: Constructor parameters are accessible in all instance methods
  3. Immutability by Default: Parameters are effectively readonly without explicit declaration

Real-World Example

Here's a practical example using primary constructors with dependency injection:

public class OrderProcessor(
    IOrderRepository orderRepo,
    IPaymentService paymentService,
    ILogger<OrderProcessor> logger)
{
    public async Task<OrderResult> ProcessOrder(Order order)
    {
        try
        {
            logger.LogInformation("Processing order {OrderId}", order.Id);
            
            var paymentResult = await paymentService.ProcessPayment(order.Payment);
            if (!paymentResult.Success)
            {
                return new OrderResult(false, "Payment failed");
            }

            await orderRepo.SaveOrder(order);
            return new OrderResult(true, "Order processed successfully");
        }
        catch (Exception ex)
        {
            logger.LogError(ex, "Failed to process order {OrderId}", order.Id);
            throw;
        }
    }
}

Tips and Best Practices

  1. Use primary constructors when the class primarily needs dependencies for its methods
  2. Combine with records for immutable data types:
public record Customer(string Name, string Email)
{
    public string FormattedEmail => $"{Name} <{Email}>";
}
  1. Consider traditional constructors for complex initialization logic

Primary constructors provide a cleaner, more maintainable way to write C# classes, especially when working with dependency injection and simple data objects.

0
68

When working with URLs in C#, encoding is essential to ensure that special characters (like spaces, ?, &, and =) don’t break the URL structure. The recommended way to encode a string for a URL is by using Uri.EscapeDataString(), which converts unsafe characters into their percent-encoded equivalents.

string rawText = "hello world!";
string encodedText = Uri.EscapeDataString(rawText);

Console.WriteLine(encodedText); // Output: hello%20world%21

This method encodes spaces as %20, making it ideal for query parameters.

For ASP.NET applications, you can also use HttpUtility.UrlEncode() (from System.Web), which encodes spaces as +:

using System.Web;

string encodedText = HttpUtility.UrlEncode("hello world!");
Console.WriteLine(encodedText); // Output: hello+world%21

For .NET Core and later, Uri.EscapeDataString() is the preferred choice.

27
1056