Unanswered Visual Studio 2010 SQL Server Data Tools extension poor peformance

  • Monday, August 13, 2012 8:04 AM
     
     

    hi all.

    i'm a software develoepr and .Net programmer.

    in VS2010 i have installed SQL Server Data Tools 2012. i have a solution that contains 5 SQL Server Projects, along with 25 class library projects.

    sometimes VS gets hang and have a poor performance. when i open Windows Task Manager, i see that it got the CPU and high memory usage, an a commit working set of more than 1.2 GB ! when made more investigation, i knew that it gets hang and high memory and CPU usage when it refreshes its LocalDB auto generated Databases for SQl Server Database Projects within the solution.

    the sql server projects have nothing, but a couple of scripts that incluse a maximum of 1500 database objects, including stored procedures, views, and a few triggers.

    no objects are created within LocalDB Databases and they don't include any data in those tables.

    is there any way to increase vs performance in this stage ? or any suggetions to get rid of this problem ?

    thanks in advance.

    Massoud Safari Foroushani

    Senior Software Developer

    EIT Technologies.


    • Changed Type massoudmario Tuesday, August 14, 2012 5:01 PM
    • Edited by massoudmario Thursday, August 16, 2012 3:03 PM
    •  

All Replies

  • Tuesday, August 14, 2012 5:08 AM
    Moderator
     
     

    Hi massoudmario,

    I am trying to involve someone familiar with this topic to further look at this issue.

    Thanks.


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us

  • Tuesday, August 14, 2012 5:06 PM
     
     

    Thank you very much for your support Vicky Song.

    i've installed MSDN Forum Assistant gadget on my desktop to be sure i won't miss your support.

    Thanks

  • Tuesday, August 21, 2012 1:46 PM
     
     

    Hi,

    When a database is refreshing, all the local files are uploading to memory.  If possible, try to modify one database at a time, so not all 5 SQL project databases are loading at the same time.

    Thanks,

    Cathy Miller

  • Wednesday, August 22, 2012 2:54 PM
     
     

    Hi Cathy.

    before go furher, i thank you very much for your reply.

    I did guess that what you told is the reason of the case.

    But, i did tell there's not any data, even one record, in the LocalDB auto-generated databases.

    I believe that you're right. but, i'm wondering why refreshing the LocalDB takes such amount of memory, both in RAM and the Windows Virtual memory?

    I think this is not a nice-balanced tool (SSDT) for VS. Perhaps you know that any application that takes a huge amount of memory in such operations, is not nicely load tested, at least i think this is.

    In the case you mentioned that i could work with a database at a time, actually i can't do so.

    because i handle 5 subsystems of the corporate software, and all of them have the limited number of database objects.

    I'll more investigate the issue and collect some useful info about details of that.

    nevertheless, Thank you again for the reply.

    Massoud Safari



    • Edited by massoudmario Wednesday, August 22, 2012 2:57 PM
    •  
  • Wednesday, August 29, 2012 8:28 PM
     
     

    Hi,

    If you need further assistance, you may want to consider opening a support case for investigation.

    Please visit the below link to see the various paid support options that are available to better meet your needs.

    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone

    If Microsoft determines that a problem is the result of a defect in a Microsoft product, you will not be charged for that incident.

    Thanks,

    Cathy

  • Tuesday, September 04, 2012 6:25 PM
     
     
    Hi,   Not sure this will help but I'll mention it.  In our environment I was doing Builds quickly and one of my associates was having them take a long time.  It may not have even been build's but even just opening the solution file.   I stored my local/edit copy on the c: attached to the laptop where VS was doing the build.  My associate put the VS "local" files (his local/edit copy, not the source control files) on a mounted machine in our large corporate environment.  Don't know what it was but there must be large compares between Source control and the local copies and between mounted drives and it was taking a long time (hours and not finishing).   When my associate switched his local copy to his c: drive he was Build'ing in minutes like I was.
    • Edited by flash7gordon Tuesday, September 04, 2012 6:27 PM
    •