Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SQL Operations Studio

github.com

Post reply on HN
Print view View original

91–96 of 96 posts

Re: SQL Operations Studio

#91

Post by dfox »

recursive wrote: post #45
dfox wrote: post #23

Earlier quoted context omitted.

I don't think that virtualized grid is an good idea for something that is primarily meant as GUI for SQL database that implicitly exposes the SQL to user.

You might have a good reason for thinking that, but I can't tell from this comment.

1) efficient implementation of data source for virtualized on top of relational (or otherwise not directly addressable) grid involves having some knowledge of how the data looks in order to be able to get only the relevant part of data by using indices ant not by geting rows 1000-1100 by selecting first 1100 and then throwing first 1000 out (which is how LIMIT 100 OFFSET 1000 is implemented by essentially all SQL databases)

2) when presenting results of user supplied SQL in this way you have to rewrite it somehow, which means that database ends up running different query than what the user entered, which is counterintuitive behavior and there certainly are cases where it is not desirable at all.

Re: SQL Operations Studio

#92

Post by will_hughes »

BrentOzar wrote: post #89
will_hughes wrote: post #26

Earlier quoted context omitted.

I just logged an issue suggesting a change of license: https://github.com/Microsoft/sqlopsstudio/issues/102

I had a discussion with MS about it, and they're going to update the Github issue soon. Short story is that they're not going to consider changing the license until general availability, but they're gathering feedback in the meantime.

Thanks for the update.

Re: SQL Operations Studio

#93

Post by SigmundA »

dfox wrote: post #91
recursive wrote: post #45

Earlier quoted context omitted.

You might have a good reason for thinking that, but I can't tell from this comment.

1) efficient implementation of data source for virtualized on top of relational (or otherwise not directly addressable) grid involves having some knowledge of how the data looks in order to be able to get only the relevant part of data by using indices ant not by geting rows 1000-1100 by selecting first 1100 and then throwing first 1000 out (which is how LIMIT 100 OFFSET 1000 is implemented by essentially all SQL dat…

A virtualized grid does not mean the data request is virtualized all the way to the sql server.

The main issue with displaying 100,000 rows in the browser is DOM overhead. A virtualized grid like Slickgrid which they are using, reuses dom elements as you scroll and in its simplest form is just backed by an in-memory JS object.

Once you start exceeding what works well in memory you can move to a local temp file system, which it sounds like what they are doing.

None of this has anything to do with the SQL server itself, it simply sends the entire result set to the client which deals with buffering and virtualizing it to the UI in whatever way necessary.

This is how native SQL UI's tend to work, I have never seen one rewrite SQL to try and virtualize all the way to the DB.

Obviously unless you do use the DB there will be limits, but 100,000 rows fits entirely in memory without issue: checkout this sample: http://mleibman.github.io/SlickGrid/examples/example-optimiz...

Re: SQL Operations Studio

#94

Post by mulltiq »

ConfucianNardin wrote: post #86
icc97 wrote: post #77

Earlier quoted context omitted.

Looks like it's opt-in [0] [0]: https://github.com/Microsoft/sqlopsstudio/blob/6e05dd7fa13d2...

That looks like opt-out (it's named "telemetry.enableTelemetry" and has "'default': true").

It's same as VSCode, I believe. So yes, you need to go to settings and set "telemetry.enableTelemetry" and "telemetry.enableCrashReporter" into false to opt-out.

Re: SQL Operations Studio

#95

Post by rexpan »

userbinator wrote: post #65

In case you're wondering, or just want to confirm the reason for the presence of a "privacy statement" --- yes, it does phone home: https://github.com/Microsoft/sqlopsstudio/tree/master/src/vs... At least the source is available, so it should be relatively easy to remove, but as the saying goes, "look before you leap"...

Set

"telemetry.enableTelemetry": false

In Preference > Settings

Re: SQL Operations Studio

#96

Post by yarovoy »

GFischer wrote: post #2

Would this be the "Visual Studio Code" to the SQL Server Management Studio? No mention of CosmosDB (I want some kind of SSMS equivalent for CosmosDB).

They added some preview support for CosmosDB recently to Azure Storage Explorer. https://azure.microsoft.com/en-us/features/storage-explorer/

But I haven't used it with CosmosDB yet.

Post reply on HN