<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Blog of Travis Gneiting &#187; SQL Server</title>
	<atom:link href="http://www.blog.travisgneiting.com/category/sql-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blog.travisgneiting.com</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2012 03:45:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	
	
	<!-- google ad injected by adsense-optimizer http://www.adsenseoptimizer.de -->
	<div  style="padding:7px; float: right; padding-right: 0; margin: 3px;"><!-- Ad number: 1 --><script type="text/javascript"><!--
    	 
    	google_ad_client = "pub-3961093531196233"; google_alternate_color = "FFFFFF";
		google_ad_width = 200; google_ad_height = 200;
		google_ad_format = "200x200_as"; google_ad_type = "text_image";
		google_ad_channel ="1685894941"; google_color_border = "336699";
		google_color_link = "0000FF"; google_color_bg = "FFFFFF";
		google_color_text = "000000"; google_color_url = "008000";
		google_ui_features = "rc:0"; //--></script>
		<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script></div>	<item>
		<title>Deploying SQL Server Database to Exsisting Production Database</title>
		<link>http://www.blog.travisgneiting.com/2010/08/30/deploying-sql-server-database-to-exsisting-production-database/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=deploying-sql-server-database-to-exsisting-production-database</link>
		<comments>http://www.blog.travisgneiting.com/2010/08/30/deploying-sql-server-database-to-exsisting-production-database/#comments</comments>
		<pubDate>Mon, 30 Aug 2010 12:49:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Deployment]]></category>

		<guid isPermaLink="false">http://www.blog.travisgneiting.com/?p=158</guid>
		<description><![CDATA[Here is a good link from MSDN that explains how to deploy database changes to an exsisting database. http://msdn.microsoft.com/en-us/library/ff754344.aspx]]></description>
			<content:encoded><![CDATA[<!-- google_ad_section_start --><p>Here is a good link from MSDN that explains how to deploy database changes to an exsisting database.</p>
<p><a title="Database Deployment" href="http://msdn.microsoft.com/en-us/library/ff754344.aspx" target="_blank">http://msdn.microsoft.com/en-us/library/ff754344.aspx</a></p>
<!-- google_ad_section_end -->]]></content:encoded>
			<wfw:commentRss>http://www.blog.travisgneiting.com/2010/08/30/deploying-sql-server-database-to-exsisting-production-database/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL Server Import of Country, State, Zip, From GeoNames.Org</title>
		<link>http://www.blog.travisgneiting.com/2010/02/12/sql-server-import-of-country-state-zip-from-geonames-org/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sql-server-import-of-country-state-zip-from-geonames-org</link>
		<comments>http://www.blog.travisgneiting.com/2010/02/12/sql-server-import-of-country-state-zip-from-geonames-org/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 18:12:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.blog.travisgneiting.com/?p=70</guid>
		<description><![CDATA[A few post have been made with complex solutions for importing information from GeoNames.org into SQL Server.  These involved downloading converters to change the file from UTF-8 encoding and downloading additional software (EditPad Pro) to complete the conversion to UTF-16. A much simpler way is to open the txt file in Microsoft Excel. Let Excel [...]]]></description>
			<content:encoded><![CDATA[<!-- google_ad_section_start --><p>A few post have been made with complex solutions for importing information from GeoNames.org into SQL Server.  These involved downloading converters to change the file from UTF-8 encoding and downloading additional software (EditPad Pro) to complete the conversion to UTF-16.</p>
<p>A much simpler way is to open the txt file in Microsoft Excel. Let Excel perform it&#8217;s magic on the tab delimited file.</p>
<p>Add the headers to the top row:</p>
<pre>The main 'geoname' table has the following fields :
---------------------------------------------------
geonameid         : integer id of record in geonames database
name              : name of geographical point (utf8) varchar(200)
asciiname         : name of geographical point in plain ascii characters, varchar(200)
alternatenames    : alternatenames, comma separated varchar(5000)
latitude          : latitude in decimal degrees (wgs84)
longitude         : longitude in decimal degrees (wgs84)
feature class     : see http://www.geonames.org/export/codes.html, char(1)
feature code      : see http://www.geonames.org/export/codes.html, varchar(10)
country code      : ISO-3166 2-letter country code, 2 characters
cc2               : alternate country codes, comma separated, ISO-3166 2-letter country code, 60 characters
admin1 code       : fipscode (subject to change to iso code), see exceptions below, see file admin1Codes.txt for display names of this code; varchar(20)
admin2 code       : code for the second administrative division, a county in the US, see file admin2Codes.txt; varchar(80)
admin3 code       : code for third level administrative division, varchar(20)
admin4 code       : code for fourth level administrative division, varchar(20)
population        : bigint (4 byte int)
elevation         : in meters, integer
gtopo30           : average elevation of 30'x30' (ca 900mx900m) area in meters, integer
timezone          : the timezone id (see file timeZone.txt)
modification date : date of last modification in yyyy-MM-dd format

Then save the Excel file. Use SQL Server import to import the Excel file and your done.</pre>
<!-- google_ad_section_end -->]]></content:encoded>
			<wfw:commentRss>http://www.blog.travisgneiting.com/2010/02/12/sql-server-import-of-country-state-zip-from-geonames-org/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

