Euan Garden - What are the myths about SQL Server (Yukon) that you'd like to correct?
- Posted: May 10, 2004 at 3:31 PM
- 18,119 Views
- 18 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Euan Garden takes on SQL Server myths. For instance, have you heard someone say that you need to be a .NET programmer to use the next version of SQL Server? Or, have you heard that SQL Server isn't scalable or performant? Euan takes those SQL Server myths head on. (In this video you catch a glimpse of the guy performing the interview, Jeremy Mazner, technical evangelist at Microsoft and you get to see Euan's office too).
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
What would you say to developers who are using MySQL to convince them to move over to MSSQL?
Iain
Euan : That's easy! We got views and triggers!
I should qualify my statement here by saying I use MSSQL and wouldn't care to use MySQL. But to give you an example of what I mean I have often used Access Data access pages to give people an interface to the data. I am an ASP/ASP.NET developer and I am opening up Access to build interfaces?? Yah, because sometimes it's just easier. Be pragmatic in your work. Work smarter and things will get easier. It means that the client/end user will get their job done easier as well.
I would like to hear however a response from MS on some of the technology advantages of MySQL - honestly I don't know.
Lord don't get me started on this debate. We have MySQL right now and i'm glad to say that we are finally converting to MS SQL Server. I have not used MS SQL Server but i am finding it is less of a learning curve than MySQL.
The other thing that MS SQL has are Stored Procedures, Backup and Restore Modules, Replication Services, and above all CONSTRAINTS!!! In MySQL by default (maybe it's just the version im suing) there are not foreign key constrains. You can type them with your CREATE TABLE syntax, but the server won't enfoce them!
Lastly, MS SQL has Enterprise Manager. Sure there are many GUI's written for MySQL, but the most popular one requires installing PHP on the server, not cool.
One of the big advantages MySQL had for a long time was cost. MySQL is free, except if you sell your product with it, then there are licensing fees.
MySQL is a good database, don't get me wrong, it has strength over MS SQL, but most of those are lifestyle arguements.
Chris Stepaniuk
Thanks for the discussion, i agree that taking those types of risks more often than not steel your sleep, but in the end pay off.
Speaking of myths...
I once heard that C# was going to be a replacement for C++, i laughed. When i was asked why, i asked this person if they knew that office was written entirely in C++, and large chunks of Visual Studio are written in Managed C++, C#, and VB.NET just to prove they could do it.
C++ isn't going anywhere, it will be around for many years, and you will continue to develop managed and unmanaged apps on the Windows platforms.
The first thing I would say is checkout our MSDE SKU which is free. Many people don't realise there is a free version of "SQL Server". It has very rich functionality, its 100% compatible with SQL Server Std and Enterprise Edition(you can just detach the database file and attach it to one of the higher end SKUs).
Next I would say look at the maturity of the Management/Development Tools and Perf Tuning tools. Tools like Profiler, Replay, Database Tuning Advisor and Graphical Showplan can really help developers build and tune there apps.
Then I would suggest going and looking into the fantastic help and advice thats available in our community via places such as http://msdn.microsoft.com/data or our newsgroups on msnews.microsoft.com or maybe some of our community sites like http://www.sqljunkies.com, http://www.sqlservercentral.com, http://www.sqlteam.com, http://sqlserverfaq.com, http://www.sswug.com/
Finally I would take a look at SQL2000 and SQL2005 and look at the range of features, the reliability, the scaleability and the performance, there is tons of information to look at, this is a great starting place: http://www.microsoft.com/sql/
-Euan
-Euan
Dealing with User Defined DataTypes written in managed languages via OLE DB, ODBC and ADO is pretty challenging, dealing with them in Managed code is a snap. Lots of the newer APIs that MS is producing are in the same bucket, VERY easy to use from managed, some harder and more challenging in native code.
In the tools team we replaced millions of lines of C++ code in this release with C#. We also wrote some new C++ and some Managed C++ code, this is mostly in SQL Computer Manager and Profiler. The former is pure C++ the later is a mix.
In reality some of the reasons we did not write everything in managed was a resourcing issue and for other external reasons which I don't believe are valid.
On the other hand I think we wrote MC++ in some places and it is still the choice.
Many people use office as a gauge to see whether Microsoft is serious about Managed code, there should be no doubt we are very very serious about managed code but we are also a business. It was the right time to rewrite the tools for Yukon for a variety of reasons, the timing was right that managed code was an option. The office team has not done a rewrite in many years of the main product, when they do I am sure managed will be one of their options and likely the choice. They did rewrite Windows Sharepoint Services 2.0 in managed code as the timing was perfect.
Remember also that in the SQL Server team we wrote all of reporting services, the server and the designer, in managed code.
We are producing a lot of managed code apps as a company today and this will only increase, but more importantly many of you, our customers are producing managed code apps.
-Euan
In addition to the competitive nature of it, MS implementing purely managed code tools will prove the legitimacy of many a developer. ANSI C has enjoyed it's status for a long time because multiple platforms have supported it, in an open standard. I see C# and the CLR capable of taking that same spotlight.
*crowd roars* =)
Euan,
That is awesome to hear. I know that i am not alone in the feeling that Microsoft isn't fully taking the plunge into managed code.
I am very excited to hear the integration with the CLR with SQL Server.
As for the Office argument, i agree, Microsoft is a business, and why break what works? Office is a huge app and would take a year or more to rewrite totally in managed code.
Again, thanks for all your insights into SQL Server and expecially the develop roles with SQL Server.
Chris Stepaniuk
To be honest I am not sure of Office's plans for the next release but they have always been keen on MSDE so I can only presume they still will be
-Euan
Does the SQL Team work much with the Access team?
Remove this comment
Remove this thread
close