Here at Topline, I personally tend to spend most of my time writing C# code and T-SQL. In the last year or two, however, in a game of tag that I didn't realize I was playing, I have become "it" when it comes to UI design. As a result, I have spent a lot of evenings learning CSS, and, contrary to what I supposed at the outset, I have grown to enjoy quite a bit. That being said, I am still learning and from time to time I encounter new and earth-shattering principles off CSS design that I have somehow missed before.
You are here
“For a small business, Office 365 is a perfect way to start,” said Rob Nichols, chief technology officer of Allovus Design, a graphic design firm and member of Microsoft’s Customer Advisory Board for Office 365. “It has all the features we need, and we can come out of the gate with the same tools the big guys have — on day one.”
During a recent purge/archive project I needed to compare two tables in different SQL Server databases to see if the schemas were the same. Basically, I was moving data from a production database to an archive database and if new fields were added or changed to any of the production tables, I needed to know and sync those changes to the related archive tables. Below are two stored procedures that I created initially in the master database to simplify the process and to allow the stored procedures to be executed from any database.
Common table expressions, a feature introduced by Microsoft SQL Server 2005, are a very powerful feature that may be used in lieu of temporary tables. They may be thought of as a temporary result set that is defined within the execution scope of a query. Using a common table expression you are able to create a reference to itself, which exposes a recursive ability that is very helpful for identifying a hierarchy amongst table elements. For our example we will use NorthWind's employee table.