Forum Discussion
Why is Visual Code giving me these errors?
I'm trying to use Visual Studio to debug a SQL Server procedure. I need some help to understand what it's doing.
When I right-click (project)>Properties>Debug in Solution Explorer it shows the correct connection string, and when I click the Edit button it shows the correct database name. But the status line of the editor pane appears to say I'm connected to a different database; on the left it shows "Connection ready," and on the right it shows "(local)\<connection name>, then my user name, then the wrong database name.
I have imported the database into the project. When I expand dbo>Tables under my project name in Solution Explorer, it shows that the right table is there.
The error pane shows an "unresolved reference" error for every reference to the table and every column in the table. (Yes, I have double-checked that I spelled the table name correctly.)
It appears that my project is using the wrong database, even though Solution Explorer says it's set to use the right one. And since I must use Solution Explorer to change the database it uses, I don't see how I can fix the problem.
Finally, a related question: Is there some explanation of debugging SQL code with Visual Studio that will make all of this stuff intelligible? I've debugged countless programs in several languages, including some with Visual Studio, and I've never encountered an environment that was this complex; where I needed to know so many technical details just to get started!
1 Reply
The mismatched database in the editor and the unresolved references need separate checks. A SQL project validates a database model, while a query editor also has its own execution connection; the status bar does not by itself prove the project imported the wrong database. First open SQL Server Object Explorer, select the intended server/database, and create a New Query there. Confirm that editor’s connection before executing anything. Then rebuild the project and capture the first complete SQL71501/SQL71502 message from Error List. Check schema-qualified names and any cross-database references or SQLCMD variables named in that message; changing the execution connection alone will not resolve missing model references. Microsoft Learn’s “Debug stored procedures” walkthrough demonstrates a breakpoint on EXEC, Execute With Debugger and F11 to step inside. Use a test database. Share your Visual Studio/SSDT versions and the exact first error so the applicable correction can be identified.
