web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / 2015 CU1 Hotfix and Kn...
Microsoft Dynamics SL (Archived)

2015 CU1 Hotfix and Known Issues

(0) ShareShare
ReportReport
Posted on by Community Member

Can anyone tell me where to find DSL 2015 hotfix and known issues list on customersource? I have asked my BP without response and only have software maintenance on SL so I cannot open a ticket. Thanks in advance.

*This post is locked for comments

I have the same question (0)
  • Cherie Kane Profile Picture
    Cherie Kane 639 on at

    Rob:

    They should be under the Support heading in customersource for HotFix.

    Which one are you looking for specifically?

    Cherie

  • Community Member Profile Picture
    Community Member on at

    Ok, the hotfix list is there. I was faked out by the SL2011 title.

  • Community Member Profile Picture
    Community Member on at

    Of course the link to Bug 36193 and KB3083965 is bad.

  • Community Member Profile Picture
    Community Member on at

    IMHO they really should add the SL 2015 to the metadata. This document is listed as applying to SL 7 and SL 2011 on the left side of the page.

    SITE: CustomerSource (1)  

    Customer Document Type: Downloads (1)  

    Product:

    Microsoft Dynamics SL (1)  

    SL 2011 (1)  

    SL 7.0 (1)

    Hotfixes Available for Microsoft Dynamics SL 2011 and Later ...

    mbs.microsoft.com/.../SLHotFixList

    This list includes all hotfixes available for Microsoft Dynamics SL 2011 and later versions. Last updated 11/03​/2015

  • Community Member Profile Picture
    Community Member on at

    mbs.microsoft.com/.../SLHotFixList

  • Community Member Profile Picture
    Community Member on at

    Hi there,

      Got a message from support that the link has been repaired.  I was able to download the hotfix this morning, applied it and... unfortunately, it didn't fix the issue we are experiencing.  Still takes 9 or 10 seconds after pressing F3 before anything happens in the project maintenance screen, which is not acceptable.

  • Community Member Profile Picture
    Community Member on at

    I'm curious as to how many projects you have in your projects table. This takes 2-3 seconds for me with 15 thousand projects. This is better than the 30 seconds delays we have been experiencing with shippers. It is my humble opinion they tested the this code for the lookup with less than 100 records in the system and it is also my humble opinion keepers of the code need to load up their test db so they can see our pain and these issues come out in QC.

    I did run an SQL trace on project maint and when you press F3 and there is a lot of what I would consider extra over head in the setup and the paging method used when you press F3. . I assume this code is core in the SL controls so this problem will exist with any table with a large number of records.

    Warning, starts to get technical from here.

    I took the SQL from the trace and ran an execution plan and client stats. I noticed inefficient SQL queries and mis-use of sp_execute so it really is no surprise how long it takes for a screen to pop up after pressing F3

    sp_executesql can be used instead of stored procedures to execute a Transact-SQL statement many times when the change in parameter values to the statement is the only variation. Because the Transact-SQL statement itself remains constant and only the parameter values change, the SQL Server query optimizer is likely to reuse the execution plan it generates for the first execution. What I call mis-use is that they don't use parameters so the execution plan is regenerated over and over for each page of data.

    On my system with 15K records, even just getting a count of the records and a list of fields to display (just the fields not the data), generates a hash recursion. Hash recursion occurs when the query data does not fit into available memory, resulting in the split of input into multiple partitions that are processed separately. This is what I called inefficient SQL. Counting the number of records or getting a list of fields should not be generating hash recursion.

    Another poor decision was including support for SQL 2008 R2. In the SQL Server 2012 a new feature was added in the ORDER BY clause, to query optimization of a set data, making work easier with data paging for anyone who writes in T-SQL as well for the entire Execution Plan in SQL Server. A great article for coders which shows how this can be done at least 10x faster is here just in case anyone is interested.

    social.technet.microsoft.com/.../23811.paging-a-query-with-sql-server.aspx

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans