﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Editorials / SQLServerCentral.com  / Rethinking Your Design / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 19 Jun 2013 08:39:52 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Rethinking Your Design</title><link>http://www.sqlservercentral.com/Forums/Topic1418042-263-1.aspx</link><description>[quote][b]LoztInSpace (2/10/2013)[/b][hr][quote]Caching is also the type of solution I've found many developers enjoy implementing[/quote]That may be true, but it's also one they also fail to get right 90% of the time.  Done incorrectly, it leaves apps with strange intermittent bugs, consistency errors, confusing "wait - didn't I just change that?" moments for the users (especially on a web farm) and performance bottlenecks when restarting a server.It may be fun, but it's hard to do well.[/quote]Very true, and I'd like to see more reference applications and information on how to do this well.</description><pubDate>Mon, 11 Feb 2013 10:36:31 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item><item><title>RE: Rethinking Your Design</title><link>http://www.sqlservercentral.com/Forums/Topic1418042-263-1.aspx</link><description>[quote][b]GeorgeCopeland (2/11/2013)[/b][hr]It is important to remember that Windows Server and SQL Server provide good caching behavior right out of the box. When designing caching functionality, take care not to interfere with or duplicate what is already occurring.[/quote]Good point George. if one does not know exactly what they are doing in this area they can easily make things worse. :-D</description><pubDate>Mon, 11 Feb 2013 10:28:27 GMT</pubDate><dc:creator>TravisDBA</dc:creator></item><item><title>RE: Rethinking Your Design</title><link>http://www.sqlservercentral.com/Forums/Topic1418042-263-1.aspx</link><description>It is important to remember that Windows Server and SQL Server provide good caching behavior right out of the box. When designing caching functionality, take care not to interfere with or duplicate what is already occurring.</description><pubDate>Mon, 11 Feb 2013 08:17:50 GMT</pubDate><dc:creator>GeorgeCopeland</dc:creator></item><item><title>RE: Rethinking Your Design</title><link>http://www.sqlservercentral.com/Forums/Topic1418042-263-1.aspx</link><description>[quote]Caching is also the type of solution I've found many developers enjoy implementing[/quote]That may be true, but it's also one they also fail to get right 90% of the time.  Done incorrectly, it leaves apps with strange intermittent bugs, consistency errors, confusing "wait - didn't I just change that?" moments for the users (especially on a web farm) and performance bottlenecks when restarting a server.It may be fun, but it's hard to do well.</description><pubDate>Sun, 10 Feb 2013 16:29:36 GMT</pubDate><dc:creator>LoztInSpace</dc:creator></item><item><title>RE: Rethinking Your Design</title><link>http://www.sqlservercentral.com/Forums/Topic1418042-263-1.aspx</link><description>Steve, it sounds like a good time for an in-depth treatment of SQL Server's in-memory capabilities ;^)</description><pubDate>Sat, 09 Feb 2013 16:55:45 GMT</pubDate><dc:creator>phegedusich</dc:creator></item><item><title>Rethinking Your Design</title><link>http://www.sqlservercentral.com/Forums/Topic1418042-263-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/Editorial/96897/"&gt;Rethinking Your Design&lt;/A&gt;[/B]</description><pubDate>Sat, 09 Feb 2013 12:34:18 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item></channel></rss>