If you missed Tech·Ed North America 2011, I have compiled a list of all the SQL Server videos for you. Each one links directly to the video, have fun watching it all Microsoft SQL Server Code-Named “Denali” AlwaysOn Series,Part 1: Introducing the Next Generation High Availability Solution Santosh Balasubramanian Database & Business Intelligence 300 – Advanced DBI302 Day 1 May 16, 2011 from 1:15PM to 2:30PM In this session we talk about the new high availability solution that is being introduced in SQL Server code-named “Denali”.
This is an archive of the posts published to LessThanDot from 2008 to 2018, over a decade of useful content. While we're no longer adding new content, we still receive a lot of visitors and wanted to make sure the content didn't disappear forever.
Introduction From time to time you want to let your users browse for a certain file and save that path somewhere. The users will usually go to their mapped folder and select a file from there. Then the filedialog will give you the path on that mapped drive. But that mapping might not exists on another drive so we should better save the UNC path since we then no longer depend on the mapping to be there when we want to get the file the next time.
This one slipped by me Microsoft .NET Framework 4 Platform Update 1. So we now have a new version of the .Net framework, but they didn’t give it a new version number, they used some manager talk and a KB number. And let’s not forget that there is a client profile with the same name, did I mention I hate the client profile? And why is it made the default?
So recently I found out that process kills developer passion. Actually I found out over and over, as numerous people sent me the link. In fact, I even heard certain past co-workers silently wishing they could send me the link (well, they would if they had read it, anyway). Except I didn’t really learn about processes killing developer passion, what I learned was that best practices take a lot of time away from programming and, what’s more, are generally followed poorly.
Today’s tip is a short but powerful one. On many occasions a DBA is forced to deal with files in some way. It may be the need to download and move a file (or folder) around in order to prepare for importing the contents into a database or simply maintain the contents or auditing levels of them. Working with files through SQL Server is more difficult than your everyday select of data from a database.
Back in January, Lara Rubbelke (Blog | Twitter) and I released V2 of the Separation of Duties Framework for SQL Server. If you haven’t checked it out yet I suggest you do. It’s a framework that helps you design a more restrictive and granular environment for administration within SQL Server. Originally, Lara released the first version during the 2010 PASS Summit and was gracious enough to allow me to collaborate with her afterwards.
Books are not a substitute for personal experience, but neither is the world a boolean place. Ignoring the experiences of others is akin to re-inventing the wheel just so we can learn how to drive. Given how long it took to develop the wheel the first time, there’s probably more productive ways we could spend our time. The combination of good books and our own experiences can help us advance our skillset, understand common methods instead of having to reinvent them, and learn a common language and terminology that other will be able to understand.
Complexity of Job Ownership When a SQL Server Agent Job is created, the creator of the job is, by default, the owner of the job. This can be important depending on the steps that the job is performing. When a SQL Server Agent job runs, the agent uses SETUSER to impersonate the owner of the job for the steps. For example, if a job is executed that has two steps that are TSQL statements and the owner of the job has the needed security to run those TSQL statements, the job will run successfully.
A colleague of mine told me this neat trick which I had to share: echo "FIGNORE=.svn" >> ~/.bashrc source ~/.bashrc Now when you’re moving around subversion controlled directories with only one subdirectory, hitting tab won’t try to autocomplete to “.svn/”.
Updating large volumes of production data is a common task for a DBA. This task falls into the level of responsibility that has been given to the DBA role in faith that the proper steps are taken to ensure the integrity of the data before and after the update. One problem that can arise from years of performing updates of this kind; at times a DBA may let their guard down and write an update quickly or with too much confidence and not take the needed steps to ensure the update, successful or not, is keeping the integrity of the data and recovery points in mind.