TSqlExecution
Metadata
| Authors | Clay Lenhart |
|---|---|
| Copyrights | Copyright Clay Lenhart 2013 |
| Description | Executes any number of sql files on MS SQL Server. Since the code doesn't know the order to execute the files, it uses a retry mechanism until each batch in the file executes successfully |
| LicenseUrl | https://www.gnu.org/licenses/lgpl-3.0.txt |
| Owners | Clay Lenhart |
| ProjectUrl | https://sourceforge.net/p/tsqlexecution/wiki/Home/ |
| ReleaseNotes | Call SET XACT_ABORT ON at the beginning |
| RequireLicenseAcceptance | False |
| Tags | build database tsql unit testing continuous integration |
| Dependencies | BasicTSqlParsing:[2.0, 3.0) |
| Title | TSQL Execution |
| PackageSize | 23558 |
| PackageHashAlgorithm | SHA512 |
| PackageHash | 9c+9x3HcW2T6bm9Sc9DEEYCT1LP/1Q3ZlAOiFTYTken1+Hkn8no48dd78ZsjziERAPxgfW/6i+Fg2XMtGnqteQ== |
| DownloadCount | 000000 |
| CreatedDate | 2014-01-20T03:23:43 |
Access
You can access data for this project using the tools and addresses described below.
NuGet (nuget.exe)
- Installing the package (HTTP Basic authentication):
-
nuget install TSqlExecution -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install TSqlExecution -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
NuGet (Package Manager Console)
- Installing the package (search all configured feeds):
-
Install-Package TSqlExecution
- Installing the package (HTTP Basic authentication):
-
Install-Package TSqlExecution -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package TSqlExecution -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package TSqlExecution
OpenWrap
- Installing the package:
-
o add-wrap TSqlExecution
- Uninstalling the package:
-
o remove-wrap TSqlExecution
Versions
A version is snapshot of a project's source code. It does not need to follow the Major.Minor.Revision.Build numbering pattern. It can be an arbitrary string of text that identifies a release or a build, in particular including meaningful words like beta, RC or RTM.