Comments
Sort by recent activity
We don't have a programmatic interface for SQL Source Control. This was
built for interactive work with developers and there is no API. / comments
We don't have a programmatic interface for SQL Source Control. This was
built for interactive work with developers and there is no API.
First, you could potentially have a way of auto committing, but you'd just be capturing changes without any context. No comments. That's not necessarily a good way of performing development. In the past, I've used auto scripting to do this. I don't know that SQL Compare could be automated to do this, but I wouldn't recommend it. Instead, I'd say that you should really be using something like SQL Compare to look at the db v VCS and alert you that changes need to be committed.
In terms of dealing with a volume of changes. The person that makes the change should commit it when they think it's done. Auto committing is bad because the work might not be done. You want there to be some decision to do this. If you can't keep up, then perhaps you have other development chaos. / comments
First, you could potentially have a way of auto committing, but you'd just be capturing changes without any context. No comments. That's not necessarily a good way of performing development. In the...
Done: https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/31791202-keep-static-data-stored-in-pk-order
I like this idea. It's really more a Data Compare item, but I'll let them know. / comments
Done: https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/31791202-keep-static-data-stored-in-pk-order
I like this idea. It's really more a Data Compare item, but I'll let the...
I don't know there will be any fix here. We've end of life'd DLM Dashboard for a variety of reasons. We are working on a replacement for this that includes some functionality. Some notes in here: https://www.red-gate.com/blog/database-development/why-and-how-you-should-automate-database-migrations / comments
I don't know there will be any fix here. We've end of life'd DLM Dashboard for a variety of reasons. We are working on a replacement for this that includes some functionality. Some notes in here: h...
Are you on version 1.7.5.x? / comments
Are you on version 1.7.5.x?
I'll apologize, though I know this isn't what you want to hear. The data is in a RavenDB system in ProgramData\Redgate\SQL Lighthouse. I downloaded Raven yesterday, but haven't set it up. I need to do this and get some client queries. Maybe I can help figure out what might be wrong. If I can, I'll post something. My suspicion is something got into an error state and the data is incorrect somewhere. Likely the error handling isn't sufficient to deal with this. I haven't run into this. I've added DLM Dashboard to a dozen or so installations and haven't had this issue. I have been able to run the setup script on a new server, then add the server in the dashboard without issue, and I might suggest that if you are open to digging around. What I'd suggest is removing the server from the config, and restart the DLMDashboard services. Then setup a new login on your instance that has the permissions. Sysadmin if you don't mind, otherwise, the permissions are doc'd here: https://documentation.red-gate.com/ddb1/getting-started/creating-a-login-with-the-correct-permissions I usually use a separate login, just for security purposes and so I can trace things. I've setup "dlmdashboard" as my login, with limited permissions. I then run the setup script (https://documentation.red-gate.com/ddb1/files/38043983/41358394/1/1459336529080/create_ddl_trigger.sql) to create the Redgate database. From here, if I add the new instance in DLM Dashboard, it seems to work smoothly, and when I pick a database, small or large, it grabs the schema and lets met set a version immediately. Again, I apologize. I know these are cheap words, but I'll see if I can find out more info, or get some debugging hints from a developer or two. / comments
I'll apologize, though I know this isn't what you want to hear.The data is in a RavenDB system in ProgramData\Redgate\SQL Lighthouse. I downloaded Raven yesterday, but haven't set it up. I need to ...
I'm sorry you're having issues. I've got a couple items to think about. First, have you restarted the DLMDashboard services? I wonder if something is stuck here. / comments
I'm sorry you're having issues. I've got a couple items to think about. First, have you restarted the DLMDashboard services? I wonder if something is stuck here.
I'll apologize, though I know this isn't what you want to hear. The data is in a RavenDB system in ProgramData\Redgate\SQL Lighthouse. I downloaded Raven yesterday, but haven't set it up. I need to do this and get some client queries. Maybe I can help figure out what might be wrong. If I can, I'll post something. My suspicion is something got into an error state and the data is incorrect somewhere. Likely the error handling isn't sufficient to deal with this. I haven't run into this. I've added DLM Dashboard to a dozen or so installations and haven't had this issue. I have been able to run the setup script on a new server, then add the server in the dashboard without issue, and I might suggest that if you are open to digging around. What I'd suggest is removing the server from the config, and restart the DLMDashboard services. Then setup a new login on your instance that has the permissions. Sysadmin if you don't mind, otherwise, the permissions are doc'd here: https://documentation.red-gate.com/ddb1/getting-started/creating-a-login-with-the-correct-permissions I usually use a separate login, just for security purposes and so I can trace things. I've setup "dlmdashboard" as my login, with limited permissions. I then run the setup script (https://documentation.red-gate.com/ddb1/files/38043983/41358394/1/1459336529080/create_ddl_trigger.sql) to create the Redgate database. From here, if I add the new instance in DLM Dashboard, it seems to work smoothly, and when I pick a database, small or large, it grabs the schema and lets met set a version immediately. Again, I apologize. I know these are cheap words, but I'll see if I can find out more info, or get some debugging hints from a developer or two. / comments
I'll apologize, though I know this isn't what you want to hear.The data is in a RavenDB system in ProgramData\Redgate\SQL Lighthouse. I downloaded Raven yesterday, but haven't set it up. I need to ...
To track changes, how would you know which row to change without a PK? If the text is unique, this should just be the PK. If it's not, then with duplicates, there's no good way to determine which rows to update unless we were to look at every field, in which case how can you determine it's an update and not a new row?
A PK is needed. WHERESCAPE may not create one, but likely there is a field that could be used as a PK, or a combination of fields. / comments
To track changes, how would you know which row to change without a PK? If the text is unique, this should just be the PK. If it's not, then with duplicates, there's no good way to determine which r...