What is the easiest-to-implement/fastest-to-set-up/cheapest/preferably-open-source way to publish and existing OHDSI/OMOP database as FHIR?
Related
I'm working on a project to create hybrid SQL database per tenant model. While we were able to replicate the on-premise databases to databases in Azure. I'm not able to find a way to continuously sync both on-prem DB and cloud DB (We cannot use data sync agent or transaction replication). We are looking for any other alternatives that we can try to achieve our purpose.
Also, how does synchronization works when the internet is down and cannot sync with cloud?
Sorry for my ignorance since I'm new to this field.
Thanks.
why can't you use data sync agent? It can be installed in other machine that has access to the database and internet.
I've an asp.net web API connecting to SQL server with migration enabled both in the asp.net web API visual studio solution ( migration folder present in the solution) and SQL server DBA which has the _Migration history table created.
Now, I want my asp.net web api connect to the another New dB which has the same tables along with their schema as the old dB.
I need to connect to the new dB seamlessly without creating the migration history table in the new dB. I know we can enable migration by running the update database command from the package manager console. But I need my asp.net web API to connect to the new dB with out creating creating migration history table in the new dB.
Please suggest me how to achieve this. Thank you
The database for our Dynamics CRM installation is clustered and located on two servers. Somewhere, the MSCRM_CONFIG database is called on one of the SQL instances instead of the cluster, leading to access problems.
I need to correct this and make sure the database is called on the cluster instead. Where can I look for places where MSCRM_CONFIG is called from (config files, services etc)?
What I have tried without success
Looked in the config files for our custom-built CRM-related services
Searched config files in the Program Files\Microsoft Dynamics CRM folder for the name of the instance
Looked at the Deployment Manager for the SQL Server for our CRM Organization
Every Dynamics CRM Server (front-end and back-end as well as servers with the discovery or deployment role) can be expected to open connections to the MSCRM_CONFIG database. This database is needed to get e.g. the organization settings.
The connection string for the MSCRM_CONFIG database can be found on these servers in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\configdb.
I'm working through this tutorial:
Deploying an ASP.NET Web Application to a Windows Azure Web Site and SQL Database
In the second part "Enable Migrations and create the database" I need to use the NuGet Package Manager console to enter a series of commends:
enable-migrations -ContextTypeName ToDoListApp.Models.ToDoDb
add-migration-initial
update-database
Why do I need to do this explicitly? Shouldn't this be wrapped up in the publish process?
Thanks
Dave
The migrations process is separate from Azure. You can have an MVC 4 project that uses database migrations but the database is not hosted on Azure. The commands you are referencing simply enable the migrations in any MVC 4 project.
I find updating the database dangerous, so I actually prefer it to be separated from the publishing process because this way someone on your team is able to update the logic of the website without pushing updates to the database.
I'm a bit new to database projects, but I find that with a bigger team it is a good way to synchronize development.
I had a single Database Project that contained all the tables used by a web app.
The powers that be want to display data from another database in the web app.
I create another Database Project that represents the tables I need in the other database.
I create views in the original database that represent tables in the second database (for linq to sql joins mainly)
Questions
Do I create a Sql Server 2008 Server Project and merge both of these databases into it? From what I can tell, a Server Project still only represents a single database.
If a Server Project isn't meant to represent multiple databases, what is it for?
I have added steps in our TFS Workflow to deploy changes from the first Database Project into our Dev environment on check-in (CI). Assuming a Server Project is meant to contain multiple database projects, can I deploy it and have it deploy changes in both databases?
Thanks!
A server project is for server scope objects needed by your solution: endpoints, server principals (logins), server level permissions, linked servers and other similar constructs that are not scoped to any particular database.
Seems to me that what you need is a solution with two projects:
your original database project
you reference database project
You need a third project in this solution, a server project, only if you must add server scoped objects.
For more details, see Using References in Database Projects.