Archive for July, 2011

Expression Web 4 Service Pack 2 Available

July 13, 2011 Leave a comment
Categories: Uncategorized Tags: ,

Hotmail mail not moved on iOS devices

July 9, 2011 1 comment

Lately, mail that I move into folders on my PC (using Outlook connected to Hotmail) does not get moved on my iOS devices (iPhone / iPad).  This used to work just fine and has broken only recently.  The upshot is that I have to move or delete the mail items again on each iOS device – what a pain.

I’ve tried the suggestion in the following Apple Support article: iOS 4.0: Exchange Mail, Contacts, or Calendars may not sync after update.

There you download and install a profile update that increases the timeout value used when iOS 4 connects to Exchange Active Sync (EAS).

A quick test shows that moving items to folders on the PC does get reflected on the iPad, but of course there could be some peculiar factor that shows the problem up so I’ll keep you posted!

Here’s a screenshot of the profile:

Note that it’s easiest installed by loading the above article on the iOS device in Safari and tapping the download the signed configuration profile link. Remember to reboot your device after the profile is installed.


How do you choose between architectural options?

July 7, 2011 Leave a comment

What process do you use to make architectural decisions? Do you know what goals are traded off against each other when choosing those options?  Is the process repeatable?  Is it well documented?

If you’re not already familiar with LAAAM, I think it’s worth 15 minutes of your time to watch this introductory video.

LAAAM stands for Lightweight Architecture Alternative Assessment Method.  It’s the brainchild of Jeromy Carriere and derived from Carnegie Mellon’s Architecture Tradeoff Analysis Method (ATAM).

Basically a hierarchical tree is constructed with a few major system goals at the top, like Performance, Maintainability, and Flexibility.  These are broken down into one or two levels.  At the leaves are “scenarios” – specific and concrete descriptions of features or function that map up through the tree associated with the goals.  Items at each level are prioritized (you can’t share the same priority), and then some math applied to compute preferential options.

For more in-depth training, watch the Tech Ed 2009 session: ARC314 Using LAAAM to Make Good Architectural Decisions, Fast!


P.S. A whole load of Architecture Presentation’s from the Software Engineering Institute (SEI) can be found here.

P.P.S source


Should you turn off Autogrowth for tempdb data files in a production system?

July 6, 2011 Leave a comment

Yes, if you want consistent and optimal performance.

And, note that we are talking about the production system (and any other test system where you test system performance).

According to Microsoft tempdb optimization recommendations, you should have “one tempdb data file for each CPU on the server” (cores count as CPUs), and you should “make each data file the same size”.  This recommendation is repeated by experts in the field.

So to ensure the multiple tempdb data files are always the same size, you must disable any Autogrowth settings.  Preallocate the files to meet the demands of your largest workload and then monitor usage to make sure you have plenty of reserve space.

The danger of leaving Autogrowth on is you rely on that as a crutch to ensure your files are large enough.  Then when they autogrow you are not alerted and your system performance is compromised.

Granted while the Instant File Initialization feature of Windows Server 2003 and SQL Server 2005 make for much faster file growth, there is still a window where operations pause.

Note this quote from Microsoft in Working with tempdb in SQL Server 2005:

By default, tempdb is set to auto grow; once the space in the file is full,
the file is allowed to grow 10 % of the initial file size. However,
relying on auto grow to manage file growth causes all applications or 
internal operations that use tempdb to pause. Instant data file
initialization (see Improvements in SQL Server 2005) shortens this pause,
improves performance, and allows files to grow much faster as compared to
SQL Server 2000. It is important to note that auto grow can lead to data 
fragmentation and should be used as a last resort.


Top 25 Most Dangerous Software Errors

July 1, 2011 Leave a comment