Plenty of other software works like this. Windows Update provides fixed to various software on my desktop, I get a list of patches I can download when VideoStudio starts, and SQL Prompt lets me know about updates when I start SSMS. Those are all channels that allow a company to easily deliver patches to customers that improve the software. Usually these are patches, but sometimes there are improvements, like Experimental Features. In SQL Server, we have usually frowned on feature enhancements in patches, but is that what we really want?

Read the rest of "Continuous Releases" at SQLServerCentral.

Consumers probably think this is a good idea. Computer gets set up for them, and they pick a password. Technical people cringe. Password written down, given to stranger, stored by large company. What could go wrong? You can guess, or read the comments in the article.

Read the rest of "Password Handling" at SQLServerCentral.

"Choose the best person for the job" is a mantra that so many people espouse, but we never have a repeatable, logical method for determining who the best person is, in any industry. Most of us use some type of interview to choose a new employee, with mixed results.

Read the rest of "Do Interviews Work?" at SQLServerCentral.

While I'm not sure big data is well defined, I do know that there are large data sets which can overwhelm relational databases, both in scale and the speed at which the data is collected. Microsoft added StreamInsight to SQL Server to help deal with the speed problem, but I'm not sure that relational databases can handle the size issues at the same time. Some large computing and analysis problems don't lend themselves well to non-relational soluttions, and other technologies are needed.

Read the rest of "What is Big Data?" at SQLServerCentral.

There are a few problems here, and they are similar problems that we've seen in the past as we pushed out more capabilities to individual users. The first one is that allowing people to create their own SQL Server instances can be problematic as they don't do a good job of setting up maintenance. SQL Server is easy to set up, but a little more complicated to manage over time. I suppose templates could potentially have backups and maintenance built in, but if you do this with any scale, you might end up with storage and space issues as well. There's only so much automation can do with limited resources, and I could see this ending up causing more infrastructure problems over time for IT staffs.

Read the rest of "Self Service SQL" at SQLServerCentral.

There's a discussion on Slashdot as well, and I was struck by a few of the comments, which seem to suggest that if you are still just a "software engineer" at age 40, you aren't very good at your job. It seems that some people seem to think that everyone in this business is constantly looking to move to a new job and advance into management or they aren't successful . I saw analogies with other industries thinking that same thing, that experienced people would not still be doing the same job after 20 years.

Read the rest of "Is Software Engineering Dead?" at SQLServerCentral.

However there was one thing in the session that struck me. One of the steps is for you to take control of your own training and make an active effort to learn more about your craft, tracking your time and efforts to present to your boss. Will says that he spends an hour a day on professional development, which sounds like a lot at first glance, but it's only 12.5% more than a 40 hour work week.

Read the rest of "Time for Your Career" at SQLServerCentral.

Recently I was in Cambridge, UK for a meeting with my group at Red Gate Software. I go over once or twice a year and spend a few days with my department and a few days in the office. This time one of the days I was planning on being in the office was a "day out" for our part of the company. Twenty-some people took a bus to another town where we etched a picture and printed it during the first half of the day, and then toured the GainsBorough house and museum in the afternoon.

Read the rest of "Teambuilding and Bonding" at SQLServerCentral.

Read the rest of "SQL Server on RDS" at SQLServerCentral.

It was quite a surprise for me, and something that hasn't happened in a long time. It wasn't for long, but a month ago, there was a period of time when SQLServerCentral was down. It's also one of the very few times it's happened since I was in charge of the servers. The exact reason was something to do with out hardware, and it was fixed relatively quickly by our hosting provider.

Read the rest of "The Colocated Dangers" at SQLServerCentral.

However thieves that target your phone as a different story, and for them, getting past a four digit lock on your phone might be trivial. There are firms that help police get past codes, and I'm sure there are plenty of instructions and utilities around that a thief with decent computer skills could use. It's also likely that there are more than a few utilities available to duplicate this functionality.

Read the rest of "Mobile Password Protection" at SQLServerCentral.

When you try to learn some new topic, say Reporting Services, there is so much information you can find on Google, but it's all unorganized. It can be hard to learn without a plan, and books are usually organized in a way to walk you through a technology. That along can be valuable, and you can supplement chapters with articles you find around the web. This was the inspiration for our Stairway Series of topics, which we'll eventually compile into books at some point. The Stairway on Reporting Services, by Jessica Moss, is excellent, and if you read through it, you'll see what I mean.

Read the rest of "The Best Way to Learn" at SQLServerCentral.

It's all too common for people in this business to overwork themselves, work very long hours, and neglect the rest of their life. I have rarely seen someone that is retired or late in life complain that they didn't work enough over their lifetime, and I'd caution you to keep that in mind as you go through life. There will always be more work, more things to do, and more requests from clients and customers. Keep a balance in your life, and remember to enjoy it along the way.

Read the rest of "Work to Live" at SQLServerCentral.

That's the advice that Scott Horowitz got from his father. He talks a little about how this relates to technical people who find themselves looking at management to further their careers, or are sometimes even get promoted just because they're the strongest technical employee in a group. Mr. Horowitz sees the transition as one that rarely works well, though he has some good advice on how you can increase the likelihood of success.

In my career I've moved to management a few times and back again to a technical role, though never at the same company. I am sure it would be a strange move to be in charge and then move back to a contributing employee, but I do know some other people that have done it successfully in their careers. I have enjoyed both roles, and at different times in my career, the different role has fit me better.

Read the rest of "Promoting Engineers" at SQLServerCentral.

The process is interesting, but one of the comments caught my eye. It includes a quote from the article:

Read the rest of "Being Responsible for Code" at SQLServerCentral.

However that's not necessarily the plan for everyone that works in the technology business. I know plenty of people that would like to move into management, or even move into some other career field if they can afford to do so. In the responses to many editorials in the past, I read that quite a few people think the technology business isn't a great choice and wouldn't encourage their children to enter this field.

Read the rest of "A LIfetime of Software" at SQLServerCentral.

We have a lot of work to do in the database with regards to security. Auditing, tracking, configuring security, these are all challenges, and while SQL Server is getting better with the enhancements they have in SQL Server 2012, there is still work to do on the platform. I do think that Microsoft needs some help and guidance from us here as well, as we implement new features, find problems with using, scaling, or just understanding them, and I hope you will try out the new features and then submit feedback on Connect and write about your experiences.

Read the rest of "Security Outside the Database" at SQLServerCentral.

We have also seen investments in computer technology result in much more efficient operations in many industries. One example is our delivery companies plot our optimum routes for package delivery, saving time and fuel. Another example caught my eye the other day: car sharing for government fleets of vehicles. It's a concept, using technology from ZipCar, that could potentially save tens of millions of dollars.

Read the rest of "Technology for Sharing" at SQLServerCentral.

Almost as soon as we got the system deployed, we had to modify it to add additional pieces of data related to power and heat. We were approaching the limits of both, and knowing where we had spare power, the consumption of power on each circuit as well as the heat load in different parts of the room allowed our hardware people to better plan for future requirements.

Read the rest of "Smelly Power" at SQLServerCentral.

If I were asked in an interview, I would politely decline and state that I have set up privacy for a reason. There are things I post to share with friends and family that are not meant to be available for the general public. In my mind, these are akin to photo albums or letters I've written that I store in my house. Anything that I post publicly I take responsibility for, but private posts are private. I would suggest you do the same.

Read the rest of "Social Media and Interviews" at SQLServerCentral.

However this presents a problem in a DR situation, especially over time. If I make a backup, and lose my server in a year, can I easily find the copies of the asymmetric keys or certificates? Can I easily match up the proper key with the encryption if I rotate keys periodically? There hasn't been a great solution I've seen to solving this issue.

Read the rest of "Key Storage" at SQLServerCentral.

I'm not alone, and most of my co-workers engaged in other sorts of distractions as well. We weren't alone either, and this survey from Salary.com shows some interesting results. Many people spend time on the Internet on non-work tasks, and I think that's OK. I also think it's not much different from the pre-Internet days of work. Smoke breaks, random walks around the building, water cooler time, I think some people would be surprised how much time they spend away from "work" if their movements and efforts were tracked by the minute.

Read the rest of "Wasting Time" at SQLServerCentral.

Recently at the DevConnections conference, I saw a talk where Mark Minasi talked about the future of tablets and smartphones, where he mentioned the idea that we will use many devices in the future that don't necessarily need to connect to the domain inside a company. They'll still authenticate, but with certificates.

Read the rest of "Certificates Everywhere" at SQLServerCentral.

However the amount of after hours calls varied widely, often related to the size of the company. In larger companies, it seemed as though there were more calls per week, but more people to handle them. Smaller companies often had me responding to anything, but there were few calls. This Friday I'm wondering what it's like for you.

Read the rest of "The On-call Demands" at SQLServerCentral.

It was a great presentation and it made perfect sense to me. I've always tried to store my DDL code in some sort of VCS, checking it and out as needed. I found it helpful for keeping track of which version of an object was released with which deployment. This also helped me to organize the changes which I was going to release, branching them away from the full list of changes stored in source control.

Read the rest of "Treat the Database Like Code" at SQLServerCentral.

Someone asked me why, and I had a few reasons, all of which seem to me good reasons to make use of my little friend. First it's easy, Apple/iOS easy. When things aren't easy, we tend not to do them, but clicking "script" is painless, it doesn't interrupt you, and it produces the script you need in a new query window. That alone ought to be a good reason to use it.

Read the rest of "My LIttle Friend" at SQLServerCentral.

At one point in my career I was working on a new application and we were debating about storing certain metrics related to the application usage and customer's behavior. My boss asked for my opinion and I said that more data was better than less and we could always delete the data if we found it was not being used.

However we rarely delete data. We seem loathe to remove old data, even when we find it's slowing down our systems. Worse still, there aren't great methods for even stripping out, and preserving older data other than custom work in each system. I ran across a piece that talks about the tremendous amount of data that we are constantly acquiring, a deluge that overwhelms us in so many scientific areas. There are some endeavors collecting so much data that they must restore to storing data in networked systems, making the data sets available only through software that can combine the information from various databases.

Read the rest of "Too Many Bricks, Too Much Data" at SQLServerCentral.

Coming up with something plausible, exciting, but unrealistic is a good challenge for me every year. The people on the team will exchange some ideas throughout the year, and I'll usually put together in February or early March, trying to contain my worry that the joke will not go over well. I think I've done a good job over the years, and I have a few good ideas for next year.

Read the rest of "Skipping April Fools" at SQLServerCentral.

The systems we build and support are often in use during the business day by our companies and clients. That usually means that patches or changes to the applications take place in off hours, and that means the IT staff is used to working at night and on weekends to make changes. This Friday I'm wondering what that means for the SQL Server community.

Read the rest of "The Maintenance Poll" at SQLServerCentral.

During the opening talk, there was a slide with a very interesting statistic. It talks about the last few years had seen 40% data growth for many organizations, but IT budgets had only grown by about 5%. Those two numbers don't really relate well to each other since the cost of IT operations can dwarf the cost of storage, but for how long? At some point 40% growth will catch up and become a significant cost in your organization.

Read the rest of "Data Growth" at SQLServerCentral.

When a company needs help, what can they do? Hopefully they're a good company, one where people want to work. If that's the case, then be real, be honest, and show employees that you are a place people want to work. My own employer, Red Gate Software, made a great video for a UX specialist. It almost makes me want to apply for that job. Unfortunately I'm much better at breaking visually appealing things than designing them.

Read the rest of "Attracting Talent" at SQLServerCentral.

Actually, I should clarify, I think that tabs should be inserted into code as spaces, so that a consistent layout can be maintained. Most tools allow for this, and while I have never worked in a place where the tab/space ratio was entirely consistent among all those writing code, I have found that using ASCII 32 is preferable to ASCII 9 when files are shared among different people.

Read the rest of "Tabs or Spaces" at SQLServerCentral.

I've had times when Service Packs that installed smoothly and essentially had no impact on production systems, and I've had times when the installation blue screened my test systems. During the latter times I was extremely glad I'd decided to test the SP and not blindly install it on a production system. That is one of the things that worries me about cloud computing. I need to be sure that patches work on my systems.

Read the rest of "Waiting for SP1" at SQLServerCentral.

That's distressing for customers, and embarrassing for Microsoft, who is spending a lot of resources to promote cloud computing and their Azure services. It lends credence to the fears and concerns of many technology professionals that outsourcing parts of their infrastructure to a cloud provider is a problem.

Read the rest of "An Azure Outage" at SQLServerCentral.

However is that really necessary for many applications? The largest applications in the world, Google's search engine, Facebook, and more, are turning to NoSQL databases and storage to handle their loads. I ran across a nice piece on Ars Technica that talks about how these companies handle the large data storage challenges they have. The one very interesting thing in the piece is the way the consistency challenges are talked about. These phrases, "designed with less concern for consistency of data across the system", "jobs in progress will still hit stale data", and "is entirely okay with serving up stale data", would scare most DBAs I know.

Read the rest of "The Consistency Debate" at SQLServerCentral.

That's why you always have an open position available for a great developer. If one is available, and they rarely are, you hire them if they want to work for you. You can always find things for them to do, and they can make improvements in code that your other 5, 10, or 20 developers will never come up with. I'd make sure they fit in your team and get along with others. You can get less work done if you have someone that is too difficult to deal with or too critical of others. While a great developer can accomplish things that others can't, or won't, they can't do all the work.

Read the rest of "Great Developers" at SQLServerCentral.

Today we have an easy poll, and I'd love to get your answer, as I'm sure Paul would as well:

Read the rest of "Old, but stable" at SQLServerCentral.

That hasn't really happened, and it seems Service Broker has not been widely adopted by many database developers. It surprises me since it seems like a fantastic way to move data between servers. I'm not sure if too many data professionals think a message means a substantial delay in the movement of data, or if they don't trust the architecture, but there don't seem to be many people using this feature in SQL Server.

Read the rest of "Scaling Out" at SQLServerCentral.

While many of us are not looking to implement cloud computing now, we may do so in the future, but not for simple cost reasons. There's a piece about data gravity in the cloud, and how the law can drive the location of data in some cases. Just as many companies that wanted to offer gambling services moved to countries with fewer laws about that business, I would expect that we see some companies moving pieces and parts of their data to other countries to take advantage of more lax or lenient privacy or other laws in the future.

Read the rest of "Data Gravity" at SQLServerCentral.

These days I know there are much better tools for testing applications, and I have heard of black box scanning of static source code. I haven't heard of too much real time scanning of the executable code by the authors of code, but I'm sure there are tools out there to help you find vulnerabilities. I saw recently there are even better tools for scanning code that combine both techniques into something being called glass-box scanning.

Read the rest of "Code Scanning" at SQLServerCentral.

One of the highly anticipated features in SQL Server 2012 is the Always On feature, which will dramatically increase the ease with which we can build databases that can not only tolerate hardware failures, but be deployed (physically) further apart, and with more flexibility in how backups can be taken. If you haven't read about Always On, I'd urge you to start looking at this feature and see if it's something that can help your company.

Read the rest of "High Availability Upgrades" at SQLServerCentral.

The simple answer is use the 4th dimension: time.

Read the rest of "Use the 4th Dimension" at SQLServerCentral.

I ran across a piece that surveyed some salaries and it shows that people working with cloud platforms are commanding higher salaries, even when the underlying technologies are the same. It seems crazy, but that's the world we live in. Perceptions drive a lot of things in the world, especially the ones that don't seem to make sense.

Read the rest of "The Cloud is good for your career" at SQLServerCentral.

Why use Hadoop? What's the power of this framework? It's designed to work with disparate data sets, with structured and unstructured data, from a variety of sources, and perform complex analysis of this data using clusters of inexpensive hardware. In other words, it scales out very nicely.

Read the rest of "The Power of Hadoop" at SQLServerCentral.

This Sunday the 84th Annual Academy Awards take place, and while I won't be watching them, it's always interesting to me to see which movies and people win awards. A winning actor or actress might entice me to go see a future movie that ordinarily wouldn't capture my interest. It's always nice to see talented people working their craft, at least to me.

Read the rest of "A Break from Databases" at SQLServerCentral.

Most things that I've built in technology don't work the first time, and in fact, I expect that. I have learned from mistakes, corrected the problems, and usually finished them with some level of success. That's the way that so many of us in technology approach our jobs. We start building, find issues, and then fix them.

Read the rest of "Accept Failure" at SQLServerCentral.

Recently I sent her this link about salespeople and commissions. It talks about the problems with commissions and the potential misunderstandings of what commissions actually do for our company. I know that some companies think paying salespeople flat rates and no commission is heresy. I know others that have transitioned to flat rates, including many retail companies, and they have continued to achieve high sales.

Read the rest of "Programmers v Salespeople" at SQLServerCentral.

That reminded me of a common issue that many of us have: we get into a rut. It's easy to stick to doing things the "old way" we've learned, and not updating our skills to take advantage of newer features. It's also easy to get used to going through a process one way and never trying, or experimenting with different techniques or applications of the tools.

Read the rest of "Use Your Tools" at SQLServerCentral.

I ran across a post recently from Microsoft researchers that showed similar issues with other anonymous data sets that contain IP information. A number of logs containing traffic from Bing and Hotmail were analyzed with the intention of identifying particular hosts. Even when the data was anonymized, it was possible to identify hosts with a high degree of accuracy.

Read the rest of "Anonymous Research" at SQLServerCentral.

It might be the nature of sensitive data means keeping the use of encryption quiet, but that shouldn't matter. If you are keeping your keys safe, the algorithms and deployments you use should not matter. This Friday I wanted to ask a question about your use of encryption in real world systems.

Read the rest of "Encryption in Production" at SQLServerCentral.

The first was the idea that we might have more data APIs in the future, designed to make the exchange of data easier. The people that work with data imports and exports have probably been hoping for his to become more prevalent, and it has gotten better. However I do think that data is becoming the most important part of the technology world. It isn't the software, or the platform, or the device, but the data that's available that is the most valuable part of a technology system.

Read the rest of "API Changes" at SQLServerCentral.

As much as I'd like to say this is a good idea, I can see this being more of a tool for abuse than a tool for making changes. I suspect most managers would take negative feedback personally and investigate more, perhaps even asking network people to comb through logs to find out who posted comments, or perhaps even assume that a particular employee had written the commend without any evidence. We are often entirely petty in our reactions to criticisms, and I'm not sure most of the managers I have worked with would actually use this data to improve the way they perform their job.

Read the rest of "Morale Data" at SQLServerCentral.

However it's not just the desk you work at that might be a problem. There's an article that talks about the dangers of mobile devices, and the potential problems of working while on the go, in bed, etc. As we use these devices more and more, it's possible that we are inducing other repetitive motion injuries, similar to carpal tunnel syndrome. If you are a heavy user or a tablet, smartphone, or other device away from your desk, I would recommend you read the article and think about how you use your device.

Read the rest of "Healthy Work Habits" at SQLServerCentral.

That's pretty cool from my perspective. They have a passion for their jobs, they like the different aspects of it, and they aren't going to change that to save a few dollars or make their jobs easier. They don't want to avoid responsibility for parts of their jobs, they want to embrace all of their jobs, as something they enjoy doing.

Read the rest of "No Cloud for Stack Exchange" at SQLServerCentral.

I know you can't attend every session, and you can't see all the content that week, but the sessions are recorded and attendees can get DVDs of the content. I love that, and it means I can pop in and out of sessions, checking out the content and topics, and mark those in a program that I want to watch later. It also means that I can focus on the important parts of the conference: meeting people.

Read the rest of "Back to Vegas" at SQLServerCentral.

I'd hope that most people would not attempt to write code in this method, but I've seen many developers do just that. They start trying other solutions until one works, often implementing the solution without understanding how it works. The fact that it works, even in a limited way, is often good enough for most people.

Read the rest of "Jiggly Code" at SQLServerCentral.

He left Microsoft as a full time employee in 2008, and has moved on to working with the Gates Foundation. His missions there, along with his wife, Melinda, is to improve people's lives. The foundation has primarily focused on ending disease and hunger in developing countries, and to date has done some very good work for millions around the globe. I ran across an infographic recently that talks about philanthropy and have reprinted a portion here:

Read the rest of "Better Than Batman" at SQLServerCentral.

As computers become a commodity, and we use them more and more to live our lives as well as work, does it make sense for workers to purchase their own machines and use them in a corporate setting? I know some companies give workers a computer allowance and the workers can take the machine with them if they quit, presumably if they work at the company for longer than a few months. Other companies give their employees money for technology, which can be exciting for technical people that might want to upgrade their monitors or other accessories regularly.

Read the rest of "BYOD" at SQLServerCentral.

These days the pace of technology change is high. SQL Server is a stable platform that many companies might install and use for a decade, but it seems we have new features to learn every 18-24 months as new versions are released. I think more and more of us have to understand a wider variety of features and platform all the time...

Read the rest of "The Virtual Lab" at SQLServerCentral.

When I was younger, I was very money driven, looking for new jobs or ways that would allow me to earn more money. I have been in and out of consulting, always looking to move up in the world. As I grew older, had a family, and (hopefully) grew wiser, I realized that most of the time I hadn't be happier by making more money. Finding more money became a game, but the things that really helped me enjoy life were the challenges, the people, and the experiences I had in different places. It's not my advice, and it's not often followed, but it's advice I think it well worth following: do something with your life that you enjoy.

Read the rest of "WWBOD" at SQLServerCentral

At some point we transitioned to Turbo Pascal, which compiled hundreds of lines in a split second, on par with the speed of today's compilers, which are often working through thousands of lines of code. Is that a good thing, however? Has this speed improvement ended up building poor habits in developers?

Read the rest of "Coding More Carefully" at SQLServerCentral.

The article did make some good points about evaluating security for your company. You should understand what these certifications means, and in some cases, make sure the provider has multiple designations. For example, both ISO 27001 and ISO 27002 are needed together to ensure a reasonable level of security. The provider should also be able to provide you with copies of their audits, and contract with you to ensure ongoing audits and vulnerability tests. These are reasonable requests, and they are measures you should have in place for any of your facilities.

Read the rest of "Cloud Safety" at SQLServerCentral.

When a developer needs to reference data in another database (or on another server), they have a variety of ways in which they can do this. Some people prefer a three or four part naming convention, others use a view local to the database, and still others might use synonyms. While they all work, from a maintenance standpoint, I think a view or synonym provide a nice layer of abstraction while minimizing the potential maintenance headaches of future changes.

Read the rest of "Referencing Remote Data" at SQLServerCentral.

On one hand, I think this is a great idea for the browsers. It has the potential to not only ensure better security on the desktop, but potentially also making life easier for developers. If the browsers automatically update to the latest code, that means that the majority, or maybe all, of your clients will be running the same browser. That would greatly simplify the testing and coding requirements for developers.

Read the rest of "Are Auto-Updates Good?" at SQLServerCentral.

I'm sure there are similar examples of this for all software vendors, especially those that sell large software packages such as ERP applications. Some are probably without merit, and are the result of customers not fully understanding what they are buying, but some are probably valid complaints where salespeople have misled customers in order to complete a sale.

Read the rest of "Truth and Demos" at SQLServerCentral.

I was reading an interview with our main administrator, Simon, who also manages the SQLServerCentral servers, about the recent challenges of managing infrastructure for the DBA in Space contest. We had no idea how big the contest would be, and we knew that there might be a need to scale up rapidly to handle thousands of users accessing the site in a short period of time as new web-isodes of Brad's adventures were released.

Read the rest of "Cloud Patches" at SQLServerCentral.

It's the last Friday of the year, and rather than ask you about the resolutions you are making overall, I wanted to ask this question:

Read the rest of "The Data Resolutions" at SQLServerCentral.

The other big push in 2011 seems to have been "the cloud". It's everywhere, from consumer Windows 7 commercials to the updates to the SQL Server tools to support the SQL Azure platform. I haven't found many people that are excited about moving their databases to the cloud, but more and more people are testing the platform, and I suspect we'll start to see some apps that don't require high security or extremely high performance appearing in the cloud in 2012. I have embraced the cloud in many ways over the last couple years (Evernote, Dropbox, Live Mesh) and I find it to be an advantage in managing a busy life.

Read the rest of "The Year in Review - 2011" at SQLServerCentral.

Whether you think this software is legitimate or Carrier IQ and the carriers had the right to deploy it, you should be aware that from a public perspective this is a failure of software. It seems as though a back door of sorts, a spy program has been developed and approved by companies that sell cellular phone services, and it is a poor reflection of their business.

Read the rest of "Data and Privacy" at SQLServerCentral.

Those of us working in IT are very lucky for the most part. We have good jobs, jobs that don't require heavy physical exertions, we work in offices not in inclement weather, and we are paid well relative to many other professions.

Read the rest of "All I want for Christmas" at SQLServerCentral.

Part of social engineering is the inherent trust for others that most of us have. Part of it is the desire that most people have to help others. However I think a part of it is also the attitude that many workers have when they aren't treated well. When employees don't feel they are a part of the company family and just work for a paycheck, they are less vigilant or caring about safeguarding the digital assets, and sometimes physical assets, of the company.

Read the rest of "Pride and Security" at SQLServerCentral.

However we're only a small part of the SQL Server track. SQLskills.com headlines the track, as they have for many years, with Kimberly L. Tripp, Paul Randal, and Jonathan Kehayias presenting some amazing information based on their years of experience (go to one of the SQLskills.com classes if you can). Paul and Kimberly have also invited a number of other great speakers, including Aaron Bertrand, Allen White, Brent Ozar, Glenn Berry, Mike Walsh, and more. These are the people that write many of books, blogs, and articles that you read to learn more about the SQL Server platform.

Read the rest of "The Connections Launch Event" at SQLServerCentral.

However, carrying around a smartphone isn't without a risk. The features and capabilities of the various mobile operating systems are a double edged sword. The power of the smartphone can easily be used for attacks against your network. This piece talks about hackers targeting the mobile platforms as another attack vector. That's scary, especially as most of these mobile OSes were not designed to be secure.

Read the rest of "Be careful with your smartphone" at SQLServerCentral.

Many of you have replied that your companies are resistant to this, or your boss doesn't think it's a good idea. I have certainly had a few managers that felt that way, but I've also had success over time in changing their minds a bit. I've been able to get them to give me the chance to pilot ideas in a small way. Sometimes it's taken years, but I've learned to play "long ball" and think about succeeding over time, not getting my way this week.

Read the rest of "Propose this to your boss" at SQLServerCentral.

When I look at the SQLServerCentral architecture, while much smaller, still scales nicely on a single database server (clustered) and a web server. If I needed more performance, I'd hope that I could do something more similar to the setup at StackOverflow, with better development and fewer parts of my architecture than adding the type of complexity that powers Instagram.

Read the rest of "Jacks of all trades" at SQLServerCentral.

If you read the comments, there are all sorts of flaws and potential holes with encryption, which are valid arguments. However that doesn't mean that you shouldn't implement any encryption on your removable or portable drives, especially those in laptops. Those devices are like the locks on your home or car. They can be defeated by determined professionals, but all too often the casual criminal doesn't bother if they are in place.

Most of the time I've taken a job in the US, it's been an "at will" employment, with a verbal contract between me and the hiring manager or HR representative. Nothing was signed, and I essentially did whatever my manager wanted, regardless of my job title. That was fine with me. Currently I have a written contract, but the requirements for my position are a little vague and my duties aren't explicitly spelled out.

Read the rest of "The Employment Contract" at SQLServerCentral.

I've been proud to work on SQL Server over the last 6 years from a security perspective as there have been very few security patches issued, and correspondingly, few vulnerabilities disclosed. It's possible Microsoft has muzzled some researchers, but I doubt it. I would guess that if any serious security issues existed in SLQ Server 2005, 2008, or R2, we'd have heard about them. I think the security engineering process that is used for SQL Server has truly resulted in more secure software.

Read the rest of "Not So Unbreakable" at SQLServerCentral.

The post notes that the buffer pool will not grow beyond 64GB, though it doesn't mention limits in any of the other memory spaces that SQL Server uses. However assuming that the memory outside of the buffer pools scales, it might be time to think about installing extra instances of SQL Server on a single host if you are licensing by the core. With a commodity server costing under $10k with 6 cores and 96GB of RAM (no HDDs), one could easily consider placing 2-3 SQL Server instances on this hardware with each getting 24+GB of RAM.

Read the rest of "Sharing Your Database Server" at SQLServerCentral.

For the database administrator, however, this should be a wake-up call that lets you know you can't rely on the firewall to protect you. If you have a small 3 machine, one subnet network, maybe, but in most enterprises there are many subnets and complex rules to implement. That means that your company might not be a soft chewy center protected by a hard shell. It might be a soft center protected by Swiss cheese that does little to limit the influx of unauthorized requests.

Read the rest of "Layers of Security" at SQLServerCentral.

That's what TDE is designed for, but the machines that are most likely to be stolen, laptops that contain Express Edition instances, can't implement TDE. Why not? It's an "Enterprise only feature". Why? I assume this is a sales technique to force those companies required to implement data at rest protection will pay more for their instances, but in reality this results in less security for lots of SQL Server applications.

Read the rest of "Not having TDE in all editions is stupid" at SQLServerCentral.

However for most companies, the security is only examined when there is an actual issue. I know most IT people that manage web systems are told about security lapses when the site si defaced, or when your data is discovered posted in some other location.

Read the rest of "A Welcome Intruder" at SQLServerCentral.

One of the advantages of virtualized servers is that they can be moved from one set of physical hardware to another. If you find that your virtual machine (VM) is not receiving enough resources from the host, you can move it to another less busy host, and improve performance. What's even more amazing is that you can move this VM while it is in use. In fact, your clients may not even notice that the VM has migrated to another host, even while connected. To me, that's absolutely amazing.

Read the rest of "Fast Migrations" at SQLServerCentral.

This time, however, I tried something completely new. I didn't check my email from SQLServerCentral, visit the site, or do anything else work related during the time away. That's a first for me, as the last few years I've been pruning emails on my phone during vacation, handling minor items as I had time. It was hard, since my email client would show an ever increasing count of unread messages, but I made a point of not working during the time away.

Read the rest of "A Refreshing Break" at SQLServerCentral.

There was a time when I managed multiple DBAs and worked to remove them from meetings whenever possible. It was hard, with the workers always feeling like they wanted to know what was going on, and managers always wanting staff available for detailed updates if needed. Too often I felt that staff time in meetings, and performing updates, was wasted. Managers should take quick updates to meetings, and handle the coordination as much as possible.

Read the rest of "Thinking Time" at SQLServerCentral.

"What do you do?"

Read the rest of "What's Your Title?" at SQLServerCentral

This isn't good for your brand as a developer. If you don't know what SQL Injection is, you shouldn't be developing software. If you don't know how to code to avoid it, you shouldn't be hired by anyone to build software. If you can't write a stored procedure around a query or built a parameterized call to a database engine, you need to learn how or find another career.

Read the rest of "More SQL Injection" at SQLServerCentral.

And that's interesting. Developers, administrators, if you're administering databases in any way, you've got a chance to enter the contest. You can get started now by signing up and going through all the videos, answering the questions as you go. The contest ends Friday, November 18, 2011, so there are a few days left to follow Brad McGehee on his space alien adventure and have fun with a few silly questions.

Read the rest of "Do You Want to be a DBA in Space?" at SQLServerCentral.

In the two decades I've worked with SQL Server, there has been some advice that I've always given to people: don't backup to the network, and don't try to put a database on a file share. SQL Server hasn't dealt with either of those situations well for most of my career, and they've been a regular source of issues for clients and posters to the forums at SQLServerCentral. Network technology, while quickly improving, was still flaky enough that I always recommend that people keep their data and backups local as a guideline.

However technology evolves, and when it does, it's time for the advice to change. Lately I have seen more and more people making backups across the network that seem very reliable. Even the tendency of Ethernet protocols to delay packets when collisions occur is mitigated by the increasingly common 1Gbps and 10Gbps network speeds that many companies are using. While I might still be a little nervous about running backups across the network, that's my personal bias and I don't know if I would continue to recommend against those backups.

Read the rest of "Network Databases? Is it time for a change?" at SQLServerCentral

The majority of the people that I know working in technology do not seem to have college degrees in computer science. I know many people with degrees in many other subjects, and quite a few people that don't have a degree. In most of those cases, the successful individuals have worked in the real world and gathered their knowledge about technology through hard work across time. It also seems that many of the people I've met with CS degrees are often those that make he most mistakes in real world software development or system administration.

Colleges don't teach you all the skills you need in the real technology world. The best workers I know in this business are the most adaptable, thinking laterally about problems, and bringing flexible approaches to solving problems. With many surveys showing a shortage of technical talent likely in the next few years, we ought to be encouraging more people to enter the technology field.

Read the rest of "The Industry Problem" at SQLServerCentral.

Read the rest of "License by Core" at SQLServerCentral.

There seems to be a quest to move closer and closer to real time decision making. Gather data, analyze it, and make decisions instantly, preferably with the help oif expert systems. That makes some sense, and as shown in the article, it can allow analysts to respond to events very quickly, performing verification, fraud checks, or just about anything you can think of.

It's a good goal, and it can definitely help many companies make more informed decisions at any point in time. However there are problems as well. Sometimes short term data can fundamentally distort the picture of reality. Some of our large stock market meltdowns are the result of automated systems, perhaps not so much expert systems, as very quick reacting systems that might overvalue the last few pieces of data and make decisions that are less than optimal.

Read the rest of "Real Time Dangers" at SQLServerCentral.

Many authors write articles and speak about techniques that you can use to build more efficient applications. The most popular sessions given by speakers and requested by attendees are those that deal with improving performance. Writing better code, troubleshooting issues, and increasing the efficiency of our systems are under our control seem to be the priorities for most IT workers that I know. Every time we build something a little better, it's a great win for the author.

Read the rest of "Going Green in Software Development" at SQLServerCentral.