Lifecycle Services Subscription Estimator And Prioviding Accurate Transaction amounts

(3) Share

Report

Posted on by Data Chappie

Our implementation partner provided some values for the LCS Subscription estimator namely the Transaction Lines per hour and Transaction volumes prior to go live. I was lead to believe that this is used by Microsoft to size our Production environment. Lots of users complain about performance and so I wanted to submit some accurate revised amounts.

I was wondering how I can get these values out of the system. We have been running production since November last year and so I thought I could use historic data to predict what transaction volumes should be.

Any advice on what reports or SQL queries could be used to derive these values would be greatly appreciated.

Also is our license subscription linked to these transaction values? Seems logical you would need to pay for a larger Azure SQL platform. I am unable to see how it is currently sized but performance would suggest it has one vcpu and very little memory.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

Holly Huffman 6,554 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today!

To address your concerns about the Lifecycle Services (LCS) Subscription Estimator and obtaining accurate transaction data, here's a detailed response:

1. Understanding the LCS Subscription Estimator
The LCS Subscription Estimator is indeed used by Microsoft to size your production environment. It estimates the required resources (e.g., vCPUs, memory, and storage) based on transaction volumes and user activity. If the initial estimates were inaccurate, revising them with actual production data can help improve performance.
2. Gathering Accurate Transaction Data
To derive accurate transaction volumes and lines per hour, you can use the following approaches:
a. Use Built-in Reports

Environment Monitoring in LCS:

Navigate to the Environment Monitoring section in LCS for your production environment.

Review the Activity Monitoring and SQL Insights tabs to analyze transaction volumes, query performance, and resource usage.

System Administration Reports:

Use standard reports like "User Activity" or "Transaction Logs" to gather data on system usage.

b. Query the Database
If you have access to the Azure SQL database, you can run SQL queries to extract transaction data. Here are some examples:

Transaction Lines per Hour:
SELECT COUNT(*) AS TransactionCount,
DATEPART(HOUR, CreatedDateTime) AS HourOfDay
FROM [YourTransactionTable]
WHERE CreatedDateTime >= '2024-11-01' -- Adjust date range
GROUP BY DATEPART(HOUR, CreatedDateTime)
ORDER BY HourOfDay;

Transaction Volumes:
SELECT COUNT(*) AS TotalTransactions,
CAST(CreatedDateTime AS DATE) AS TransactionDate
FROM [YourTransactionTable]
WHERE CreatedDateTime >= '2024-11-01' -- Adjust date range
GROUP BY CAST(CreatedDateTime AS DATE)
ORDER BY TransactionDate;

c. Use Telemetry Data

Enable telemetry in your Dynamics environment to capture detailed logs of user activity and transaction volumes. This data can be exported to Azure Application Insights or Power BI for analysis.

3. Revising the Subscription Estimator
Once you have accurate data:

Open the Subscription Estimator in LCS.

Update the transaction lines per hour and transaction volumes based on your findings.

Submit the revised estimate to Microsoft to request a re-evaluation of your production environment sizing.

4. Licensing and Azure SQL Platform

License Subscription:

Your Dynamics 365 license is not directly linked to transaction volumes. However, the size of your Azure SQL database (e.g., vCPUs, memory) is determined by the Subscription Estimator and may incur additional costs if upgraded.

Azure SQL Sizing:

To check your current Azure SQL configuration, access the Environment Details in LCS. Look for the database tier (e.g., DTU or vCore-based) and resource allocation.

If performance issues persist, consider upgrading to a higher tier or adding more resources.

5. Recommendations

Monitor Performance:

Use LCS Environment Monitoring and SQL Insights to identify bottlenecks.

Optimize Queries:

Work with your implementation partner to optimize poorly performing queries.

Request Support:

If issues persist, contact youor partner and/or Microsoft Support to review your environment sizing and performance.

Hope this helps!

Was this reply helpful? Yes No
MYGz 2,334 on at

Like (3)

Report
Copy link

Link copied!

Restore Production DB on UAT and then you can query the AxDB via SSMS.

Check VendTable, CustTable, AssetTable, EcoResProduct, InventTable etc for master data and VendTrans, CustTrans, AssetTans, InventTrans, GeneralJournalEntry, etc. for transaction data.

You can get the UAT SQL Access like so:

https://dynamics365musings.com/how-to-connect-to-a-test-d365-database/

Was this reply helpful? Yes No
André Arnaud de Cal... 303,667 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi Data Chappie,

Apart from checking if you need more resources based on the transactions, you can use a Trace parser to analyse a recorded scenario from the application. This can give clarity on what takes time. Performance issues can be caused by a lot of things, like settings, usage of particular scenarios, customizations, missing indexes. Also Dual-Write can add a performance penalty when saving changes. In most cases when I looked at performance issues, it was not caused by a wrong estimation and allocated resources for your environment.

Was this reply helpful? Yes No