Activity overview
Latest activity by jmeyerbejdl
Robert,
In an attempt to prove/disprove the notion that it was down to reference data I've added another database to our CI builds. This one is an archive database that has no reference data at all and it fails in exactly the same way, just without any errors being displayed in SQL Compare - the snapshot is visible in the SqlCompareSnapshots and comparing the extracted nuget package with database using SQL compare shows them to be identical, but the dashboard still reports drift rather than an update. Any idea where we can go from here? I'd really like to get this working.
Thanks / comments
Robert,
In an attempt to prove/disprove the notion that it was down to reference data I've added another database to our CI builds. This one is an archive database that has no reference data at all...
Robert,
I've now tried comparing the nuget package as suggested and it seems as though perhaps there is an issue with static data. If I compare the extracted nuget package from the root I get a whole load of errors saying 'Non-schema statement ignored', followed by one of the inserts of static data rows to our tables. I'm not sure if this is significant or not, but if do the comparison in the dbstate subfolder of the package rather than at root, that works correctly - the schema in the package and the database schema are identical. Is this down to the static data we have linked and if so is there some way that I can fix this?
Thanks / comments
Robert,
I've now tried comparing the nuget package as suggested and it seems as though perhaps there is an issue with static data. If I compare the extracted nuget package from the root I get a who...
Robert Clenshaw wrote:
Hi James,
We need to know if the build step is actually registering the schema with DLM Dashboard or if it's encountering a problem and not registering it. To verify that the schema has been registered, please perform the following -
Visit http://localhost:21060 in Internet Explorer.
In the top menu click on Documents.
In the left hand pane click on SqlCompareSnapshots.
In the main window, look for a snapshot with the package name that you were trying to register it with.
If you can find it in the list then you've been able to register the schema and the problem is somewhere else.
Another thing I would do is to extract the nuget package to a blank folder and then use SQL Compare to compare it to the database - if there has been some sort of issue with the sync step then there might be a schema difference. That would be a possible explanation for the dashboard not recognising the schema as the one that you registered.
Thanks.
Robert,
Thanks for the reply. I can see that several snapshots exist with names of packages built in Bamboo and yet I've never seen anything that wasn't identified as drift. It appears that registering the schema with the dashboard is working, exactly as the Bamboo log had suggested, but that something else is going wrong. I'll try comparing the nuget package as you suggested. Witha a bit of luck that might shed some light on the issue. / comments
Robert Clenshaw wrote:
Hi James,
We need to know if the build step is actually registering the schema with DLM Dashboard or if it's encountering a problem and not registering it. To verify that ...
Robert Clenshaw wrote:
Hi instalectual,
We discovered a bug (reference SQLLH-642) in DLM Dashboard where very long file names in the script folder caused a problem that meant the schema didn't get registered. In this case it was down to unit tests with long names, but in theory it could be any object with long names.
Try excluding unit tests from your build step to see if that helps. Make sure you restart the DLM Dashboard processes before doing this to make sure the effects of the bug aren't lingering.
What exactly do you mean by 'very long'? We seem to have the same issue, though with Bamboo. As far as I can tell, the longest script name we have is 82 characters, which is quite long but as I don't know what the limit is I've no idea if it's long enough to cause the issue we're seeing.
Thanks / comments
Robert Clenshaw wrote:
Hi instalectual,
We discovered a bug (reference SQLLH-642) in DLM Dashboard where very long file names in the script folder caused a problem that meant the schema didn't g...
SQL CI integration with DLM dashboard not working
Hi,
I'm trying to get the DLM dashboard set up for one of our databases which we've just started building and deploying using SQL CI. We're using Bamboo and are building the database using the comm...