A quick little tip on how to manage connection strings in your applications with a SQL Alias that you can create with “SQL Server Configuration Manager”
Ease your Visual Studio development with a SQL Server alias
Labels: .NET, database, deployment, vs2010
Fast = $$$ How do you make sure to have a fast application?
Many articles on the web, books and statistics tell us that “faster = better” and even more important: faster = more revenue.
For Google an increase in page load time from 0.4 second to 0.9 seconds decreased traffic and ad revenues by 20%.
For Amazon every 100 ms increase in load times decreased sales with 1%.
Also Google uses site speed in their web search ranking. So make sure to optimize your website for speed as per my other blog post.
Is Web Performance Optimization (WPO) something for you?
Labels: database, deployment, performance, silverlight, SSRS, testing, TFS
SQL can stink too - Code smell in stored procedures
Figure: You don't need to dig deep to find smelly code
I just found this nice piece of TSQL that I came across in a 500 line stored procedure on my current project.
Labels: coding, database, readibility, sql server
ORM: Should I go Micro?
We had an interesting internal discussion about ORMs (Linq to SQL, Entity Framework, …) and MicroORMs (Dapper, Massive, PetaPoco, …). This discussion led me to think about: When should I use a MicroORM?
I would go for the approach: Use both (MicroORM and BigORM) and use them where they make sense.
Labels: database, databinding, sql server
log4net – How to change settings of an appender at runtime
I found this awesome blog post about 4 tips on log4net from the year 2005.
Since the code is out to date I post here my update.
2 nice things:
- I use EntityConnectionStringBuilder to extract the database connection string from an entity framework connection string
- If my log4net connectionstring, holds {auto} , we replace it, otherwise we wont
(so that we can change the logging database, if we want to)
Labels: database, deployment, entity framework, how to, sql server
Solution to: System.InvalidOperationException: There is already an open DataReader associated with this Command which must be closed first.
from an internet website: a datareader represents an open connection to the database. to run 2 readers simultaneously, you need to use two seperate connections. #1 just change your connection string to add it back (add MultipleActiveResultSets=True to connection string).http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=123691&SiteID=1 NO SOLUTION #2 new Connection on every GetConnection() --> no singleton NO SOLUTION ERROR: Invalid attempt to MetaData when reader is closed. #3 connectionstring always another! NO SOLUTION ERROR: Invalid attempt to MetaData when reader is closed. #4 BackgroundWorker solves the problem!
Labels: database
Access 2007 - Whats good and bad
very interesting info.... sorry forgot the link.... http://allenbrowne.com/access2007.html
Latest Posts
Popular Posts
-
*Updated* 26. September 2010: Updated with comments from Adam Cogan *Updated* 27. September 2010: Updated the comparison between anonymo...
-
It's easy I thought, just select the Property of the EntityType and set the Default Value in the Properties window to: DateTime.Now ...
-
Had some discussions about Lists and controls, like Listbox and Listview, and sometimes its difficult to distinguish those. System.Win...

