I've been doing this for 3 days. I couldn't find the solution. Normally it was supposed to have features like the following.
What is the cause of this problem? And how do I solve it?
You're using SQL Server Express. SQL Server Express is a very cut down version of SQL Server and does not provide anywhere near as many features as Standard and Enterprise; such as database mail (Additional Database Services). If you need features, you need to purchase SQL Server and pay for the edition licences that have the features you need.
If you are using SQL Server for development purposes only, you can use SQL Server Developer Edition, which is allowed to be used for non-production environments only. Developer edition has all of the features that Enterprise does.
You can find the full list of features supplied by each edition here: Editions and supported features of SQL Server 2017
Related
After install I wanted to practice creating SQL Server Agent jobs, I know that you cannot do this on a SQL Server Express instance, so I'm wondering with my developer edition if it's possible to create a non-SQL Server Express instance, and if so how, thanks.
Please check following tutorial which shows SQL Server 2016 installation step by step
In general for all SQL Server versions the setup procedure is very similar.
You can exclude installing components like Reporting Services, Integration Services, Analysis Services and other optional components if you want to make the setup process simple
What you should install is Database Engine Services! You can exclude the other features under Database Engine if you check the screenshot I shared in the article.
And what is important is the Management Tools that you can use to connect db instance and execute queries, etc.
Although the above tutorial shares the download link, you can also refer to https://www.microsoft.com/en-us/evalcenter/evaluate-sql-server-2016 for SQL Server 2014 and 2012 download links as well
So I realized that I only had SQL Server 2012 Express edition by using:
SELECT SERVERPROPERTY('EDITION')
Using the link provided by Eralper I installed SQL Server 2014 developer edition and now have two instances of SQL Server, one is the the express for 2012, the other is the 2014 developer edition. Once I log in to the named instance I can finally see of course the SQL Server Agent node at the bottom.
Thanks everyone for all the help and sorry for the confusion.
I'm currently in the process of coming up with our upgrade plan for our migration from SQL Server 2005 to SQL Server 2012, and some of our business units still use ProClarity.
I'm aware that this is essentially a "dead" application; where Microsoft isn't upgrading it anymore, and it's scheduled to be EOL'ed in the future.
After googling and digging around on Microsoft's forums, I still can't come up with a definitive answer as to whether the 2012 upgrade will be incompatible with Proclarity. (Business users are on 6.2; which is one minor revision behind)
Has anybody tried this out and been successful? Would we need to keep this portion of the BI tools on SQL Server 2008?
Upgrade was successful, and the users were able to connect to 2012 Analysis Services using ProClarity
I was wondering if we could backup the database that we currently host on regular SQL Server, and put it onto our clients computer when we setup SQL Server Express for them.
Is this possible?
Thanks,
Matt
Yes, it's possible to restore a database backup from the Standard edition to the Express edition. It's not possible to restore a SQL Server 2008 to a SQL Server 2005 version, though.
However, there a some minor differences between versions. I've noticed an issue in SQL Server Express 2005 when calling .NET SQL CLR functions across databases, so your mileage may vary. I haven't been able to find a good overview of the exact differences between the various SQL Server editions.
It's always best to keep the development platform as close as possible to the release platform. I can only recommend that you use the Express edition of SQL Server for development as well; and re-test your application.
I've been trying to work out whether it's possible to manage (i.e. add tables, modify them, create stored procedures) a SQL Azure database using some kind of GUI like SSMS and I keep coming up against different answers.
I found a post from the end of 2009 saying that it would be supported in SSMS but I'm not sure if that includes the Express version? Does anybody know what the most recent update of the express version is and whether it supports it?
I think I'm right in saying that it can't be done in Visual Web Developer 2010 (and I can't afford the full fat VS2010).
I'm prepared to consider alternatives though if anybody knows any full features GUI tools that work with SQL azure and I don't mind paying for a commercial license if it's not too expensive.
Thanks.
Yes, SQL Server 2008 R2's Management Studio does support working with SQL Azure databases.
See:
Getting Started with SQL Azure Development
There are a couple of options
1) You can use SSMS (get the free version by downloading SQL Express v2008 or greater) with advanced services. This will give you SSMS. You can then connect to SQL Azure using SSMS. However - there is a limited set of functionality available via this tool.
2) You can use SSDT (stand-alone for free) or from within VS2010 SP1 or greater. Again, you can connect to SQL Azure, but there are some restrictions on what you can do.
I am using the SQL Express on AWS RDS (free usage tier) myself lately (and connecting via SSMS or SSDT). I prefer their implementation of SQL Server in the cloud to Microsoft's implementation of SQL Azure.
I want to use SQL Profiler to trace the queries executed agains my database, track performance, etc. However it seems that the SQL Profiler is only available in the Enterprise edition of SQL Server 2005. Is this the case indeed, and can I do something about it?
You don't need any SQL license to run the client tools (Management Studio, Profiler, etc). If your organization has a copy of the installation media for Developer, Standard, or Enterprise, you can install the client tools on your local machine under the same license.
If you're working solo, I would recommend purchasing SQL Developer edition, it's only $50.
If you are open to using third party profilers, I have used xSQL Profiler and it performed well enough.
The SQL Profiler tool is only available with the Standard and Enterprise version of SQL Server, however, all version can be profiled using the tool.
Source: http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
Client tools are not licensed separately. So you can download the evaluation edition of SQL 2008 R2 and use the client tools from it (the client tools will still work even once the eval expires and the engine is no longer usable).
You must be licensed in some way for each sql server you connect to but that is not the same as requiring a license to use the tools.
You can use SQL Profiler on both Standard and Enterprise editions, but you will need certain rights to run it (you need to have sa rights or be granted ALTER TRACE permissions)