Comments
Sort by recent activity
Rob C wrote: »
Hi Sebastian,
Ah, this explains things and I'll try to explain what is going on. We are trying to build a series of scripts. Script files don't really have a concept of database name as they are just flat files representing individual objects. When you use three part naming, the parser assumes you are referring to an external dependency that doesn't need to be built and this can result in an incorrect deployment order.
To fix this, you'll need to adjust these references to remove the database name.
How about the stored procedures that might be using other database tables for merging purposes, lookups (RI checks) during ETL process? how can we deal with cross-database objects mainly during DLM schema validation? I thought about synonyms but how are these handled during schema validation, do they fail? / comments
Rob C wrote: »
Hi Sebastian,
Ah, this explains things and I'll try to explain what is going on. We are trying to build a series of scripts. Script files don't really have a concept of database ...
Same here, while migration scripts have been very useful to protect our data in our target environments when making structural changes, they're causing way more issues in our jenkins build schema validation, for some reason schema validation fails when looking at old migration scripts, and while I know I can Ignore Migration Scripts, I would really would like to validate the schema of the migration scripts that have not been deployed yet. So far I don't know how to do this when using: Invoke-DlmDatabaseSchemaValidation Any ideas or thoughts? / comments
Same here, while migration scripts have been very useful to protect our data in our target environments when making structural changes, they're causing way more issues in our jenkins build schema v...
Does this mean that if we ever use synonyms in either views or user defined functions we won't be able to use LocalDB as our schema validation database? for example: $validatedScriptsFolder = $scriptsFolder | Invoke-DlmDatabaseSchemaValidation -SQLCompareOptions $options instead of $validatedScriptsFolder = $scriptsFolder | Invoke-DlmDatabaseSchemaValidation -SQLCompareOptions $options -TemporaryDatabaseServer $buildDb / comments
Does this mean that if we ever use synonyms in either views or user defined functions we won't be able to use LocalDB as our schema validation database?for example:$validatedScriptsFolder = $script...
swinghouse, any resolution on this? / comments
swinghouse, any resolution on this?
this is still happening, since 2010 , are there any red gate recommended workarounds? / comments
this is still happening, since 2010 , are there any red gate recommended workarounds?