If you’re trying to export data in Windows to a UTF-8 format you may be wondering which code page you should use. Well the riddle is solved. Code Page 65001 is the equivalent of UTF-8. If you need to create an SSIS package to export data as UTF-8 for consumption by a unix system you should take a look at the post SSIS Export To UTF-8 or UNIX (or how to set your code page to output a flat file for…
As more and more companies are moving to heterogenous environments with both windows and unix systems the life of the Microsoft SQL Server developer is becoming much more interesting. For our recent data warehouse project I was asked to create a SQL Server 2012 Integration Services (SSIS) ETL package to output a text file for consumption by another system. No problem! I can do that in my sleep!…
Ummm, what version of GreenPlum am I running? (Which is the same as asking: What version of Postgres am I running?) There are a few easy ways to figure this out but I’ll stick with the SQL since that’s the most universal:
For some reason no one has ever trusted me enough to let me help administer the active directory groups. This means I’m always adding database perms to groups somewhat blindly, hoping the group names are intuitive enough that I can deduce who’s in them. Enter the magic of the command line! TUrns out you can view the members of an AD group with a quick trip to the command prompt. Witness: (more…)
~ Etiquette; Or, A Guide To The Usages of Society, by Count Alfred D’Orsay, 1843
And science supports this!(via currentsinbiology)
I admit, this post is primarily to provide a place for me to copy and paste my own code, but it’s so sweet I figured some of you other SQL Server Data Tool Users might find it handy.
When troubleshooting the generated deployment scripts I’ve always added a PRINT statement to indicate the beginning and ending of the pre and post deploy section. But, a post by SSDT kingpin Jamie Thompsonmade my…