Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Steps for connecting to SQL database #4619

Merged
merged 2 commits into from
Mar 4, 2025
Merged

Steps for connecting to SQL database #4619

merged 2 commits into from
Mar 4, 2025

Conversation

v-ajajvanu
Copy link
Contributor

Description

The procedures for connecting to a SQL database are outlined in this PR.

Related issues

Addresses issue #123379.

Testing

Reviewed it in code editor preview window.

FHIR Team Checklist

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

@v-ajajvanu v-ajajvanu added New Feature Label for a new feature in FHIR OSS Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs labels Sep 17, 2024
@v-ajajvanu v-ajajvanu added this to the S150 milestone Sep 17, 2024
@v-ajajvanu v-ajajvanu requested a review from a team as a code owner September 17, 2024 09:20
@v-ajajvanu
Copy link
Contributor Author

/azp run

@azure-pipelines Azure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@v-ajajvanu
Copy link
Contributor Author

/azp run

@azure-pipelines Azure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@v-ajajvanu
Copy link
Contributor Author

/azp run

@azure-pipelines Azure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@v-ajajvanu
Copy link
Contributor Author

/azp run

@azure-pipelines Azure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@v-rachitsh
Copy link

/azp run

@azure-pipelines Azure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@v-rachitsh v-rachitsh merged commit a21d2cc into main Mar 4, 2025
46 of 48 checks passed
@v-rachitsh v-rachitsh deleted the personal/v-ajaj/123379 branch March 4, 2025 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@evachen96 evachen96 evachen96 left review comments

@v-shnarang v-shnarang v-shnarang left review comments

@SergeyGaluzo SergeyGaluzo SergeyGaluzo left review comments

@v-rachitsh v-rachitsh v-rachitsh left review comments

@brendankowitz brendankowitz brendankowitz approved these changes

Assignees
No one assigned
Labels
Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs New Feature Label for a new feature in FHIR OSS
Projects
None yet
Milestone
S150
Development

Successfully merging this pull request may close these issues.
6 participants
@v-ajajvanu @v-rachitsh @brendankowitz @evachen96 @v-shnarang @SergeyGaluzo