Right now I have the express version and I need some automated work done and thus, I need the agent in my SSMS, my question is:
Which edition has the agent? On the website I've seen...
Enterprise,
standard - per core,
standard - server + CAL,
Developer,
Web,
Express
SQL Server Express doesn't support SQL Server Agent.
SQL Server Enterprise, standard, Developer, Web all support SQL Server Agent.
By the way, You can also see the SQL Server Agent Service of the SQL Server Express instance in the Sql Server Configuration Manager. But you can't start it. You will get the error message like the below picture.
Related
Recently, a tech support specialist installed SQL Server 2016 Management Studio in my computer. When I asked about the possibility of using integrated R services in SSMS, he said I need to have stand alone SQL server installed in order to use that feature (which is not going to happen as individual license is pretty expensive).
Can somebody shed some light on using R services from SQL server 2016? Do I really need stand alone SQL server? or there is a workaround?
Thank you
poshan
SQL Server 2016 Management Studio is a client tool that connects to the Microsoft SQL Server 2016. If R-service already installed (as part of setup wizard, if you have chosen Database Engine Services and R-Services (In-Database)), you can connect to the SQL Server and execute R-script from Management Studio setup in your machine.
Some useful documentation:-
https://msdn.microsoft.com/en-us/library/mt696069.aspx
I am setting up a new SQL Server 2014 Enterprise Reporting Services instance on a Windows Server 2012 R2 server.
In Reporting Services Configuration Manager, when I select the SQL Server instance where I want to setup a new report database, the error message below is shown:
The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.
Error:
The SQL Server instance where I intend to setup the report database runs SQL Server 2014 Developer Edition build 12.0.4422 (which is displayed in Management Studio and ##version) and the SQL Server instance where I am configuring Reporting Services runs also MSQL 2014 build 12.0.4422 as displayed in Reporting Services Configuration Management - but Enterprise Edition (I've just installed SQL Server Cumulative Update 2 from https://support.microsoft.com/en-us/kb/3075950).
If I select an instance which runs SQL Server 2008 R2 Enterprise Edition build 10.50.4260 instead, the error is not shown and the setup proceeds correctly - but unfortunately this is not the instance where the report database should be.
What am I missing here? How can I solve this issue?
Thanks in advance,
Cristhian.
This behavior is correct. The reporting services database is supported on a wide range of versions.
You are not allowed to use a production reporting services against a developer version database. (Why would you want to!). You can either use a developer edition of reporting services, or an enterprise database.
I have a phone server running Window Server 2008. The server software is currently using Microsoft SQL Server 2012 Express Edition. I created an IVR application that has created a second database using the same SQL Server instance.
I found out post-development that the version of SQL Server installed on the server was Express and NOT Standard like I had thought. I checked the SQL Server Configuration manager and noticed that the instance is MSSQLSERVER, but it is running express. The phone system software I am using is proprietary and I cannot get in to change/modify connection strings.
My question is:
Is it reasonable to assume that upgrading from SQL Server 2012 Express to SQL Server 2012 Standard is safe? Does upgrading change the connection string, or instance name? Or is there anything I should be aware of during the upgrade? Or would it be better to just run Standard alongside Express?
Thanks!
I have read various articles saying that the connection string doesn't change, but I would like some input from someone who has actually upgraded from Express to Standard.
I created an Azure SQL Server Standard VM. As the price page showing, VM with SQL Server installed will charge additional SQL Server fee.
Now I found I have a SQL Server Enterprise key. After I upgrade my pre-installed SQL Server Standard version to Enterprise version, will I still be charged the SQL Server fee?
Thanks
After I upgrade my pre-installed Standard version Sql server to
Enterprise version. Will I still be charged the Sql Server fee?
Yes.
If you want to use your own key, you have to strat from a regular Windows Server VM (and not SQL Server VM). Then, on top of that Windows Server, you install your version of SQL Server with your key.
I think its a strange question but my problem now that I ordered from my organization to buy a license for SQL Server Enterprise edition, but after they made order I found that I only need SQL Server Enterprise Manager just to manage my DB during developing a asp.net website.
So can I ask the organization to return SQL Server Enterprise Edition back or is it impossible? And do I need to buy SQL Server Enterprise manager or there is a free version online?
Enterprise Manager is the SQL Server 2000 GUI client tool. No server side components. No database engine, no analysis services, no reporting services.
Enterprise Edition refers to the server side components feature level (has more than Standard, Workgroup). This is separate to the the GUI/client components.
Enterprise Manager has been replaced by "SQL Server Management Studio" ("SSMS") since SQL Server 2005. This can manage all editions