sql-server

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

Is your feature request related to a problem? Please describe.
Even if I have a folder open, especially in VS Code, and create a new SQL project - I have to reselect that folder as the project location.

![image](https://user-images.githubusercontent.com/12227241/166515237-e7ebaf

Feature Request

A simple command that just pulls readable information from msdb..suspect_pages.

Problem to solve

At times you need to monitor the suspect pages a server may have or verify after you get logical errors returned from DBCC results, or even finding the dreaded 823/824 err

Unlike all the existing charts that graph a string (most likely) against a number, this graphs numbers on both axises. So in addition to the configuration changes needed for passing the right field to chartjs, the PR for this should also change the "preferred type" to "number" for the x axis when the chart type is scatter plot.

I know it's not a course about RESTful principles but maybe you'll consider in the future extracting resource id from request body to path parameter ?

https://github.com/aspnetrun/run-aspnetcore-microservices/blob/c30712aa099bc335f5613a3b196ea1e943f800a5/src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs#L85

https://docs.microsoft.com/en-us/windows/communitytoolkit/mvvm/migratingfrommvvmlight

Hey,

I see awesome MySQL preset but at case in my company there are still missing some features. We need three things:

• Run in root mode.
• Don't choose database at start because we have multiple db's in single MySQL instance.
• Mount Docker volumes. We use internal cache for seeds and it's saved in Docker volume.

Here's a quick sneak peek what I'm talking about in code:
https://g

We currently have support for some, but not all of MySQL's logical operators.

For example, select 1 OR 1; works, but not select 1 XOR 1;. We should review MySQL's logical operators and ensure we support all of them.

Found by: go-sqlsmith