<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Physical on SQLNikon</title><link>https://sqlnikon.com/tag/physical/</link><description>Recent content in Physical on SQLNikon</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 16 Sep 2011 11:08:39 +0000</lastBuildDate><atom:link href="https://sqlnikon.com/tag/physical/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding SQL Server Instances</title><link>https://sqlnikon.com/2011/09/16/understanding-sql-server-instances/</link><pubDate>Fri, 16 Sep 2011 11:08:39 +0000</pubDate><guid>https://sqlnikon.com/2011/09/16/understanding-sql-server-instances/</guid><description>&lt;p&gt;Being raised within SQL Server 6.5 &amp;amp; 7.0, SQL Server instances were not available in those versions.  I never fully understood the advantage of having multiple instances on the same server so I never embraced it.  I always had a single, default instance per physical server.  Once I got involved with virtualization a few years ago, having multiple instances of an OS running on a single physical server finally got me thinking about multiple instances of SQL Server.&lt;/p&gt;</description></item></channel></rss>