insnwd.sql is not a working code ( Jan 2022)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Open insnwd.sql and run it in SQL Server Management Studio while reviewing the reported errors, especially the syntax error and the Northwind database and object conflicts. Reproduce the failure and identify the script changes needed for it to execute without the listed errors.
Written by the indexing model from the issue text.
Description
Any time I attempt to download or even copy and paste the code in to SSMS I end up with an error.
Below is the error message I receive. I am new to this and do not know how to fix this and it appears that I would have to do so because of frequent syntax errors. What do I do now?
Error Message:
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '.'.
Msg 3702, Level 16, State 4, Line 13
Cannot drop database "Northwind" because it is currently in use.
Msg 1801, Level 16, State 3, Line 15
Database 'Northwind' already exists. Choose a different database name.
Msg 3726, Level 16, State 1, Line 113
Could not drop object 'dbo.Customers' because it is referenced by a FOREIGN KEY constraint.
Msg 2714, Level 16, State 6, Line 175
There is already an object named 'Customers' in the database.
Msg 1913, Level 16, State 1, Line 193
The operation failed because an index or statistics with name 'City' already exists on table 'dbo.Customers'.
Msg 1913, Level 16, State 1, Line 195
The operation failed because an index or statistics with name 'CompanyName' already exists on table 'dbo.Customers'.
Msg 1913, Level 16, State 1, Line 197
The operation failed because an index or statistics with name 'PostalCode' already exists on table 'dbo.Customers'.
Msg 1913, Level 16, State 1, Line 199
The operation failed because an index or statistics with name 'Region' already exists on table 'dbo.Customers'.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
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.
More from microsoft/sql-server-samples
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/sql-server-samples#1499 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
microsoft/sql-server-samples#1495 · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
microsoft/sql-server-samples#1341 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 64/100
microsoft/sql-server-samples#276 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
microsoft/sql-server-samples#1497 ·
All issues in microsoft/sql-server-samples
Similar issues
-
[Documentation Request] vLLM kv_load_failure_policy doesn't apply to load failures in L2 adapters Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
DATABASE_URL=pglite:memory: creates a directory named 'memory:' instead of an in-memory database Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BuilderIO/agent-native#5730 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
supabase/agent-skills#602 ·