Comments
Sort by recent activity
I don't see anything that indicates this could be the issue. Perhaps you could clarify what you mean by Scripts folder. I also can't find any information on bug SQLLH-642 in your documentation. My build log only shows the following when executing the DLM Dashboard stage:
[17:08:55][Step 2/4] Registering schema with DLM Dashboard...
[17:08:56][Step 2/4] Done
[17:08:58][Step 2/4] Process exited with code 0 / comments
I don't see anything that indicates this could be the issue. Perhaps you could clarify what you mean by Scripts folder. I also can't find any information on bug SQLLH-642 in your documentation. My ...
I am having a similar issue using SQLCI integration with Teamcity and sending the schema information to DLM Dashboard. Was there ever any resolution on this? The build step in Teamcity just says "Registering schema with DLM Dashboard..." No schemas are recognized and every deployment is listed as drift. I am using the same .scpf filter file in the DLM dashboard as is used throughout our release/deployment process. Is there a way to verify that the DLM Dashboard is in fact recieving the schema updates from SQLCI?
My Config:
DLM Dashboard 1.6.5.639
TeamCity Enterprise 9.1.4 (build 37293)
DLM Automation Suite 1.3.11.393
sqlCI.exe -- Red Gate's SQL Continuous Integration v2.1.9.169
SQL Server 2014 / comments
I am having a similar issue using SQLCI integration with Teamcity and sending the schema information to DLM Dashboard. Was there ever any resolution on this? The build step in Teamcity just says "R...
I am no longer experiencing this issue with the newest beta (11.0.0.198), everything is working as expected. / comments
I am no longer experiencing this issue with the newest beta (11.0.0.198), everything is working as expected.
I upgraded from v11.0.0.142 to v11.0.0.184
This is a side by side installation with v10 and I've tried both upgrading and uninstalling and reinstalling. Curiously, if I try to go back to v11.0.0.142 it now also gives me a trial expired error. / comments
I upgraded from v11.0.0.142 to v11.0.0.184
This is a side by side installation with v10 and I've tried both upgrading and uninstalling and reinstalling. Curiously, if I try to go back to v11.0.0.14...
I received a popup window when executing at the command line using the new beta stating that my trial period has expired although the console window message stated that the trial was valid until Sept. 1. The window said to press the skip button to continue the trial however skip button was grayed out. I ended up trying my current Toolbelt license and that made it go away. I'm not sure why that worked but it did, hopefully I didn't just waste an activation. / comments
I received a popup window when executing at the command line using the new beta stating that my trial period has expired although the console window message stated that the trial was valid until Se...
It turns out that one of the table creation scripts in SVN was trying to grant permissions to the user and since the user no longer exists we encountered the error. I'm still not clear why that grant statement was in the table creation script but editing the script and committing seemed to resolve the issue. Hopefully editing the script directly doesn't have any unintended consequences.
-D / comments
It turns out that one of the table creation scripts in SVN was trying to grant permissions to the user and since the user no longer exists we encountered the error. I'm still not clear why that gra...
I can run a trace while the synchronization happens. I don't think it's the filters however because I am able to run the command manually at the command line and it works. It's the exact same command using the same filters on which the automatic task is failing. Also, the user it fails to synchronize does not exist in the source or target, I think the issue would be related to whatever is causing the synchronization task to try and synchronize a object that is not in either database. / comments
I can run a trace while the synchronization happens. I don't think it's the filters however because I am able to run the command manually at the command line and it works. It's the exact same comma...
I'm not sure if this was ever resolved but I am able to reproduce this issue using SQL Source Control 3.4.9.265.
I have created my own DB for tracking changes and modified the appropriate xml config file. The changes are being logged correctly and everything works for the most part except for a similar condition as the OP.
I created a new stored procedure and the change appears on the commit tab with my username and is in change log. I did not commit the change and made a subsequent modification to the new procedure. This change also appears in the change log with my username but after refreshing the commit tab now shows changed by as 'Unknown' in grey text. I was able to reproduce this behavior with several procs.
-Daniel / comments
I'm not sure if this was ever resolved but I am able to reproduce this issue using SQL Source Control 3.4.9.265.
I have created my own DB for tracking changes and modified the appropriate xml confi...