SQL Server Errors or Failures from Error: 11511 to Error: 11530

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 11511 to Error: 11530

Error: 11511, Severity: 16, The metadata could not be determined because the statement ‘%.*ls’ in procedure ‘%.*ls’ is not compatible with the statement ‘%.*ls’ in the main batch.
Error: 11512, Severity: 16, The metadata could not be determined because the statement ‘%.*ls’ in procedure ‘%.*ls’ is not compatible with the statement ‘%.*ls’ in procedure ‘%.*ls’.
Error: 11513, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ contains dynamic SQL. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
Error: 11514, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ in procedure ‘%.*ls’ contains dynamic SQL. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
Error: 11515, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ invokes a CLR procedure. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
Error: 11516, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ in procedure ‘%.*ls’ invokes a CLR procedure. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
Error: 11517, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ invokes a CLR trigger.
Error: 11518, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ in procedure ‘%.*ls’ invokes a CLR trigger.
Error: 11519, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ invokes an extended stored procedure.
Error: 11520, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ in procedure ‘%.*ls’ invokes an extended stored procedure.
Error: 11521, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ uses an undeclared parameter in a context that affects its metadata.
Error: 11522, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ in procedure ‘%.*ls’ uses an undeclared parameter in a context that affects its metadata.
Error: 11523, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ causes indirect recursion.
Error: 11524, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ in procedure ‘%.*ls’ causes indirect recursion.
Error: 11525, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ uses a temp table.
Error: 11526, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ in procedure ‘%.*ls’ uses a temp table.
Error: 11527, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ does not support metadata discovery.
Error: 11528, Severity: 16, The metadata could not be determined because statement ‘%.*ls’ in procedure ‘%.*ls’ does not support metadata discovery.
Error: 11529, Severity: 16, The metadata could not be determined because every code path results in an error; see previous errors for some of these.
Error: 11530, Severity: 16, The metadata could not be determined because there are no code paths that reach the end of the batch.

With codeplex shutting down, we have moved SQL Nexus to github with a new release (6.0). Now both Pssdiag/SQLDiag manager and SQL Nexus are on github. Where to get it As you navigate to SQL Nexus, you can download code and released binary files. If you choose to download binary files, you can go to...

SQL Server : large RAM and DB Checkpointing Hi everyone, This post’s purpose is to establish a summary of the specific behaviors with relation to DB Checkpoint that may happen within SQL Server when running with a large quantity of allocated memory and when applicable, how to best address them. SQL Server 2016 improves...

Recently we got an inquiry from a customer who received the following message in errorlog and wanted to know why. [INFO] HkDatabaseTryAcquireUserMemory(): Database ID: [7]. Out of user memory quota: requested = 131200; available = 74641; quota = 34359738368; operation = 1. This is my first time to see this error. As usual, I relied...

Recently I assisted on a customer issue where customer wasn’t able to alter a memory optimized table with the following error Msg 41317, Level 16, State 3, Procedure ddl, Line 4 [Batch Start Line 35]A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases...

In a previous blog, I talked about memory optimized table consumes memory until end of the batch. In this blog, I want to make you aware of cardinality estimate of memory optimized table as we have had customers who called in for clarifications. By default memory optimized table variable behaves the same way as...

I worked on an interesting issue today where a user couldn’t restore a backup. Here is what this customer did: backed up a database from an on-premises server (2008 R2) copied the file to an Azure VM tried to restore the backup on the Azure VM (2008 R2 with exact same build#) But he got...

Recently, I looked an In-Memory OLTP issue with Principal Software Engineer Bob Dorr who is still my office neighbor. After restoring a database that had just one memory optimized table, we dropped the table. Even without any memory optimized tables,number of checkpoint files keep going up every time we issue a checkpoint. For a while,...

In this blog Added per-operator level performance stats for Query Processing, Senior PM in QP talks about extending operator level performance stats. They include stats related to reads, CPU and elapse time. These are very helpful to track down query performance issues. We worked on recent case where we put ActualElapsedms in a good...

In blog “Importance of choosing correct bucket count of hash indexes on a memory optimized table”, I talked about encountering performance issues with incorrect sized bucket count. I was actually investigating an out of memory issues with the following error. Msg 701, Level 17, State 103, Line 11There is insufficient system memory in resource pool...

I was working with a customer to troubleshoot memory optimized table issues. In this scenario, our customer uses a memory optimized table variable. He put 1 million rows of data into the table variable and then process it. Based on what he said, I tried to come up with a repro to see if...