This T-SQL script exceeds the maximum allowed size. Adjust this setting in the SQL Server Tools page by selecting Options from the Tools menu

snvhrwxg  于 2023-04-28  发布在  SQL Server
关注(0)|答案(4)|浏览(107)

I have a .sql scripts which is pretty huge. I added this script to a sql server project under visual studio 2013. When I try to build it I got this error message
This T-SQL script exceeds the maximum allowed size. Adjust this setting in the SQL Server Tools page by selecting Options from the Tools menu

According to this msdn article there is a property called Maximum script size it can be accessed in visual studio tools:

Tools->Options->Text Editor->SQL Server Tools->IntelliSense->Maximum script size

I changed it from 1MB to unlimited but nothing had changed

yacmzcpb

yacmzcpb1#

Change the setting under SQL Server Tools -> General

zpgglvta

zpgglvta2#

In addition to the other answers/comments I'd like to point out that ReSharper also played a role in this game.

I configured VS like so:

Tools / Options / SQL Server Tools / General / Database model size: 20 megabytes -> 200 megabytes
Tools / Options / Text Editor / SQL Server Tools / IntelliSense / Maximum script size: Unlimited

Still getting the error (which is not a build error btw., but an IntelliSense error, MSBuild works fine).

A colleague applied the same configuration and it worked for him. The reason was that he did not have ReSharper installed. After disabling ReSharper (2018.3.4 Build 183.0.20190304.43214) it worked for me as well.

We realized that there was a new version of ReSharper available (2019.1.1) and this one seems to have fixed the issue as well.

Just for reference: There is a Developer Community entry available with nearly the same content.

vktxenjb

vktxenjb3#

I had this issue, changed both settings, and have never had ReSharper loaded. This is a fresh install of vs 2019, with only microsoft extensions loaded. I had placed the very large sql script under the project/dbo/folder location. When I moved it to under the solution as a solution item the database project compiled with no concerns.

4nkexdtk

4nkexdtk4#

As of Visual Studio 2022 this issue still exists.

To get past the problem:

  1. Modify the settings described above by @Martin Smith and @timmkrause.
  2. Open the properties of the "offending" file (shown in Visual Studio's Error List output).
  3. Change the Build Action from "Build" to "None" and rebuild.
  4. Once successful, you can now restore the Build Action back to "Build".

相关问题