microsoft / microsoft/sql-server-samples
post set of SQL 2019 BDC not able to login into DB via SQLCMD or Azure DB studio
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
Description
not particular error reported during the installation .
I have setup the K8S separately due to SPN creation failures
post that I have leveraged the python script to setup default BDC .
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Python script used to set up the default BDC and the separate Kubernetes setup described in the issue. Reproduce the post-installation login attempt with SQLCMD or Azure DB Studio, then capture the missing error details and determine whether the SPN setup is related; done means documenting or fixing the identified login failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, python, sql
- Domain
- authentication, cloud, databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100