THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Greg Low (The Bit Bucket: IDisposable)

Ramblings of Greg Low (SQL Server MVP, MCM and Microsoft RD) - SQL Down Under

Big Changes for Visual Studio and .NET–Where is the Ecosystem for SQL Server?

Published Thursday, November 13, 2014 10:43 AM by Greg Low

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Cody said:

I thought the news (about .NET) was really interesting but I don't think it will lead to any huge changes. I'm also not really happy about it.

- If they were waiting for .NET to be mature they could just as easily have justified doing this 5-7 years ago.

- If they were doing this because they are about to jettison .NET, somehow I don't see that happening.

- They might be desperate to build .NET brain share. Again, I'm not sold.

- But also .NET has already been available on Linux and Mac for a decade with Mono.

I think the real source of this is a random move by their newish CEO to appear trendy and innovative. Even if it doesn't make sense, the press will just say it's so forward-thinking us mere mortals can't understand it.

But most importantly, to me, I'm a huge Richard Stallman supporter so I see this as just another move by Microsoft to poison the well of the Free Software movement with their inferior Open Source derivative. See: https://www.gnu.org/philosophy/open-source-misses-the-point.html

Of course, if it turned out SQL Server 2016 was built on .NET and runs on Mac and Linux... well that would be awesome :-P

November 13, 2014 8:21 AM
 

mbourgon said:

FWIW, agreed on all points.  Thankfully the community has been dealing with the SSMS plugin hole - specifically Red-gate's IDE for SSMS (http://documentation.red-gate.com/display/MA/SSMS+ecosystem+project).  But hell, I've got dozens of connect items marked as Won't Fix - features that worked in Query Analyzer(!) that don't exist anymore.  

I'm glad MS is working on all these high-concept projects like CCS, Hekaton, etc - but how about fixing some of the more used stuff?  Yes, I pay a premium for Enterprise, but I use SSMS on a daily basis a lot more than I deal with Hekaton.  And I'd give a body part for stuff like Federations (or whatever replaced it) in my datacenter, without having to write it myself.  Not everyone's moving to Azure, guys.  We're getting squeezed on the AWS side, specifically Scale-Out, and using Azure features doesn't help me one whit.

*sigh*

November 13, 2014 9:25 AM
 

Cody said:

I'd just like to clarify (on my comment) that it has since come out they are using a permissive MIT license which makes it real free software and not open source.

So I'll have to take back part of my comment. This makes it an amazing contribution to the computing community.

November 15, 2014 12:05 AM
 

Daniel Nolan said:

As an indie software developer, the lack of extensibility within SSMS is a major drawback for me, as my database development projects only work in Visual Studio at present, requiring end-users to alt tab between the two IDEs.

Ideally I'd like to be able to introduce my database development projects to SSMS to avoid the context switching, but the tool has no support for MSBuild-based projects at the moment.

However it is true that the functional gap between VS and SSMS has been closing (e.g. VSPackage support was added in 2012) so I hold out hope that this will change at some point.

November 18, 2014 5:05 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

Tags

No tags have been created or used yet.

Archives

Privacy Statement