What are the challenges you face when working across database platforms? Take the survey
Options

Static Tables not deployed via OctopusDeploy

jsaravanakumarjsaravanakumar Posts: 3
edited July 28, 2015 5:55AM in DLM Automation
Hi,

I used the instructions below to setup an OctopusDeploy job for 1)Make database update resources and 2) Run the update script.
http://documentation.red-gate.com/displ ... pus+Deploy

This partially works and the schema is deployed to a new database. However I would want the "static data" to be deployed as well.
I have linked the static data as well in SQL source control and I am able to see it in my SVN.

However, I am not sure why Static data is not deployed to the target database. Appreciate any assistance on this issue.

If you see the logs below, "/include="StaticData" default option is not populated in the New-DatabaseRelease cmdlet. I see only an option to ignore static data since StaticData is included by default. However this does not work for me ? Any inputs please...


Log of OctopusDeploy:
Info 04:52:07
Executing step: Make database update resources

Info 04:52:07
Running "Make database update resources" on "DB-DEV"
Running PowerShell script: C:Windowssystem32configsystemprofileAppDataLocalTentacleTemp7e2fc676-cd9a-45ee-9cab-80111ee9ca94.ps1
Info 04:52:07
Tentacle script execution
Info 04:52:09
New-DatabaseRelease, SQL Release 1.2.1.3109, Copyright c Red Gate Software Ltd 2014-2015
VERBOSE: Calling: C:Program Files (x86)Red GateSQL ReleaseSCSQLCompare.exe
/? /OutputWidth:1024 /out:"C:WindowsTEMPSQL Releasei1msksod.log"

Info 04:52:11
VERBOSE: C:Program Files (x86)Red GateSQL ReleaseSCSQLCompare.exe ended
with exit code 0
VERBOSE: Calling: C:Program Files (x86)Red GateSQL
ReleaseSDCSQLDataCompare.exe /? /OutputWidth:1024 /out:"C:WindowsTEMPSQL
Releasewpjtdnxt.log"

VERBOSE: C:Program Files (x86)Red GateSQL ReleaseSDCSQLDataCompare.exe
ended with exit code 0
VERBOSE: Licensed: serial number
Making a scripts folder of database 'Test123' on server 'TestServer'.
VERBOSE: Calling: C:Program Files (x86)Red GateSQL ReleaseSCSQLCompare.exe
/server1:TestServer /database1:Test123 /username1:SA
/password1:******** "/makescripts:C:WindowsTEMPSQL Releasem3dl2uq1.j2z"
/force /options:DecryptPost2kEncryptedObjects,IncludeDependencies
/OutputWidth:1024 /out:"C:WindowsTEMPSQL Releasexitjo5zm.log"

Info 04:52:21
VERBOSE: C:Program Files (x86)Red GateSQL ReleaseSCSQLCompare.exe ended
with exit code 0
VERBOSE: SQLCompare.exe completed successfully.
Making a scripts folder of database 'Test456' on server 'TestServer'.
VERBOSE: Calling: C:Program Files (x86)Red GateSQL ReleaseSCSQLCompare.exe
/server1:TestServer /database1:Test456 /username1:SA
/password1:******** "/makescripts:C:WindowsTEMPSQL Releasejtnfnqnq.wvu"
/force /options:DecryptPost2kEncryptedObjects,IncludeDependencies
/OutputWidth:1024 /out:"C:WindowsTEMPSQL Releasegjvga2hf.log"

Info 04:52:29
VERBOSE: C:Program Files (x86)Red GateSQL ReleaseSCSQLCompare.exe ended
with exit code 0
VERBOSE: SQLCompare.exe completed successfully.
Creating the update script.
VERBOSE: Calling: C:Program Files (x86)Red GateSQL ReleaseSCSQLCompare.exe
"/scripts1:C:WindowsTEMPSQL Releasezwgrfyx3.ytq"
"/scripts2:C:WindowsTEMPSQL Releaseuzlgse0t.2td"
/options:ConsiderNextFilegroupInPartitionSchemes,DecryptPost2kEncryptedObjects,
DoNotOutputCommentHeader,ForceColumnOrder,IgnoreCertificatesAndCryptoKeys,Ignor
eDatabaseAndServerName,IgnoreTSQLT,IgnoreUserProperties,IgnoreUsersPermissionsA
ndRoleMemberships,IgnoreWhiteSpace,IgnoreWithElementOrder,IncludeDependencies,T
hrowOnFileParseFailed,UseMigrationsV2 /transactionIsolationLevel:SERIALIZABLE
"/scriptFile:C:WindowsTEMPSQL Release
s3kudy5.sql"
"/report:C:WindowsTEMPSQL Release240vmibj.xml" /reportType:Xml
/showWarnings /include:Identical /force /OutputWidth:1024
/out:"C:WindowsTEMPSQL Releasec5ymuhx0.log"

Info 04:52:49
VERBOSE: C:Program Files (x86)Red GateSQL ReleaseSCSQLCompare.exe ended
with exit code 0
VERBOSE: SQLCompare.exe completed successfully.
Export-DatabaseRelease, SQL Release 1.2.1.3109, Copyright c Red Gate Software Ltd 2014-2015
Exporting database deployment resources to folder 'C:xxxDatabaseUpdateResources'.
Info 04:52:49
==============================================
PowerShell exit code: 0
==============================================
Requesting upload...
Info 04:52:51
Collect artifacts created on tentacle
Info 04:52:51
Collecting remote file Changes.html...
Info 04:52:51
Storing artifact Changes.html...
Info 04:52:51
Collecting remote file Update.sql...
Info 04:52:51
Storing artifact Update.sql...

Comments

  • Options
    Hi There, sorry you've had trouble getting SQL Release set up.

    You're right that static data ought to be included by default by SQL Release (and is only turned off if you use the IgnoreStaticData flag.)

    Its not obvious to me right now why your static data isn't getting deployed as you'd expect. Something that would help me to debug the issue is if you could post the script you ran to generate the update (minus any sensitive data of course). Alternatively it could be useful if I could see the scripts folder you are updating from. If that is possible you can email me at dlmautomationsupport@red-gate.com

    Kind Regards,
    Matt Chandler
    Test Engineer on the DLM Automation Suite team.
    Matthew Chandler
    Software Developer on SQL Compare and SQL Data Compare
  • Options
    All,

    I got it resolved.
    The issue was that the scripts folder which I used was not the one which was within my Source Control repository. Instead it was a scripts folder which I created for the same DB using the below reference manually http://documentation.red-gate.com/displ ... ts+folders which was not part of the Source control.
  • Options
    I'm glad you sorted this out. Do let us know if you need any other help or information,

    Matt Chandler
    Matthew Chandler
    Software Developer on SQL Compare and SQL Data Compare
Sign In or Register to comment.