Version Conflict of .NET Framework in IIS

Another point to share. Of course I delayed the publishing. While I was migrating the YAFNET forum from my machine (WinXP with SQL Server 2005 Express), to a machine with Win2K3 and SQL Server 2000, I faced another issue. The first issue was of migrating SQL Server 2005 Express database to SQL Server 2000 database. The next issue is of conflict of versions of .NET in IIS. The target machine was hosting few web applications developed on .NET 1.1 and was running fine. I created a site for the YAFNET application and in the properties, set the .NET version as

Continue reading

Moving SQL Server 2005 Express databases to SQL Server 2000

Beyond general concept of upgrading, I faced a challenge of downgrade. I needed to migrate a database in SQL Server 2005 Express edition to SQL Server 2000 standard edition. I thought of how to do the same. Time permitted was just few hours.   I scratched on my head and thought of possible ways:  1. Detach from 2005 and attach in SQL 2000: Can not be done. It is not allowed, even if you set the compatibility level of the database to SQL server 2000. This just sets the way how sql queries are parsed and processed.  2. Import from

Continue reading

How choice of Data Structures and Algorithms affect Performance

  The main data structure issues that you need to consider are as under: Table 1 Issues Implications Choosing a collection without evaluating your needs (size, adding, deleting, updating) Reduced efficiency; overly complex code. Using the wrong collection for a given task Reduced efficiency; overly complex code. Excessive type conversion Passing value type to reference type causing boxing and unboxing overhead, causing performance hit. Inefficient lookups Complete scan of all the content in the data structure, resulting in slow performance. Not measuring the cost of your data structures or algorithms in your actual scenarios Undetected bottlenecks due to inefficient code,

Continue reading

State Management Best Practices

  The following table highlights the main state management issues:   State Management Issues Implications Stateful components Holds server resources and can cause server affinity, which reduces scalability options. Use of an in-memory state store Limits scalability due to server affinity. Storing state in the database or server when the client is a better choice Increased server resource utilization; limited server scalability. Storing state on the server when a database is a better choice In-process and local state stored on the Web server limits the ability of the Web application to run in a Web farm. Large amounts of state

Continue reading