Hi Guys,
I am going to start one new project as a freelancer. I want help to decide which version of SQL Server should I use. Either Sql Server 2012 Express Edition or Sql Server 2014 Developer Edition.
I can purchase Developer Edition as it is not costly.
The problem is Express edition don't have SQL Job Agent and on Microsoft Website it is said that Developer Edition cannot be used on production.
Please help me deciding what should I prefer.
Developer Edition can't be used in production, so that's a non-starter. That leaves you with a) Express, or b) springing for a better licence and buying Web edition. It really depends on what you want to use the agent for, if its just backups there are other tools available, but you will more than likely want to perform other maintenance tasks (history cleanup, reorganizing indexes etc)
Have you considered Windows Azure? You could set up a SQL Azure Database instance, which you could combine with Azure Automation to perform your jobs?
Related
The question comes as the Express version has a cap of 10 gb which my database is over. If the SQL Server Developer edition only allows certain amount of connections, would have a Windows server on another machine allow this to count as only 1 connection. If anyone has experience with a similar setup and can tell me about the experience. Looking to understand the cost of $4000 for SQL Server Standard version to the Developer version which seems to be have more features.
Literally answering your question, you can run SQL Server Developer Edition on a production server, however you should not. You will be in violation of Microsoft's Licensing terms:
SQL Server Developer Edition
SQL Server 2017 Developer Edition is a
fully featured version of SQL Server software—including all the
features and capabilities of Enterprise Edition—licensed for
development, test and demonstration purposes only. SQL Server
Developer Edition may not be used in a production environment or with
commercial data. Any test data that was used for design, development
or test purposes must be removed prior to deploying the software for
production use.
Get the whole story At Microsoft's SQL Server Website
What edition of sql server contains all BI , analysis, integration, reporting.
Does the install of SQl server for BI create a report database, reportdatabase tempdb and does analysis and integration need database components.
I guess I asking what do I need to install to get a sql server database running with BI. Is it just sql server and SSDT tools or during the install of SQL Server do I need to select analysis, reporting, etc
There are four editions of SQL Server (as of SQL Server 2017) - Enterprise, Standard, Web and Express (Developer is Enterrpise, is free (sometimes there is a $50 media fee but cannot be used in production). All four support Reporting Services.
Please see the following link https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-features-supported-by-the-editions-of-sql-server-2016?view=sql-server-2017
If you are going to run SSRS and SSDT do yourself a favor and select these products during the install. Initially the databases are not that large. You probably can run SSDT from the command line without the install but you will run into all kinds of unnecessary issues if you don't install it. You can turn off the service if you are not using that feature.
BI is fully supported in Enterprise and many of the features I have used are available in Standard. Please see the following to compare editions for BI:
https://learn.microsoft.com/en-us/sql/analysis-services/analysis-services-features-supported-by-the-editions-of-sql-server-2016?view=sql-analysis-services-2017&viewFallbackFrom=sql-server-2017
I have installed on my computer SQL Server Express Edition (2014 I guess), and I have a project who suppose to create a backup for a DB. But I found out from the internet that the Express Edition doesn't have the Maintenance Plan from the Management Folder or the SQL Server Agent. So I want to update this edition with another edition who will have all of these but I don't know why, can you help me, please? I don't want to pay for the new edition because this project is for school and then I don't know when I will use SQL Management Studio. Thank you!
PS:When I make upgrade I don't want to lose my DBs!
If you just need backups, you do not need to upgrade the edition.
You can use Ola Hallengren maintenance solution and run the commands from the Operating System Scheduled Tasks.
Here are the instructions: How do I get started with the SQL Server Maintenance Solution on SQL Server Express?
I use this for all my Express installs and it works fine.
We need to use SQL server snapshots for some automated tests and also for rollback purposes in case our Database Upgrades in Production systems goes bad. We were planning to use DB snapshots feature in SQL server 2008.
To be able to test all our processes and code in our development environment. We were trying to use it on SQL server 2008 developer edition which seems like it has all the features of enterprise edition but we ran into some problems with using DB snapshots.
Is this a feature that is really exclusive to Enterprise edition or do we need to make some setting changes to use this on Developer edition.
I've had no issues using developer edition with snapshots - our unit tests use them to do more efficient data tier tests.
What is the best (or THE) way to change my SQL Express 2008 (with advance...) installation to a 2008 Developer edition?
I need to keep the databases, along with the logins and so on.
I need to upgrade because, I Want to use all the features in TFS 2010.
Do I have to make backups of all the data and uninstall express - install developer?
Is there a quicker way?
SOLVED:
In the SQL Server Installation Center, there a Edition Upgrade options found under Maintenance. The only thing is that you have to choose processor type as x86 (as Express is only x86) in the options in the Installation Center. Now my SQL Server is developer.
We had to do the same thing at one time. I think we simply backed up our database(s) and the master and msdb databases as a precaution, to restore if we had to, which I don't think we did.