Embedded Resource limitation on large databases

paul

SQL Packager 5.4

My question concerns the 50MB limitation on package sizes when packaging large databases. This causes dlls to be created to store the extra data.

This was noted in this forum post: http://www.red-gate.com/messageboard/vi ... ght=store1

Is there a supported or well-accepted workaround for this involving modifications to the C# templates maybe? Something that may involve pre-compressing the data prior to package insertion?

We already have a database versioning\release process in place and stumbled across this problem today. Our process revolves around the one package exe that's generated and so the additional dlls involved with large db's are a problem.

Anyway, just curious as to any solutions that have presented themselves regarding the subject.

Thanks for any help,

Paul

chris.buckingham

I'm sorry to say that there is an arbitrary limit on the AppDomain class that Microsoft set which is out of our control - therefore there isn't a workaround for the 50MB limit.