Databases show as "Checking schema..." forever.
dwainew
Posts: 59 Bronze 4
Adding DBs went fine. this is dev, so I used a SQL account which has sa. no complaints, but also no results.
DLM Dashboard – Version: 1.4.3.197
DLM Dashboard – Version: 1.4.3.197
Tagged:
Comments
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.
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.
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, they seem to get caught up. I wonder if this is a case where you need to drop a db and add it back? Maybe use the IP instead of the name so it appears new?