Install Vuze ISO on pre-existing vitual machine - sql-server

I have an SAP environment on a Vuze Windows 2012 R2 VM and the when i start the ECC the disp+work.exe fails and stops. This is because SQL Server 2014 "Standard" is installed and SAP only support "Enterprise" editions of SQL Server - as per note 63988.
My Microsoft Partnership is not valid for an enterprise key so I have an option to deploy with Vuze. Though the only option I see is to deploy SQL Server 2014 Enterprise as its own VM not actually install it on the existing VM.
Does anyone know about deploying the ISO's on Vuze to an existing VM or if I do deploy SQL Server 2014 as its own VM, will I be able to point SAP on VM "Y" the the SQL Server on VM "X"?
Thanks for any help

my MSDN subscription finally came through and now i have access to an Enterprise download =D

Related

How to migrate collections from TFS 2017 to Azure DevOps Server 2019 (Different DB servers)

I have been handling an aging Windows Server 2008 machine with TFS upgraded in place to 2017.2. Now, with Azure DevOps Server 2019, support for Windows Server 2008 is no longer available. Also, the existing SQL Server is 2012 and is no longer supported as well. I cannot upgrade the database to SQL Server 2014+ as there is the OS restriction. and in our company, upgrading OS in-place is not allowed.
Existing setup is as follows:
Windows Server 2008 (One VM)
TFS 2017.2
SQL Server 2012 Ent (On same VM)
Non-HTTPS machine name URL Team Portal access over Intranet
I prepared a brand new Windows Server 2016 for the Azure DevOps 2019.0.1. I also was able to get hold of a SQL AlwaysON Cluster based off SQL Server 2017 Ent just for Azure DevOps.
If I proceed with DevOps setup, I'll target the new DB Cluster and it will set up the new DB accordingly.
How do I move my existing collections to the new cluster (easy: restore DBs on the new cluster)?
Will Azure DevOps just accept the new collections?
All migration topics I've read are always assuming DB server and TFS server are the same and do not change.
Ideal path:
Install the SQL Server matching your original environment.
Attach the databases
Install a version of TFS that supports your SQL server version that is the same or newer than the original server.
Walk through the configuration wizard.
uninstall TFS server
Detach databases and uninstall SQL Server
Install the desired SQL Server version with the same instance name.
Attach databases
Install latest version of Azure DevOps Server
Walk through the Upgrade wizard.
Full details here:
https://devblogs.microsoft.com/premier-developer/move-or-clone-tfs-from-one-hardware-to-another-in-tfs-2017-2018/

Unable to run Reporting Services 2017 on Azure instance running SQL Server 2017 Web edition

I'm running this version of SQL Server on an Azure instance:
Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Aug 22 2017 17:04:49
Copyright (C) 2017 Microsoft Corporation
Web Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)
Per the description for the instance ('SQL Server 2017 Web on Windows Server 2016'):
This image contains the Web edition of SQL Server 2017 on Windows Server 2016. This provides a low-cost database solution for medium-size web applications. It includes the core database engine and Management Studio for integrated administration and development. Also includes basic versions of Reporting Services for web reports, Integration Services for moving and transforming data, and Analysis Services for data mining. We recommend that you use a virtual machine size of DS12 or higher.
When I attempt to connect / configure using the 'Report Services Configuration Manager', I'm unable to 'find' the Report server instance in the 'Reporting Services Configuration Connection' dialog. I.e. the 'Report Server Instance' had not values to choose from.
I installed Microsoft SQL Server 2017 Reporting Services (note three editions were available - Eval, Developer, & Express - tried each edition - uninstalling each version before trying the next)
When I went to configure the Reporting Services using the 'Report Server Configuration Manager' I got to the 'Change Database' tab. At the point that I am assigning the database engine to the reporting services I get the error:
The database engine instance you selected is not valid for this edition of report server
Note I'm running the Web edition of SQL Server, but I'm not seeing an option to select that in the installation of the report services
Thoughts re what I'm missing?
I Ended up reverting back to SQL 2016 to go around the issue
I have been having a similar issue. I tried to get the SQL Server key from a PowerShell script as well, but they didn't work for SQL Server 2017 Web Edition.
So the solution was much easier than I expected.
Go to the C: drive of your VM. You will find SQL Setup there.
Run the setup to start a new standalone installation. When you will be on product key page it will display the License Key.
Copy that key and put it into your Reporting Services Installation.
I hope it will help someone.
The error is basically saying you cannot use the edition of your SQL Server Engine (in this case, Web edition) for SQL Server Reporting Services 2017. Can you try a different edition of SQL Server?
Update:
You can learn more about supported editions of Database Engine you can use for each different type of edition of Reporting Services 2017 at https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-features-supported-by-the-editions-of-sql-server-2016. While some of the content may not be applicable for SSRS 2017, the bits which are applicable are still accurate.

Azure SQL Server VM with personal SQL Server production key

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.

Missing Integration Services Catalog in Management Studio

I have SQL Server 2008 R2 SP3 standard edition installed. I access remote to the server where SQL Server is installed. The option of the integration services catalog is missing under the database connection.
I did check the followings
I have the role sysadmin when I log in SQL Server
The service of integration services is installed and running.
The installation of the management studio is complete
I am missing the Microsoft SQL Server Integration Services when I run the Dcomcnfg.exe under Services, Computers, My Computer, and DCOM Config. Weird I am missing this. I wanted to find this to give appropriate permissions, but can't since the node is not there.
Any ideas? Help!
That's because you're using SSMS 2008. The Integration Services Catalog was introduced with SQL Server 2012. The older client doesn't know that's a "thing."
I prefer to manage servers with the latest and greatest version of SSMS which is now a free download.
Microsoft® SQL Server® 2014
Choose "MgmtStudio 32BIT\SQLManagementStudio_x86_ENU.exe"
For clarification
Integration Services Catalog
Integration Services Object Explorer
I had the same problem, Integration Server Catalog is invisible
This is my solution:
Check your installation edition of SQL Server.
How to check? right click on the node of (SQL Server...) on SSMS - click properties - in "general" check the "product" name.
If you still use "SQL Server Developer Edition", some features will not available.
the solution is download SQL Server Enterprise Edition.
I have no idea for Standard Edition, but maybe you can also use Enterprise Edition.
This is link for download : download SQL Server 2014
Click setup.exe to install and choose New SQL Server Stand-alone Installation select the feature you need. I think you can also select Integration Services in Feature Selection.. then fill the instance name and instance ID. continue the installation process until complete.
Open SQL Server Management Studio. Database Engine connection -> Server Name: (Server Name) / (Instance ID)
You will see the Integration Server Catalog. In the picture bellow, you can compare the display between SQL Server Developer Edition (above) & SQL Server Enterprise Edition (bottom with instance name).
I hope it can help..
Final result:
I got same issue and i have installed SSMS 17.0 and now i am able to create the SSISDB catalog with encryption password.
It's working as expected.

Microsoft Azure + SQL Database

How can i create a SQL Server 2008 SQL Database with microsoft azure.
Looks like it is defaulted to
productversion : 11.0.9214.43
productlevel : RTM
edition : SQL Azure
Please help me
SQL Azure is a cloud service version of SQL Server. You can't opt to use different versions of it (and it's actually slightly different to the regular server hosted version of SQL Server)
If you need a specific version of SQL Server hosted in Azure, you'll need to create a Virtual Machine and run it there.
Have a look through the VM Gallery to see if they have a pre-built VM Image with SQL 2008 installed,
Alternatively, spin up a Vanilla Window Server VM, and install SQL Server yourself.

Resources