Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Size Limit on SQL Change Scripts
-
Is there a size limit on SQL change scripts? I have a SQL script that is just under 6KB, and when I try to add it to my application I get an HTTP 500 when I click "Save Change Script". Other scripts seem to be fine.
Product: BuildMaster
Version: 4.1.5
-
Not really; it'd be more related to timeouts than anything else. But you wouldn't see that at 6KB.
My guess is that it's something else (crash when detecting encoding, perhaps?) Is there a stack-trace or other information related to the 500?
-
I don't have any other information other than it's an HTTP 500 on /applications/#/change-scripts/edit (POST). It's just a standard ANSI file, but setting the encoding to "ANSI" doesn't help.
Does BuildMaster do any kind of syntax checking or does it just take whatever it's given? The script consists of a bunch of UPDATE statements wrapped in a transaction.
-
I just lopped off a chunk of SQL from the end of the file to get it under 4KB, and BuildMaster is happily accepting it.
If it's not BuildMaster, could it be an IIS configuration issue?
-
It could be the max request length (we don't configure it in our webconfig), but that usually complains after 6MB, not KB.
Could you try adding...
maxRequestLength="1048576"
to thehttpRuntime
web.config element.<requestLimits maxAllowedContentLength="1073741824" />
under therequestFiltering
element
Does that help?
-
That worked. Thanks!
-
So apparently these changes are overwritten when we upgrade BuildMaster. Is there any way to make these part of BuildMaster out of the box, or are they environment-specific settings that you don't want to set across the board for all your customers? If it can't be added to the stock BuildMaster install, we'll have to make a note to change the Web.config every time we upgrade.
-
We've made settings part of BuildMaster like that in the past (e.g. FormsAuthenticationTimeout).
Since I'm not sure how we'll handle this particular setting in the future, you can set the value in machine.config for the time being.
You can find the .config here: C:\Windows\Microsoft.NET\Framework[version]\config\machine.config