none
IPAM Database requirements RRS feed

  • General discussion

  • Why is SQL Server Enterprise edition required and WHY is it so poorly documented? Is there any way around this limitation. It is not mentioned here:

    https://technet.microsoft.com/en-us/library/dn758112.aspx here 

    https://technet.microsoft.com/en-us/library/jj878312.aspx or here

    https://technet.microsoft.com/en-us/library/dn758115.aspx

    However it does state: 

    "Use one of the following procedures on a computer running Microsoft SQL Server 2008 or later to configure the SQL database for a connection to IPAM on a separate computer." and "Microsoft SQL Server 2008 R2 and later is supported."

    This just cost us a lot of time and money, please advise.

    Monday, April 25, 2016 8:46 PM

All replies

  • Any thoughts?
    Tuesday, May 3, 2016 8:16 AM
  • We just ran into this same problem in our environment -- this is totally ridiculous and arbitrary.

    We were unable to install IPAM onto our SQL Server Standard cluster, using a Windows Server 2016 IPAM deployment. I know for a fact that this is an arbitrary restriction in the IPAM source code, because WID does not support ANY features that SQL Server Standard does not support.

    Joe

    Monday, June 4, 2018 7:10 PM