Lab 8-Integrate SQL solutions with Azure services- Need improvement in instructions

Open Beginner friendly

#12 opened on Jun 23, 2026 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 62/100

Issue type: Documentation
Clarity: Mostly clear
Activity status: Quiet
Tech stack: azure, sql
Domain: cloud, databases, documentation

Research direction

Locate the Lab 8 instructions and review the database setup at the start and the “Test locally” task, especially Option B for SQL authentication. Update the lab so Azure SQL Database creation is covered and the tested connection-string example is used; done means both instruction paths are clear and consistent with the Skillable environment.

Written by the indexing model from the issue text.

Description

Lab 8- Integrate SQL solutions with Azure services
Issue 1- Lab start with Database creation by connecting Azure SQL database to SSMS/VS Code/SQL server.
But there is now step to create the SQL DB in Azure like other labs.
May me due to that there is no Azure subscription in Skillable platform.
Please add Azure SQL Database createtion task at the start.

Issue 2 - Under task- Test locally
Option B: SQL authentication
Shell | Command
PowerShell | $env:DATABASE_CONNECTION_STRING="Server=your-server.database.windows.net;Database=ProductCatalog;User Id=your-user;Password=your-password;TrustServerCertificate=true"

This gives error - else use the "connection string" as below- tested and worked well

PowerShell | $env:DATABASE_CONNECTION_STRING="Server=tcp:.database.windows.net,1433;Initial Catalog=;Persist Security Info=False;User ID=;Password={your_password};MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;"

Dominant language: TSQL
Stars: 23
Forks: 34
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

Similar issues

[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
fix(mcp): `permanently_delete_cloud_{source,destination,connection}` lack `workspace_id` param, unusable without a default workspace Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

airbytehq/PyAirbyte#1201 · Opened Sep 21, 2026
[BUG] Route53Resolver: CreateResolverEndpoint requires IpAddressRequests, but the AWS member is IpAddresses, so no SDK client can call it Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

floci-io/floci#4108 · Opened Sep 21, 2026
wm_gcp_parse_output underflows its heap buffer by one byte Open

level/task module/gcp type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

wazuh/wazuh#39525 · Opened Sep 21, 2026
[Bug]: aws_lb_listener silently ignores tcp_idle_timeout_seconds on TCP_UDP listeners Open

bug needs-triage service/elbv2

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

hashicorp/terraform-provider-aws#50100 · 1 comment · Opened Sep 21, 2026

More Cloud issues