We are considering upgrading from SQL Server 2008 to SQL Server 2019, but I just noticed on this website that the support end date for 2019 is 1/7/2025. If we do this upgrade, we would basically only have "support" for 2023-2024. This seems pretty short, so I wanted to ask what "support" means in the context of SQL Server.
Microsoft's own documentation on end of life support explains how it works very clearly:
Each version of SQL Server is backed by a minimum of 10 years support, which includes five years in mainstream support, and five years in extended support:
Mainstream support includes functional, performance, scalability and security updates.
Extended support includes only security updates.
End of support (also sometimes known as end of life) indicates that a product has reached the end of its lifecycle, and servicing and support is no longer available for the product. For more information about the Microsoft Lifecycle, see Microsoft Lifecycle Policy.
Tim's comments: So if you use SQL Server 2019, you should be entitled to 5 years of full support, until 2024, followed by 5 years of security updates and patches, until 2029.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I would started a database project (Accounting Application) for now Mac version which will be available in AppStore.
For future might be on iOS, Windows and web base.
I need database app that don't need the database ported to other platforms just by changing the UI and other sources I able to port it, no need to touch the database.
I'm a bit confuse to choose a suitable database SDK or etc!
Ror example I can choose:
• SQL Server
• MySQL
• SQLlite
• FileMaker
• Cocoa SQL
Remember I need:
1- Something not to complicate and easy to use it on XCode.
2- Have a bit security on the file.
3- the most XCode user using it.
4- Price is no problem.
5- Unicode fully compatible.
For my situation, which one do you recommend.
I think you're approaching the problem backwards - first you should be deciding on what development and deployment platform you want to use, and then select the best database server compatible with that platform.
What I mean by this is that whether you're using SQL Server, MySQL, SQLite, or any other faceless database engine, that doesn't answer the question of how you're going to develop or deploy the application.
You also need to decide whether to write one application for deployment on all platforms, or if you're OK with rewriting the application for deployment on certain platforms. The only technology choices I'm aware of that will work across all the platforms you've mentioned is an HTML 5 web app (using Ruby, Java, .NET, PHP, or some other web development system) or FileMaker (using FileMaker Pro for Mac / Windows / Web deployment and FileMaker Go for iOS deployment). If you're OK with writing a desktop/iOS version separately from a web version, then you need to ask yourself how many versions you want to write. If you pick something like C / C++ / Obj-C, then you're going to need to pretty much re-write it for each platform you've mentioned (although you can port from iOS to OS X with less effort than the other platforms). If you pick Java, then you're set for web deployment, Mac deployment (although you can't distribute Java apps via the Mac App Store) and Windows deployment, but you'll need to use Obj-C or HTML 5 for iOS.
So in summary, the right approach is:
Pick your deployment target(s)
Based on that choice, pick your development system(s)
Based on that choice, pick your database engine.
If its for a single user application SQLite is probably the best option - its purpose built for embedded apptications. Its also portable between os types.
I'd second the recommendation of SQLite as a lightweight database portable to multiple platforms. But what do you mean by "fully compatible" with Unicode? See: http://www.sqlite.org/version3.html
It's hard to say what you need from your description, but from what I can glean, SQLite would be the logical choice. However, if you insist on actually having a database server, you should investigate PostgreSQL. It has a far more permissive license than MySQL.
I would advise you to pick a Database Management System based on your data management requirements rather than on your choice for other components of your system. In the end almost all of them support SQL. SQLite is a good choice for a portable client-only solution. SQL-Server, MySQL, Postgres, DB2 and Oracle are optimized for server-side transaction processing (lots of inserts and updates). Vectorwise, Vertica and MonetDB focus on analytical queries (e.g., statistical analytics on your data like group by). If you make a bad choice here you might face scalability/performance issues later which may be very expensive.
So pick your DBMS based on the anticipated usage pattern.
BTW: A License for an Oracle DBMS instance can easily go up to a couple of ten thousand dollars. So be careful when saying "Price is not a problem".
I've been programming in .NET professionally for three years and am always looking to sharpen my tools. I'm a sole developer for a company that recently purchased a MSDN subscription along with Visual Studio 2008 Professional. In what ways can the subscription be useful?
I'm used to googling 80% of the day to figure out how to do what I want to do, and I've learned a ton that way. I'm having trouble seeing what the subscription gains me.
An MSDN subscription provides much more than simply an offline version of their documentation. You get access to nearly all relevant software that Microsoft makes including Windows, SQL Server, Office, etc. It also includes previous versions, as well as versions that are not yet released to the public.
It's great for testing, developing for a new platform, and for learning about new features in other Microsoft products in which you may not normally be exposed to.
The MSDN subscription isn't necessarily about access to documentation but it gives you a few key pieces of functionality.
Software licenses for Visual Studio, Office, Windows, etc.
Technical Support Incidents - For when you can't answer the question
MSDN Magazine Subscription (Yes you can get this outside of this as well)
I'm sure that there are some other things, but the license and support benefits are by far the "reasons" to have a MSDN subscription.
If you really want to grow your ability as a .NET developer the best way is to spend time around other developers using the same toolset. There are just too many tools in the .NET environment to experience them all yourself. Especially since you don't have other co-workers explorering the .NET environment with you.
If I were you, I'd check the web for any .NET user's groups located near you and attend their meetings. Those can be great places to pick up new ideas/ways of using the tools.
Among other things you get a license for Visual Studio and Office. You also get access to a wide range of operating systems and applications you may use to test your own software. For instance you may want to test your software on different versions of Windows, or if you develop software for Exchange Server you probably need to install this product without having to buy a full production license just to be able to develop software.
Which is a better choice on a development box if you primarily develop Asp.Net applications and SSRS reports. I have never had to use the Express editions, so I don't really know the pros or cons.
The cons I have listed for Standard+ editions are:
toll it takes on system resources
pain to attach database for projects
pain to detach unused databases
$$$
Pros:
You have everything you need
Management Studio features
Easy move to production
Are you talking about for your dev machine, or for production? If it's your dev machine I would just pony up the ~$50USD for the developer sku, the only caveat is to make sure you don't make use of enterprise features unless you will have enterprise in prod.
I don't have experience with the 2008 versions as yet, but I've used both the 2005 and 2000 equivalent (MSDE) on live production projects. The codebase for both of these is essentially the same as the full blown product but with restrictions on ussage and the absence of some tools - the later of which can be generally worked around with 3rd party replacements.
If the number of concurrent users is low, and the the database is unlikely to grow that large, then generally the express versions are fine. It's a little more hassle to manage than having the full edition to hand, but the cost saving is significant.
Low and that large are of course elastic, but for example we have a real estate application that runs in several offices with half a dozen users and a couple of tables with a million rows and performance and management is perfectly fine.
SQL Server Developer Edition.
The only problem you have to watch out for is that it has features not available (it basically has the Enterprise Edition features) in the Standard Edition (for example, indexed views).
So, for instance, dev edition will work much better than express on your quad-proc dev box.
http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx
Usually there is no "Best" choice, however in this case there is: SQL Server Developer Edition. Reason: It gives you everything in every other edition (except the licensing) for all of $65-$90. Seriously, any SQL developer would be crazy not to get it, it's one of the best deals in the history of software.
Other stuff that you mentioned:
System Load: this depends much more of how you use it than what edition it is. I have both 2005 & 2008 instances running on my 3 year-old 2GB laptop with no ill effects.
pain to attach database for projects: painless with developer edition.
pain to detach unused databases: same
"You have everything you need": now you have everything that you will EVER need (for 2008).
Management Studio features: Yep
Easy move to production: Yep
Honestly, at this price, employers should be giving this to all of their developers.
On the rare occasions where I am in the same situation (usually on my personal web hosting), I opt for sql express + various free or cheap third party tools to substitute for SSMS and EM.
The development editions have all the features of the enterprise editions (with some quirky exceptions, consult BOL), so it's not like the dev edition will give you fewer things to play with. You just won't be able to let any of your customers connect to your SQL developer edition, you'll have to deploy your SSRS reports to a Standard Edition production server somewhere.
If you are using SQL at work and your employer doesn't have a license for SQL Standard at all, then that sound like a licensing problem.
In short, I think the choice of edition starts with a choice of license, which is an economic and legal question, not really a feature set question. (i.e. will your planned uses be legit with your chosen license? with SQL Express and Dev edition you can't wrong-- the sql express has you covered for production use, the dev edition has you covered for being able to use the features you want, like SSMS)
Express isn't really designed for actual products - it is more to let developers familiarize themselves with the system and see if they like it, or for sample apps.
Express is free though, but if you need a free solution you might be better off with MySql.
I know just the question is a bit of heresey, but I'm curious...
Sure, there are the express editions. But when Microsoft is effectively competing for 'hearts and minds' in an OSS world, it seems more than a bit counterproductive to charge devs who wholeheartedly support .NET high subscription fees for Microsoft software. It's hard to imagine that, in the context of Microsoft's overall sales, dev licenses represent such a significant revenue stream as to justify the downsides.
So my question is: do you know of any instances where MSDN subscription rates have deterred a team from adopting .NET for a project - where cost played a role in a decision to go OSS instead?
I think MS has made huge inroads to making .Net cheaper to access and work with. With competent Express versions of Visual Studio and Sql Server, the only thing you need to pay for is Windows itself (both in your dev environment and server/production environment).
The only thing holding .Net back now is it may not be the right tool for every job regardless of cost.
It does to me. It makes me ask maybe I should try and become a Microsoft MVP because they get all the software for free.
You can't buy Expression Blend and Design for anything but the highest level on the License and that just ticks me off.
I don't think so, especially with the empower program for small ISVs -- $375 gets you 5 MSDN licenses and other goodies. After that there are Microsoft Action Packs as well as the entire partner program.
I've always gotten legal, free copies of Visual Studio. You can either download the Express versions which will handle most people's needs or go to the Launch events where they literally give out copies to everyone who shows up.
.NET Framework is a free download, so really the only thing left is a box running Windows.. and I'd be willing to bet that you've got one of those kicking around somewhere.
There's no reason to purchase an MSDN subscription.
It's not a barrier to entry, but it certainly represents a glass ceiling. You get a lot of things with the Express editions, but not EVERYTHING. There's a lot of little perks that come with the Pro versions - addins for instance +cough+ Resharper +cough+. I'd say you need Visual Studio 20xx Pro at a minimum to do any mid-range to Enterprise level development.
The cost of MS developer tools was the sole reason behind my Year of Linux. It's tough seeing all the free development tools for Linux, OS X and Java. If my job didn't depend on keeping up to date with .NET, I'd leave it for dead in a heartbeat.
In my view MSDN subscriptions are not a huge deterrant, as not only are there express editions, there are also trial versions of most products, and I think a basic MSDN subscription is not that expensive.
However licencing costs and licencing complexity of certain developer tools as well as certain products can be a huge obstacle which unfortunately is often not thought about at the beginning of projects.
I am aware of a number of projects which have chosen alternative technologies due to licencing costs and licencing complexity.
I'm currently on the Empower program but I'll be paying the full fare when it runs out
for the same reason I pay A$800/year for an AutoCAD subscription - it easily saves me more time & hassle than it costs in the long run by having everything I need at my fingertips.
I think I'm getting value for money when I consider both the licenses as well as the community - most of which I suppose is free anyway.
I consider it a legitimate cost of running my business and it's tax-deductible anyway.
I am trying to restart my career, my life, etc and my previous MSDN Universal sub expired in 2005. At the time it expired, I stopped working for a while. That coincided with Microsoft changing the cost and structure of that subscription program. To acquire a similar subscription today is out of the question. I do not have the funds. I am currently developing with old technology (VB6 and ASP) and will do so until I have the funds to purchase the MSDN sub that I want. I have downloaded the "express" versions of VS 2008 and SQL 2008 but, lets be frank, any serious developer is going to want to utilize the features that arent available in "express". In exploring this issue here on StackOverflow, I have seen others talk about the Empower program. It looks promising and I shall investigate it.
But, yes, the barrier to entry is the cost. Hopefully Empower lowers that, for a while. I agree with the requirement that after it expires I will need to pay full fare. I think thats only fair.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As a long time Microsoft developer, I find MSDN to be an invaluable resource.
However, when tinkering at home I am not able to play with the best latest technologies and the different offerings coming from Microsoft as I cannot justify paying such a hefty price for what is essentially a pastime.
The Express editions are great, but fall flat when trying to use the more advanced feature I am used to from the versions I use at work. I cannot get the latest betas and play with the new offerings, not legally, anyway.
Apart from getting an MVP, how would one go about getting an MSDN subscription for an acceptable price for a non-professional environment?
I am aware of the Empower program, but I thought it was geared towards getting commercial software to market. If this is not the case, it appears like the way for me to go. Thanks!
MSDN subscriptions are per user rather than per device so as long as you're the only person using them I think you should be free to use them at home. I'm not aware of any differentiation being applied to the workplace, unless of course your workplace itself lays down such a rule.
From http://msdn.microsoft.com/en-gb/subscriptions/aa948867.aspx:
MSDN Subscriptions are licensed to
individuals who may install the
provided software without restriction.
Software provided through MSDN
Subscriptions is licensed for design,
development, test and demonstration of
your applications.
See also http://msdn.microsoft.com/en-gb/subscriptions/aa948864.aspx.
There is an Empower program that Microsoft has available. It gives you several Premium subscriptions for cheap, with the catch that you have to be an ISV working towards an actual product.
This (Not available anymore - broken link) gives you all the software you'll need for development, and even a few "real world" licenses for certain apps (like Office)
After a couple of years, you have to pay full price though. The logic being that you should have a product on the market, and can afford it.
+1 Luke's comment about using work MSDN license at home. I think that's the best answer for the OP.
Also consider
DreamSpark (for students): http://www.dreamspark.com
BizSpark (for startups building "next gen web apps"): http://www.bizspark.com
Empower (for ISVs wanting to partner with Microsoft): http://www.empowerforisv.com
(Note there is some overlap between BizSpark and Empower ... many ISVs will find them both useful)
And finally ... don't overlook trial versions and VHD's. Most Microsoft software is available for trial (30-360 days). Many are available via the "VHD Test Drive"
VHD Test Drive: http://microsoft.com/vhd
Check out the Microsoft Action Pack Development and Design subscription. It is designed to replace the Empower program and gives you access to some MS products at a great price point.
https://partner.microsoft.com/global/40132997
In agreement with comments already made - get an Empower subscription, it's geared up towards people like yourself. As I recall, you have 2 years to bring a product/solution to market (where market is very loosely defined) that uses some element of MS technology (again, where this is quite loosely defined). In return for quite a modest outlay, you get MSDN, a bunch of OS licenses and access to development tools and end-user application programs (XP, Vista, Office being obvious examples).
For instance, I develop in Delphi but write code to run on SQL Express 2005 and full-blown SQL Server 2005+, and this entitles me to purchase an Empower agreement. I get all the goodies, plus things like Visual Studio, SQL Server, Office and OS licenses. If you don't bring a solution to market in the time allocated, you can pay to extend your agreement or... well, I must admit I'm not sure. It's hard to see what bad thing can befall you if you try to produce something but ultimately fail - it's the American dream, right? You have to stop using the software at the end of the period, etc. :-)
If you want to develop for desktop Windows you really need some level of MSDN access, or a good broadband connection and some patience while you access the online materials. Empower is a fairly pain-free method of getting your hands on all the best tools for very little outlay indeed - you end up with a large pile of DVDs and CDs, and a few updates during the year. I'd say it was an essential purchase - particularly if this is viewed as a career investment, or some element of training or progression. It's not a lot of money at all (I speak as an ISV - everything I have to pay out truly comes from my pocket!).
You may want to talk to your boss about your opportunities to join MSDN for free. I work at a company using all Microsoft Software, and I get a free subscription, which comes with access to almost all of microsoft's software.
If you have an MSDN subscription at work, odds are good that your subscription license has a provision for you to be able to install things at home as well.
I know with our subscriptions here I'm allowed to install copies of operating systems and development tools at home since I obviously can't use the copies at work and at home at the same time.
Edit: I'm assuming that since you said you were a longtime MSDN developer that you are currently employed doing development on Microsoft platforms.
Even with just one licence you can get MSDN Under a Volume Licence. This is cheaper and (depending on exactly which VL program) can allow the cost to be spread across the VL period (once fully paid the licences become permanent).
Also means you get the VL builds and keys for Office/Windows rather than just the retail.
Many MVP's have gift subscriptions that they can give away, so it pays off to be visible in the community.
Speak at your local user group, start (or participate) in an open source project, start a blog... just generally get your name out there.
Eventually you'll get one (or an MVP :)).
What I've found is that if you pay attention there are plenty of opportunities to snag a free copy of Office or Visual Studio at local Microsoft events.
Good luck!