Add options for timeout, schema restriction and dbo-prefixing #193
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added 3 new options:
timeout={secs}
- specify the commandTimeout for queries, as this could exceed the default 30 secs on slow machines or large databases.--noprefixdbo
- not prefixing dbo files is only set for backwards compatibility. The consensus seems to be that they should be. By default they will now be prefixed. This option allows for older code bases to turn that off for compatibility.schemas={a,b}
- an optional comma-separated list of schemas names. Only objects within these will be scripted (plus global objects such as users and assemblies). This is useful for us as we have a few dev-only schemas in our db which we do not want to script to source control.Additionally, I have swapped out the resharper test tools for the Nunit Test Adapter, as the generic test runner has been built into VS for quite a while now.
May fix #176