Group items tagged

"Microsoft SQL Server performs dynamic memory management based on the memory requirements of the current load and activities on the system. On a Windows Server 2003 or a Windows XP or later version system, SQL Server can use the memory notification mechanisms that are provided by the QueryMemoryResourceNotification Windows API. On a Microsoft Windows 2000 Server-based system, SQL Server periodically calculates the free physical memory on the system by using the native Windows API. Based on this information from the QueryMemoryResourceNotification Windows API or from the memory calculation, SQL Server responds to the current memory situation on a specific system. This provides the following benefits:"

Open Source Message Queue system that is entirely built in C# and .NET framework 3.5.

"DBAs and developers alike find it hard to effectively develop, deploy and manage a data-tier application throughout its lifecycle. SQL Server developers today want to create a data-tier application they can test, declaratively deploy across multiple instances while the system deals with version upgrades. SQL Server DBAs on the other hand want to know deployment requirements a priori and they too want the system to perform some of the mechanical upgrade operations instead of managing data-tier applications via a bunch of scripts. In this video we will dive into Microsoft's investments in the SQL Server data-tier application space and demonstrate the concepts and tools that simplify development and deployment of data-tier applications using Visual Studio 2010 and SQL Server Management Studio in SQL Server 2008 R2."

"The Issue, in which Dylan gets bit in the ass by a legacy database I'm building some message-oriented-middleware (MOM?) for a 3rd party vendor product. The database has evolved over many years and has all of the quirks that you might expect of such a system: primary keys that are implied but not made explicit with constraints, relationships that are implied but not explicit, columns that are not nullable in the business logic but are nullable in the tables, etc. I'm not knocking the vendor: I am keenly aware that keeping a multipurpose database absolutely clean of cruft is a tough challenge indeed. But it does make for some really tough integration points. My major challenge over the past week has been auditing. The vendor system makes very heavy use of sprocs and embeds the creation of the audit trail in those sprocs rather than using what, to my mind, is the more obvious approach of triggers."

Hammock is a .NET CouchDB library modeled directly on NHibernate and strives for much of the same functionality while avoiding the vast complexity of mapping object data to a relational system.

"Everyone's up in arms to embrace distributed version control as the new must-have tool for the developer in the know. Though many people have not yet migrated from Subversion, those that have almost invariably extoll the virtues of their particular choice. But though all of the major DVCS's have features that set them above the previous generation of centralized systems, none stands head-and-shoulders above the others as Subversion does among the last generation: each of them was designed for a specific purpose, and each of them will serve those with different habits, workflows and development styles differently. Having used both git and Mercurial for the better part of a year, I've had the opportunity to compare the two. It saddened me to see a Twitter-based debate flamewar erupt over which is better, so I thought I'd do my best to try and ease the tension - with analogies!"

"Quartz.NET is a port of very propular open source Java job scheduling framework, Quartz . This project owes very much to original Java project, it's father James House and the project contributors. Quartz.NET is a pure .NET library written in C# which currently targets Framework version 1.1 and above. Quartz.NET is feature-wise equal to Quartz Java 1.6 excluding Java specifics. Quartz.NET is already running in production systems and has received good feedback. "

"Programmers take certain features for granted - sequential programming for instance, writing down an algorithm that does one thing after the other. RelatedVendorContent State of Agile Development Survey Results & Summary Architecting the Ultimate Service Security Control Point 2010 Open Source Integrity Report: Defect Scan of 291 Key Projects Including Android Kernel DataPower: Messaging, ESB, Cloud, Security as an Appliance The Agile Tester However, if you're writing code in Javascript that uses blocking I/O or other long running operations, sequential coding is out of the question because blocking the only thread in the system is a very bad idea. The solution is to implement algorithms using asynchronous callbacks, ie. spread out sequential code over multiple callbacks."

"Takeaway: SQL Server 2005 has several system tables and views that can provide a ton of insight into blocking problems that you may be facing in your database environment. Through these procedures, you can find blocking chains. Learn more about blocking processes."

"I was astonished to be invited to what became the meeting that originated the Agile Manifesto because my work had always been based around building models. The Structured Development for Real-Time Systems trilogy with Paul Ward and the pair of Object-Oriented Analysis books with Sally Shlaer all focused on analysis and design, placing much less emphasis on the coding and testing favored by agile practitioners."

"Just as it does with file system data, Veracity's decentralized database keeps the full history of the database. Every version of every record is retained in history, with log information about who made the change and when. Veracity also supports push and pull of "database changesets", including the ability to automatically merge (at the level of a record or of a field) and resolve constraint violations."

"There can be a great difference in the performance of a particular routine in a test database, and in a fully loaded production system. When you hit performance problems in a database under load, and there is excessive locking and blocking, how can you determine exactly where the problems lie, in order to fix them? Read on..."