I'm assuming we are fine with the SQL Server Standard + 1 CAL for the service account (or do we need 3 CALs for the service account, target db and source db)? This would be cheaper than a per proc license. If you still cant access Microsoft Eopen Login Site then see Troublshooting options here. Login screen appears upon successful login. VLSC Help is also available if you're not signed in. Go to Microsoft Eopen Login Site page via official link below. You can find instructions for using the VLSC by clicking Help in the VLSC menu bar and then clicking the name of the FAQ that relates to your question. What I'm trying to decide is if we need a per proc license or a standard + CAL license (and if CAL how many CALs).ġ) The packages all run as Scheduled Tasks periodically to update data from one database to another.Ģ) No users access these packages (only the service account) except when a new version of the package is deployed to the server.ģ) The packages are all developed by developers who have the approprate MSDN license for the dev environment. If you need help using Microsoft's Volume Licensing Service Center, here's where to go. However, my question deals specifically with what kind of license I need.īased upon what features we are using, I need a SQL Server Standard license. Q: Are up-to-date points accumulated by a lead affiliate published in the Volume Licensing Service Center (VLSC). I'm aware that I need to have a SQL Server license for the application. Up front is the only option for License only. We are deploying SSIS packages to an application server (not a SQL server).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |