Lost parameter value during SQL trace in EF Core

Question

I have implemented an approach for tracing SQL queries from EF Core according to this article: https://learn.microsoft.com/en-us/ef/core/miscellaneous/logging. And have problems with tracing query parameters. When I receive Log events in all values of DbParameterLogData I see only the question mark instead of the actual values which I passed to the query.

I am using VS 2015.

Ferrochromium

That looks very much like the value is the string "?". How did you build the query? – Braze

No. For example query from other context but with the same result: IQueryable<Agreement> query = _agreements.Where(a => a.AgreementNumber == filter.AgreementNumber); And I'm shure, that filter.AgreementNumber have value differ from '?' – Ferrochromium

Answer 1

This is the default behavior of EF Core (filling up the DbParameterLogData.Value property with "?").

In order to get the real parameter values, you need to enable sensitive data logging by using DbContextOptionsBuilder.EnableSensitiveDataLogging method:

Enables application data to be included in exception messages, logging, etc. This can include the values assigned to properties of your entity instances, parameter values for commands being sent to the database, and other such data. You should only enable this flag if you have the appropriate security measures in place based on the sensitivity of this data.

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
{
    optionsBuilder.EnableSensitiveDataLogging();
    // ...
}

Heisel

Sometimes this results in a MissingMethodException. In which case, you should call it in ConfigureServices(): services.AddDbContext<MyDbContext>(options => options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")).EnableSensitiveDataLogging()) – Beatup

A little debugging trick. protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) { base.OnConfiguring(optionsBuilder); if (Debugger.IsAttached) { optionsBuilder.EnableSensitiveDataLogging(); } } – Imagination

Answer 2

The new way C#(just being a syntactic sugar) may be as follows.

builder.Services.AddDbContext<RepositoryContext>(o =>
    o.UseMySQL(configuration.GetConnectionString("sqlConnection")!)
     .EnableSensitiveDataLogging());

Thus, it prints a log as such

[Parameters=[@__companyId_0='3d490a70-94ce-4d15-9494-5248280c2ce3'], 
CommandType='Text', CommandTimeout='30']
      SELECT `c`.`CompanyId`, `c`.`Address`, `c`.`Country`, `c`.`Name`
      FROM `Companies` AS `c`
      WHERE `c`.`CompanyId` = @__companyId_0
      LIMIT 2

Instead of,

[Parameters=[@__companyId_0='?'], 
CommandType='Text', CommandTimeout='30']
      SELECT `c`.`CompanyId`, `c`.`Address`, `c`.`Country`, `c`.`Name`
      FROM `Companies` AS `c`
      WHERE `c`.`CompanyId` = @__companyId_0
      LIMIT 2

Ezarras