General Consultant Discussion

Has anyone purchased the OEM SQL for use for with SAGECRM?

We have not for CRM. But assuming it's the same process as Sage 100, I would avoid it. Getting a download link is impossible

@BasilMalik any info on this? @SageCRM

@MoiraGoggin @JimWoodhead I've actually had zero issues getting links to download the SQL Server files provided by Sage. I'm not sure if it's just easier since the order form for Sage CRM is pared down to three products (CRM licenses, SQL seats, and Sage Alerts & WF), or if there's some other unknown variable... But no issues from what I've experienced.

@BasilMalik We can not get the link from SAGE for our client. (They said they email it to the client) Can you PM me the link you have for the SQL for SAGECRM. I have the SAGE 100 SQL links but no SAGECRM SQL. I think they are different.

@JimWoodhead Ah - my misunderstanding on that... and they're also fibbing a bit. The SalesAdvisorA@sage.com team should give the same link to the partner and the customer (as I've seen them do). The link for Sage CRM's SQL software download is the same as the Sage 100's download link (they only offer the version of SQL Server that's compatible with their most up to date version of SQL for their ERP products).

Very frustrating. Sales advisor told me they cannot send me the link as they don't have it. Always sent to the client only and they have no ability to resend it. Clients are not getting the email that was allegedly sent.

Same problem here

@BasilMalik Are these the links you have? There are multiple links. You need to download all 3 of them. http://cdn.dlm.na.sage.com/sage100/10267/microsoftsqlserver2014oemforsage100.7z.001 http://cdn.dlm.na.sage.com/sage100/10268/microsoftsqlserver2014oemforsage100.7z.002 http://cdn.dlm.na.sage.com/sage100/10266/microsoftsqlserver2014oemforsage100.exe

@RobertWhite @JimWoodhead : I mean worst case scenario, you should be able to ask for the license key associated with their SQL install... they should have that (or should be under the customer's profile in the partner portal) since they're the keepers of the keys. Then download a standard or express version of whatever version of SQL they put on the sales order, use/update the license the key for the installation, and viola. Circumvent the inconsistency with how Sage is delivering the downloads. @JimWoodhead - you actually need all three files. The "".7z.001"" and "".7z.002"" files are data cabinet files housed as .7z archives that contain data necessary to install (because Microsoft's own FAT32 file system doesn't like transferring files > 5GB). So download all three, then run the ""microsoftsqlserver2014oemforsage100.exe"" to extract/compile everything into a true installation directory so SQL Server 2014 can be installed. You'll have what you need to install the product from there.

Be careful with Sage's SQL licenses and hosted servers.

What do you mean from a licensing standpoint or specific issues?

Licensing. ISVR licenses (like Sage sells) do not come with ""Licensing Mobility"".

I'm reaching out to my account manager to get some clarification on the licensing. But from the sounds of his first response, it sounds like Sage and Microsoft have some agreement in place with specific regard to SQL Server. ""**Good news SQL Server is back!** The issues related to our distribution agreement with Microsoft have been resolved, and we are now able to start selling the SQL Server database again."" Will respond back once I get something a bit more definitive.

Basil, The problem is that the SQL run-time licenses sold by Sage have restrictions, which Sage does not communicate with partners or customers... or even with Sage employees.

Damn - that's good to know. I'm assuming you referring to this: ""The SQL Server Runtime license is a license that lets an independent software vendor (ISV) embed the complete SQL Server code into a solution for use only by the ISV application. The customers of the ISV cannot use this SQL Server product to run other applications or to develop new applications, databases, or tables."" https://support.microsoft.com/en-us/help/917400/how-to-obtain-the-sql-server-runtime-license

Not just that. Here's a quote from an email, handed down to our customer from an apparent official MS source: **ISVR licenses/Licensing Mobility Eligibility The ISVR restrictions are outlined in the ISVR Agreement. It is not currently an option with ISV Royalty Licenses because LM (License Mobility) is a benefit of Software Assurance and ISVR does not offer Software Assurance, only Embedded Maintenance. The End Customer can have the Unified Solution running on Outsourced Servers, but not on shared (Cloud hosted) servers.**

Wow... the things that they hide in the fine print. I haven't had any issues with it to date, but still... this is something that should be disclosed or plainly stated somewhere... because expectations.