Catch the Latest Shows
[Watch] SQLonCall – all about conferences
[Watch] SelectViews – a new idea, tips, tricks and SQL Server goodies
Featured Article(s)
Tips for Improving ASP.NET Application Performance
The performance of web applications has always been a major concern for application developers. It is one of the most important factors that we need to take care of. When you design your applications, scalability, re-usability and performance are the major factors you need to consider. A lot depends on a good design too! The Design and Architecture of your application should suit your business needs. We will skip any discussion further on issues related to design and architecture here and would rather concentrate on some recommended useful tips and techniques that we can follow in this regard. This article is a quick guide to the best practices, tips and techniques that you can follow.
SQL Server For The Rest of Us
I have a confession. I’ve been doing my best to be a virtual fly on the wall, trying to get a feel for where people are really applying SQL Server, things they’re running into and the like. You find the information in the darnedest of places – from twitter to myspace and facebook to, well, non-tech blogs and other places you wouldn’t really think of SQL Server being talked about.
Some of these are pretty one-way communications where I think people feel a bit like they’re shouting into the bit-bucket, just hoping someone is out there. It’s frank discussion of SQL Server at the most intriguing of levels. Most of these folks are just trying to make it work – just trying to understand how it works and what’s needed to get their database, or their customer’s database working right. The reason I think it’s so fascinating is because it’s a real reality-check on what people are seeing with SQL Server. These are not the people trying to determine the most performant SAN system with the highest degree of scalability and recoverability. They’re not trying to configure the merge replication between windows, RIM and PALM devices.
Most are focused on installation, getting SQL Server running and understanding how to get the application going. They’ve not even considered recovery, not even thought about data protection. The fact is, they really couldn’t care less, they just want the application to come to life.
I think standing back and watching is amazing. The perceptions, assumptions and non-awareness of what we all think about daily is amazing to me. I think we have a lot of "back to the basics" work to do in helping people understand what they should be considering, even at these really basic applications of SQL Server. If the volume of posts and information is any indication, clearly there is real risk of not helping this type of user.
This is one of those odd editorials. You can’t really do much with this information except one thing. Keep your eyes and ears open. Watch out for those that are just getting started and have a legitimate use for SQL Server. Lend ’em a hand – perhaps just scribble down two or three things that will help give them the directions they should be thinking in. Backup your database nightly, use decent passwords, think about the information you’re storing and whether you have information that should be protected.
Just give them a hand – even if it’s just food for thought.
Call for Speakers
If you may be interested in speaking an an upcoming virtual conference, please drop us a note, let us know. It can be a great deal of fun and if selected, we have some great things coming with the next conference. More details very soon – but in the meantime, let us know – email me if you’d like to know more.
Featured White Paper(s)
Deploying Microsoft® SQL Server in an iSCSI SAN
This Technical Report describes how to deploy SQL Server in an iSCSI SAN with PS Series storage arrays. It provides configura… (read more)
Addressing the Persistent Problem of the I/O Bottleneck in SQL Server Applications Through a RamDisk Software Solution
This white paper describes the I/O bottleneck problem that occurs when using SQL and the pain points for which it is responsi… (read more)