I am thinking to join MS Action pack subscription.
Does anyone have a list of the exact software I can use?
I am very interested in MSSQL 2012/2014 as I have a dual quad core machine (8 cores) and wanted to know if I can run MSSQL 2012 or 2014 on it with my Action Pack License.
Shame Microsoft can't make this information easily discoverable on their website. Here is a link which I eventually found with Google, which will probably break within 2 months, because that's how Microsoft roll....
https://mspartner.microsoft.com/en/us/pages/membership/downloads/software-licensing-for-action-pack-subscription-partners.aspx (seems to be dated 2014, PDF main points copied below)
Windows 10 Enterprise (Current Branch or 2015 Long Term Service Branch) (Upgrade Only)
Microsoft Desktop Optimization Pack 2015
Windows Embedded 8.1 Industry Pro
Windows Embedded 8.1 Industry Enterprise
Windows Embedded 8 Standard
Windows Embedded 7 Standard
Windows Embedded POS Ready 7
Microsoft SQL Server 2014 Standard
Microsoft SQL Server 2014 client access licenses (CALs)
Windows Server 2012 R2 Standard
Windows Server 2012 CALs (not edition specific)
Windows Server 2012 Remote Desktop Services (RDS) CALs
Windows MultiPoint Server 2012 CALs
Windows MultiPoint Server 2012 Premium
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows Storage Server 2012 R2 Workgroup
Microsoft Office Professional Plus 2013
Microsoft Project Professional 2013
Microsoft Visio Professional 2013
Microsoft Exchange Server 2013 Standard
Skype for Business Server 2015
Microsoft SharePoint Server 2013
Microsoft Dynamics CRM Workgroup Server 2015
Microsoft System Center 2012 R2 Standard
Microsoft System Center 2012 R2 Client Management Suite Client MLs
Microsoft System Center 2012 R2 Configuration Manager Client MLs
Microsoft System Center 2012 R2 Endpoint Protection
3 Visual Studio Professional licenses
To get the Action Pack you have to become a Microsoft Partner. Then there are two packs. The developer pack definitely includes SQL Server.
Dig around on the Partner web site and you should find the details.
Related
I'm trying to move to a new hosting provider and I'm having real difficulty getting my web site to run. It uses Hangfire on application startup to run some background jobs, whilst also serving web pages on the main thread.
The website seems to work for the very first page load and then subsequent accesses fail to run a reasonably complex Entity Framework search query.
Here's the server's configuration on the existing machine, via SQL Server's select ##version command:
Microsoft SQL Server 2017 (RTM-GDR) (KB4583456) - 14.0.2037.2 (X64) Nov 2 2020 19:19:59 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: )
Shared operating system (not sure what this is)
SQL Server 2017 - Standard Edition
.NET Framework 4.8
Hangfire using SQL Server storage, with table's using the Hangfire schema
Other application tables, with tables using the dbo schema
Here's the server's configuration on the new machine, via SQL Server's select ##version command:
Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Express Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)
Windows Server 2019
SQL Server 2019 - Express edition
.NET Framework 4.7,. (according to Plesk, although I've installed 4.8)
On the new server I have full RDP access, so can install whatever software I like on this machine. However, SQL Server Standard edition is extremely expensive for a little website like mine.
Is there something that is preventing the Entity Framework query running on the new Windows Server 2019 machine, with SQL Server Express? Does that combination not allow multiple schemas for the database, or is there some other restriction from this combination that I might not be aware of?
Running the website with SQL Server Express on my local Windows 10 machine runs fine.
I'd really appreciate any help with this, as I'm pulling what little hair I have left out of my head!
Thanks for trying to help, but in the end the problem was a lot simpler than I'd anticipated. I thought this was a permissions issue, but actually it's just a simple performance issue.
Running SQL Express on the new server failed because the machine didn't have enough RAM. It only had 4GB of RAM, and with Plesk and other software installed by the hosting provider, the free RAM was down to just a few hundred MBs.
Some simple queries that would take milliseconds to return on the old server could take over 2 minutes to return on the RAM limited new server.
Increasing the RAM to 8GBs fixed most of the issue, although using SQL Express is still significantly slower than the SQL Standard edition on the old server, and SQL Standard is alarmingly expensive to run just for this one website (the old server has a shared SQL Standard edition installation).
There was a need to upgrade SQL Server 2008 to SQL Server 2016 on a Windows Server 2008 R2 64 bit, so when I started the installation of SQL Server 2061 Express SP2 using
SQLServer2016-SSEI-Expr.exe
on Windows Server 2008 R2 64 bit SP1 there was a note on the first window:
Note: your Operating System is not supported by SQL Server 2016.
You may download the installation media but you will not be able to install it on this machine. For more information see this link:
https://go.microsoft.com/fwlink/?LinkId=826321
What can be done to solve the problem?
Looks like SQL Server Express 2016 isn't supported in Windows Server 2008 https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server?view=sql-server-2016
You'll either have to upgrade your windows OS, or keep your current SQL Server version.
Below is a list of windows OS' that can support SQL Server Express 2016.
SQL Server Express Windows Server 2019 Datacenter
Windows Server 2019 Standard
Windows Server 2019 Essentials
Windows Server 2016 Datacenter
Windows Server 2016 Standard
Windows Server 2016 Essentials
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows Server 2012 Datacenter
Windows Server 2012 Standard
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows 10 Home
Windows 10 Professional
Windows 10 Enterprise
Windows 10 IoT Enterprise
Windows 8.1
Windows 8.1 Pro
Windows 8.1 Enterprise
Windows 8
Windows 8 Pro
Windows 8 Enterprise
The error is telling you the problem, Windows Server 2008 is not supported by Microsoft SQL Server 2016. As per Hardware and Software Requirements for Installing SQL Server - Processor, Memory, and Operating System Requirements: Principal Editions of SQL Server, SQL Server 2016 can be installed on:
SQL Server Enterprise:
Windows Server 2019 Datacenter
Windows Server 2019 Standard
Windows Server 2019 Essentials
Windows Server 2016 Datacenter
Windows Server 2016 Standard
Windows Server 2016 Essentials
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
SQL Server Standard:
Windows Server 2019 Datacenter
Windows Server 2019 Standard
Windows Server 2019 Essentials
Windows Server 2016 Datacenter
Windows Server 2016 Standard
Windows Server 2016 Essentials
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
SQL Server Developer:
Windows Server 2019 Datacenter
Windows Server 2019 Standard
Windows Server 2019 Essentials
Windows Server 2016 Datacenter
Windows Server 2016 Standard
Windows Server 2016 Essentials
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows Server 2012 Datacenter
Windows Server 2012 Standard
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows 10 Home
Windows 10 Professional
Windows 10 Enterprise
Windows 10 IoT Enterprise
Windows 8.1
Windows 8.1 Pro
Windows 8.1 Enterprise
Windows 8
Windows 8 Pro
Windows 8 Enterprise
SQL Server Express:
Windows Server 2019 Datacenter
Windows Server 2019 Standard
Windows Server 2019 Essentials
Windows Server 2016 Datacenter
Windows Server 2016 Standard
Windows Server 2016 Essentials
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows Server 2012 Datacenter
Windows Server 2012 Standard
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows 10 Home
Windows 10 Professional
Windows 10 Enterprise
Windows 10 IoT Enterprise
Windows 8.1
Windows 8.1 Pro
Windows 8.1 Enterprise
Windows 8
Windows 8 Pro
Windows 8 Enterprise
Windows Server 2012 R2 Foundation
Windows Server 2012 Datacenter
Windows Server 2012 Standard
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows 10 Home
Windows 10 Professional
Windows 10 Enterprise
Windows 10 IoT Enterprise
Windows 8.1
Windows 8.1 Pro
Windows 8.1 Enterprise
Windows 8
Windows 8 Pro
Windows 8 Enterprise
Windows Server 2012 Datacenter
Windows Server 2012 Standard
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows Server 2008 (R2) is not one of those Operating systems.
In truth, this is another reason you should be upgrading. Windows Server 2008 (R2) support runs out on January 14, 2020, that's only 7 months away. You should be looking at changing now, so that you can iron out any kinks before you move your production server.
I have an SSIS project in VS:
Microsoft Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01590
SQL Server Data Tools 14.0.61116.0
Microsoft SQL Server Data Tools
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 13.0.1601.5
Project > Properties > Configuration Properties > Deployment Target Version > TargetServerVersion = SQL Server 2016
I deployed and validated successfully on two SQL server instances, but cannot on a third.
The chief difference I see in the three instances is this:
First (success)
Microsoft SQL Server 2016 (RTM-GDR) (KB4019088) - 13.0.1742.0 (X64)
Jul 5 2017 23:41:17
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows Server 2012 R2 Datacenter 6.3 (Build 9600: ) (Hypervisor)
Second (success)
Microsoft SQL Server 2016 (RTM-GDR) (KB4019088) - 13.0.1742.0 (X64) Jul 5 2017 23:41:17 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows Server 2012 Datacenter 6.2 (Build 9200: ) (Hypervisor)
Third (failed)
Microsoft SQL Server 2016 (SP1-CU5) (KB4040714) - 13.0.4451.0 (X64) Sep 5 2017 16:12:34 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Datacenter 6.3 (Build 9600: ) (Hypervisor)
I have been unable to track down fixes for the errors via Google, and they seem to be the same as when I target SQL Server 2014. I can post those as an edit if necessary, but my suspicion is the Sql Server installation (perhaps an issue specific to the Enterprise edition or something otherwise missing from that install) and not my package based on the above.
Here are the first and likely most relevant errors:
I found that this error goes away if you deploy from within Visual Studio instead of the wizard that is output by the build. However, I don't think you can connect to remote SQL Server instances when deploying from Visual Studio (I think that a Windows login is required).
So the solution was to install SSDT (Visual Studio 2015) on the production machine and deploy locally. This is obviously not great because you then have to move the SSDT project to the target machine every time you want to deploy (i use Git for this).
I'm sure Microsoft will come up with a fix for this eventually... Although at the moment I'm still waiting for them to release SSDT for Visual Studio 2017.
=== EDIT October 2017
SSDT is now available in Visual Studio 2017. However, I found that I still had to deploy from a locally running Visual Studio (but I can't remember why since having tried this a couple months ago from VS2017)
I am trying to add Reporting Services – SharePoint feature to my computer sql server installation.
I am currently using Sql Server 2012 Enterprise on a 32 bit computer
Microsoft SQL Server 2012 - 11.0.2100.60 (Intel X86)
Feb 10 2012 19:13:17
Copyright (c) Microsoft Corporation
Enterprise Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)
Unfortunately, in Shared features I don't have the Reporting Services items mentioned in this article:
http://msdn.microsoft.com/en-us/library/jj219068.aspx
Could it be because I don't have Sharepoint installed on my computer?
Or maybe, because my computer is 32 bit?
Any suggestions?
Thanks
I think you have 64 bit computer Reporting Services Add-in for SharePoint Products says
computer must meet the following software requirements
The add-in is 64-bit only, which is a requirement of SharePoint 2010
products and technologies.
In this article you can check Report Server Database Requirements
If you want to install Reporting Services and a SharePoint product instance on the same computer, you can run SQL Server Express and another edition of
SQL Server side-by-side on the same computer or you can use the same instance of the Database Engine for the SharePoint configuration and content databases
if you choose the Advanced installation option when installing a
SharePoint product . If you choose the Basic installation option instead,
the SharePoint Setup program will install SQL Server Embedded Edition
as an internal component and use that instance to host the SharePoint databases.
reporting servides in sharepoint mode
I have to copy a db from a remote server to my local dev machine.
What is the best way to do it.
Last night I made a script for the remote db using xSQL Object and ran it on the local server. the script gave a bunch of errors. Below is the select ##version output for the 2 servers. is there a reason the script is not working
The remote server is using SQL server authentication, the local one is using windows authentication
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64)
Jul 9 2008 14:17:44
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 2)
It would be helpful if your provided some of the errors your script produced.
I notice you're using Enterprise and Express editions - these two editions have differing features, described here: http://www.microsoft.com/sqlserver/2008/en/us/editions.aspx. Perhaps you're using a feature that Express edition doesn't support, or your database is too big.
Not sure if the functionality is exactly the same in 2008, but in 2005, you can open up SQL Management Studio, right-click on the dbase you'd like to copy, and then click on Export Data.
This will guide you through a wizard, allowing you to export the data to another SQL dbase, including one that runs on your local machine. Used it many times - works great.
Why don't you just do a backup and restore?