User profile for rconrad

Found it. I had not specified a server on Invoke-DatabaseBild so it was probably using localdb. Thanks for your help. / comments

Found it. I had not specified a server on Invoke-DatabaseBild so it was probably using localdb. Thanks for your help.

0 votes

The project was originally version 3 and then upgraded to version 4. I was running a version 3 powershell module. I upgraded the SqlChangeAutomation module to the latest 4.2.20189.21070 which did not fix the problem. Then I added the DeployChangesForProgrammableObjects element to the project and that did fix the problem. Seems like I shouldn't need the DeployChangesForProgrammableObjects since I already had ProgrammableObjectHandling. I am now getting an error that TRIM() is not recognized. (If you prefer I can post this as a new question) WARNING: DbBuildTask: ERROR C:\Code\UtilityBilling\Databases\SCA\Client\ClientDB\Programmable Objects\dbo\Stored Procedures\pgb_custo mer_SSNSearch.sql(0,0): 'TRIM' is not a recognized built-in function name. I updated the DSP to Microsoft.Data.Tools.Schema.Sql.Sql150DatabaseSchemaProvider which I thought should correct that. Here is a snippet from the project file. <PropertyGroup> <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration> <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform> <Name>ClientDB2</Name> <SchemaVersion>2.0</SchemaVersion> <ProjectVersion>4.1</ProjectVersion> <ProjectGuid>{fd29acf3-02a8-4a8b-bb18-fe70d8ab409f}</ProjectGuid> <DSP>Microsoft.Data.Tools.Schema.Sql.Sql150DatabaseSchemaProvider</DSP> <OutputType>Database</OutputType> <RootPath> </RootPath> <RootNamespace>ClientDB</RootNamespace> <AssemblyName>ClientDB</AssemblyName> <ModelCollation>1033, CI</ModelCollation> <DefaultFileStructure>BySchemaAndSchemaType</DefaultFileStructure> <DeployToDatabase>True</DeployToDatabase> <TargetFrameworkVersion>v4.5.2</TargetFrameworkVersion> <TargetLanguage>CS</TargetLanguage> <AppDesignerFolder>Properties</AppDesignerFolder> <SqlServerVerification>False</SqlServerVerification> <IncludeSchemaNameInFileName>True</IncludeSchemaNameInFileName> <IsSqlChangeAutomationProject>True</IsSqlChangeAutomationProject> <MinimumEngineVersion>4.2</MinimumEngineVersion> <SqlChangeAutomationSchemaVersion>1.12</SqlChangeAutomationSchemaVersion> <DeployOnceSubFolder>Migrations</DeployOnceSubFolder> <DeployChangesForProgrammableObjects>True</DeployChangesForProgrammableObjects> <DeployChangesSubFolder>Programmable Objects</DeployChangesSubFolder> <DeployChangesImportSchemaFolders>True</DeployChangesImportSchemaFolders> <PreDeploymentSubFolder>Pre-Deployment</PreDeploymentSubFolder> <PostDeploymentSubFolder>Post-Deployment</PostDeploymentSubFolder> <GenerateSqlPackage>False</GenerateSqlPackage> <MigrationOrdering>FilePath</MigrationOrdering> <EvaluateExecutionOrderOnImport>True</EvaluateExecutionOrderOnImport> <Provisioner>CustomScripts</Provisioner> <TargetDatabaseSet>True</TargetDatabaseSet> <BuildOptionSkipShadowDeployVS>True</BuildOptionSkipShadowDeployVS> <DeployChangesInitialImportDone>True</DeployChangesInitialImportDone> <SccProjectName>SAK</SccProjectName> <SccProvider>SAK</SccProvider> <SccAuxPath>SAK</SccAuxPath> <SccLocalPath>SAK</SccLocalPath> <ProgrammableObjectHandling>UseRepeatableScriptsForAllObjects</ProgrammableObjectHandling> </PropertyGroup> / comments

The project was originally version 3 and then upgraded to version 4. I was running a version 3 powershell module. I upgraded the SqlChangeAutomation module to the latest 4.2.20189.21070 which did...

0 votes

Programmable Objects Disabled in Invoke-DatabaseBuild

I'm getting the warning below when I build my project using Invoke-DatabaseBuild and indeed the programmable objects are not included, but when I build in VS they work fine. I cannot find any plac...

3 followers 5 comments 0 votes

Further info. The database did exist it just doesn't show in object explorer. If I drop the database I am prompted to "Change Connection" or "Create Database" when I open the project. It seems that I do not have access to how the database is created from Visual Studio. / comments

Further info. The database did exist it just doesn't show in object explorer. If I drop the database I am prompted to "Change Connection" or "Create Database" when I open the project. It seems t...

0 votes

Deploy Project Not Using CreateDatabase script.

I'm using SCA in Visual Studio. I change my database connection to a database which does not exist. I click "Deploy Project". I get an error indicating the database does not have trustworthy on....

2 followers 2 comments 0 votes

Thanks for the heads up. I'll try that. / comments

Thanks for the heads up. I'll try that.

0 votes

I'm running into the same issue except that every single stored procedure and view are flagged as changed when in reality none of them have changed (and neither has anything else). If I "Import and Generate Script" I get a new script with no sql commands. The only thing in the script are commented lines regarding the symmetric key. / comments

I'm running into the same issue except that every single stored procedure and view are flagged as changed when in reality none of them have changed (and neither has anything else). If I "Import an...

0 votes

Yes, that works. Thanks. Am I misunderstanding the documentation on the getting started page? The code snippet for "Syncing to a test database" does not identify the source of $validatedProject, but the only other reference is the snippet in "Validating the SQL Change Automation project" which is set from Invoke-DatabaseBuild. https://documentation.red-gate.com/sca3/tutorials/getting-started-with-the-sql-change-automation-powershell-components / comments

Yes, that works. Thanks. Am I misunderstanding the documentation on the getting started page? The code snippet for "Syncing to a test database" does not identify the source of $validatedProject,...

0 votes

How can we help you today?

rconrad

Activity overview