Modifying my query and SQL exception

I love MiniProfiler for our .NET project. However, I ran into a problem. The profiler actually raises several different requests that cause errors. For example, when the profiler is not initialized, an SQL query is generated containing nvarchar(4000) . However, when initializing the profiler, this part of the request was changed to nvarchar(max) . This results in the following SqlException :

The full-text query parameter for the full-text string is not valid.

I did not find anyone with a very similar question.

One solution would be to let the MiniProfiler be uninstalled dynamically in some way before this particular request is executed, so that only the default DBProviderFactory will be used for this request, not the MiniProfiler DBProviderFactory. However, this does not seem to be supported.

+6
source share
1 answer

If you are using a wireframe entity, then update the model because you are changing in the field range.

0
source

All Articles