Blog Feed Info

This page provides an aggregate of feeds from Colorado SQL community members that blog about SQL Server.  If you live in Colorado and would like your fieed listed, please send us an email at and let us know.

ColoradoSQL Bloggers

Tuesday, April 15, 2014 9:01:11 AM

PASS SQL Saturday is a training event for SQL Server professionals and those wanting to learn about SQL Server. Please note that in order to attend one of these event, you must register. Please register soon as seating is limited, and let friends and colleagues know about the event. Most events are free, however a nominal fee may be charged so that lunch may be provided (not pizza). View future events on the SQLSaturday website.

The post PASS SQLSaturday Events: May 2014 appeared first on DawaBI.

Monday, April 14, 2014 8:51:48 AM
SQL Saturday #297   On April 12th we had the 3rd SQL Saturday hosted in Colorado Springs, Co. The event meet and exceeded all of our goals, our goals may not line up with some of the other SQL Server Saturday traditional goals you may have heard of. We share similar goals of reaching the […]
Thursday, April 10, 2014 10:21:05 AM
SQLSaturday #297 in Colorado Springs is this coming Saturday! If you haven't registered yet, why not? It's a free event that has the best SQL Server professionals traveling from all over to present and attend this awesome event. If you able to make into Colorado Springs by Saturday, you should be at the event! I will be presenting "Capture Change and Apply it With Change Data Capture & SSIS" at 3:15pm (keep your eyes on the schedule page or use the Guidebook app to track any changes to the schedule). I'm looking forward to seeing everyone this Saturday, make sure you register and support all of the sponsors of this event when you are there.

Below are some more details from Chris Shaw's blog about the food drive that is also being done as part of the event:
What we are asking is that when you come to the event on April 12th that you bring with you food items that you would like to donate the more items that you bring the better your odds are in taking home one of these awesome SWAG items. We will soon be sending everyone who is signed up more details on individuals can participate in our food drive. You don’t have to bring any food items to be registered for the giveaways and there will be opportunities to participate in our Data-Rodeo for additional chances to win. Why a Data-Rodeo you ask? This year’s theme in going to be centered around the old west, our event will be taking place in a historical building that is over 100 years old, in the heart of the oldest part of town.
See y'all on Saturday!
Tuesday, April 08, 2014 12:27:12 PM

SQL Meetings are training events for SQL Server professionals and those wanting to learn about SQL Server. Please note that in order to attend one of these event, you must register. Please register soon as seating is limited, and let friends and colleagues know about the event. Most events are free, however a nominal fee may be charged so that lunch may be provided (not pizza).

The post Colorado SQL Events for April 2014 appeared first on DawaBI.

Wednesday, April 02, 2014 1:55:01 PM
Microsoft quietly released SSDT-BI for Visual Studio 2013 as a separate download a couple of days ago: No blog post or anything yet that goes through all of the features, so my assumption is it just adds the same functions that SSDT-BI for Visual Studio 2012 does for the latest version of Visual Studio (at least until later this year when Visual Studio 2014 is released). I also assume that this adds support for SQL Server 2014 BI, same as the previous updates for SSDT have done now for Visual Studio 2012 and 2013.

Just for review, SSDT-BI is for SSAS, SSIS and SSRS development. For database projects, they have now built that functionality back into all versions of Visual Studio 2013 (available as a separate download for Visual Studio 2012) and can be updated via Visual Studio 2013 directly. For more updates on SSDT, make sure you follow the SQL Server Data Tools Team blog.

Update: At about the same time I posted this Kasper de Jonge posted about SSDT-BI for Visual Studio 2013. Biggest disappointment is that there is NO backwards compatibility with SSIS 2012 or SSIS 2008R2 projects, so if you are only doing SSIS development on previous versions of SQL Server, don't jump on this upgrade just yet. No explanation was given for this incompatibility or if it will be fixed in a future update. Just keeps getting more and more complicated.
Wednesday, March 26, 2014 9:32:08 AM
If you haven’t noticed, SQL Saturday #279 in Phoenix this weekend has 3 great BI pre-cons that are scheduled for Friday, March 28.  The pre-cons are held at the Microsoft Office in Tempe, AZ and run from 8:30AM – 4:00PM. There is still time to register! I’ll be presenting Predictive Analytics in the Enterprise, showing […]
Wednesday, March 26, 2014 2:56:22 AM
Microsoft has announced that a new version of SSDT for Visual Studio 2012 is now available for download and that an update for Visual Studio 2013 will be released through the update tools built into VS 2013. This new version adds support for SQL Server 2014, which will be available next Tuesday (April 1st). Along with support for SQL Server 2014 there are some new features in SSDT, including:

  • Filtering Data when using View Data - filter the rows shown and even hide columns along with applying aliases to columns and sorting the data by columns
  • Azure Integration - Add and connect to Azure databases without needing to setup firewall rules or other complicated network setup
  • Change T-SQL Query Connections - Change the database that the query window is current attached to so that you can execute the same query against another database without having to disconnect and connect

There are few other new features that I have not mentioned, make to check out the SQL Server Data Tools Team blog for more details!

This release is for the data tools portion of SSDT only, SSDT-BI for SSAS, SSIS and SSRS development will be released separately at a later date.
Tuesday, March 25, 2014 10:44:37 AM
Finally, the last part in my Encryption in SQL Server series that I started at the end of 2013! If you have not been following along, please see Part 1, Part 2 and Part 3 before reading this post.

Now that you have data in your databases encrypted and hopefully you have automatic backups setup against these databases, you are probably wondering how you can restore these backups while maintaining the encryption. If you are restoring to the same server and you have not made any changes to the Service Master Key (SMK) it will all work seamlessly.

If however you are restoring the backup or attaching a database with encryption to another server that does not have the same SMK you will need to take a couple of extra steps to get the encrypted data visible and encrypt new data working. Keep in mind that the SMK is the key that is generated at the time the SQL Server instance is installed on the server and you have no control over how that key is created. This SMK is used as part of the whole encryption setup on the server, so you may think that all is lost, but Microsoft has put in place some commands that will still allow you to access the encrypted data and encrypt new data into that restored/attached database.

After restoring/attaching the database to the new instance, run the commands below in order.

Restore Service Master Key (SMK), but only if this instance has no other encryption currently setup on it. If you do have encryption already on this instance, just skip this step and move on to restoring the DMK and modifying it to use the SMK (based on backup sample shown in Part 1):
    FROM FILE = 'C:\localhost_SMK.smk'
    DECRYPTION BY PASSWORD = 'ADa329wopkj*&ER.slkqksl';
 Restore the Database Master Key (DMK):
RESTORE MASTER KEY FROM FILE = 'C:\localhost_AdventureWorks_DMK.dmk'             DECRYPTION BY PASSWORD = 'U982LKJOWlkslpq&^@#lskjnkxOPx.w'                     ENCRYPTION BY PASSWORD = 'Ils20*(LKjqwnslqo372,cklweLKHJn'
Next we want to alter the DMK to use the SMK for encryption, otherwise the DMK will have to opened every time we want to do any encryption/decryption:
    DECRYPTION BY PASSWORD = 'Ils20*(LKjqwnslqo372,cklweLKHJn';
Now we need to create the Asymmetric and Symmetric Keys that we created previously in Part 2, in the same way they were created previously as we could not back up these since they were not created in certificates (if you did decide to create these keys with certificates and you have the back ups, then you can just restore the certificates):
 (SELECT * FROM sys.asymmetric_keys WHERE [name] = 'AdventureWorks_AsymKey')
    (SELECT * FROM sys.symmetric_keys WHERE [name] = 'AdventureWorks_SymKey')
    CREATE SYMMETRIC KEY AdventureWorks_SymKey
        WITH KEY_SOURCE = 'I82xskoiw820KOW>282kxow',
            ALGORITHM = AES_256,
            IDENTITY_VALUE = 'w,xi292XWE82S92iqoxl*&23'
        ENCRYPTION BY ASYMMETRIC KEY AdventureWorks_AsymKey; 
It is important that you use the same KEY_SOURCE and IDENTITY_VALUE when re-creating the Symmetric Key as this and the Asymmetric Key were used to do the initial encryption of the back-up and if these values are not the same the decryption of the previous data will not work.
Once all of these steps are complete you will be able to use the same commands we used in Part 3 to verify that the decryption works correctly:
SELECT Phone_encrypt, Phone,
CONVERT(nvarchar(25),DecryptByKeyAutoAsymKey(AsymKey_ID('AdventureWorks_AsymKey'), NULL, Phone_encrypt, 0)) AS 'CustomerPhone_decrypted' FROM Person.Contact;
SELECT Phone_encrypt, Phone, CONVERT(nvarchar(25),DecryptByKey(Phone_encrypt))) AS 'CustomerPhone_decrypted' FROM Customer.Contact; 
CLOSE SYMMETRIC KEY AdventureWorks_SymKey;
With these steps and the previous posts in this series you should be able to take full advantage of encryption in SQL Server and have full control of that encrypted data on any of your servers/instances. With all of the data breaches that are occurring today it is even more important for you to make sure any sensitive information you have in your database is protected and this is a great way to do it in SQL Server without causing a major impact to you existing systems.

Monday, March 24, 2014 9:41:27 AM
I was recently having a discussion with a client and they were looking for recommendations on how to handle a common security issue with SQL Server. Here is there situation, they have a number of applications that connect to the database, and security was implemented by using Windows Authentication. The application required read and write […]
Tuesday, March 18, 2014 7:10:53 AM
Microsoft officially announced today on the SQL Server Blog that SQL Server 2014 will be released on April 1st! Always find it funny that Microsoft will release products on April Fools Day, but to them I guess it is just the beginning of another month and quarter for them. For those that are just getting upgraded to SQL Server 2012, now you will already be one version down after April 1st.

In past years this release would have been called SQL Server 2012 R2, but thankfully they have decided to drop the R2 (Release 2) naming on SQL Server products (it is still being used on Windows Server and other server products). See the official blog entry for a list of the new features, mostly just enhancements to the features added in SQL Server 2012. The best new feature that I see is the enhancement to In-Memory ColumnStore Indexes making them updatable! There is also the feature of being able to backup right to Azure, which is great for providing instant off-site backups for your databases.

If you want to be notified of the official release, click here and fill out the form.
Page 1 of 4 1 2 3 4 > >>