<?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>ASP.NET MSSQL Webhosting Blog &#187; Microsoft SQL</title>
	<atom:link href="http://www.mywebhostingblog.net/tag/microsoft-sql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mywebhostingblog.net</link>
	<description>ASP.NET, MSSQL and Windows dedicated server articles</description>
	<lastBuildDate>Tue, 10 Nov 2009 19:53:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>About MSSQL Server</title>
		<link>http://www.mywebhostingblog.net/mssql-server-hosting/about-mssql-server/</link>
		<comments>http://www.mywebhostingblog.net/mssql-server-hosting/about-mssql-server/#comments</comments>
		<pubDate>Tue, 17 Mar 2009 06:36:32 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[MSSQL Server]]></category>
		<category><![CDATA[Microsoft SQL]]></category>
		<category><![CDATA[MSSQL]]></category>
		<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.mywebhostingblog.net/?p=29</guid>
		<description><![CDATA[The architecture of Microsoft MSSQL Server is mainly divided into three components: 1. SQLOS: which implements the basic services required by MS SQL Server, including thread scheduling, I/O stat management and memory management. 2. Relational Engine: which implements the relational database components including support for databases, tables, queries and stored procedures as well as implementing [...]]]></description>
			<content:encoded><![CDATA[<p>The architecture of <strong>Microsoft MSSQL Server</strong> is mainly divided into three components:</p>
<p>1. <strong>SQLOS</strong>: which implements the basic services required by <strong>MS SQL Server</strong>, including thread scheduling, I/O stat management and memory management.</p>
<p>2. <strong>Relational Engine:</strong> which implements the relational database components including support for databases, tables, queries and stored procedures as well as implementing the type system.</p>
<p>3. <strong>Protocol Layer:</strong> which exposes the <strong>MS SQL Server </strong>functionality.</p>
<p><strong>SQLOS</strong></p>
<p><span id="more-29"></span></p>
<p>SQLOS is the base component in the <strong>Windows</strong> <strong>SQL Server</strong> architecture. It implements functions normally associated with the <strong>Operating System</strong>, thread scheduling, memory management, I/O management, buffer pool management, resource management, synchronization primitives and locking, and deadlock detection. Because the requirements of <strong>Windows SQL Server</strong> are highly specialized, it implements its own memory and thread management system, rather than using the generic one implemented in the OS. <strong>SQLOS</strong> also includes synchronization primitives for locking as well as monitoring for the worker threads to detect and recover from deadlocks.</p>
<p><strong>SQLOS</strong> handles the memory requirements of <strong>MS SQL Server</strong> as well. Reducing disc I/O is one of the primary goals of specialized memory management in SQL Server. It maintains a buffer pool, which is used to cache data pages from the disc, and to satisfy the memory requirements for the query processor, and for other internal data structures. <strong>SQLOS</strong> monitors all the memory allocated from the buffer pool, ensuring that the components return unused memory to the pool, and shuffles data out of the cache to make room for newer data. For changes that are made to the data in buffer, <strong>SQLOS</strong> writes the data back to the disc lazily, that is when the disc subsystem is either free, or there have been significant numbers of changes made to the cache, while still serving requests from the cache. For this, it implements a Lazy Writer, which handles the task of writing the data back to persistent storage.</p>
<p><strong>WIndows SQL Server</strong> normally supports up to 2 GB memory on x86 hardware, though it can be configured to use up to 64 GB if the Address Windowing Extension is used in the supporting operating system. For x64 hardware, it supports 8 TB of memory, and 7 TB for IA-64 systems (currently it is limited by Windows Server 2003 SP1 to 1TB). However, when running x86 versions of SQL Server on x64 hardware, it can access 4 GB of memory without any special configuration.</p>
<p><strong>Relational Engine:</strong></p>
<p>The Relational engine implements the relational data store using the capabilities provided by<strong> SQLOS</strong>, which is exposed to this layer via the private <strong>SQLOS</strong> API. It implements the type system, to define the types of the data that can be stored in the tables, as well as the different types of data items (such as tables, indexes, logs etc) that can be stored. It includes the Storage Engine, which handles the way data is stored on persistent storage devices and provides methods for fast access to the data. The storage engine implements log-based transaction to ensure that any changes to the data are ACID compliant. It also includes the query processor, which is the component that retrieves data. <strong>MSSQL</strong> queries specify what data to retrieve, and the query processor optimizes and translates the query into the sequence of operations needed to retrieve the data. The operations are then performed by worker threads, which are scheduled for execution by <strong>SQLOS</strong>.</p>
<p><strong>Protocol Layer:</strong></p>
<p>Protocol layer implements the external interface to <strong>MS SQL Server.</strong> All operations that can be invoked on <strong>MSSQL Server</strong> are communicated to it via a <strong>Microsoft</strong>-defined format, called Tabular Data Stream (TDS). TDS is an application layer protocol, used to transfer data between a database server and a client. Initially designed and developed by Sybase Inc. for their Sybase <strong>MS SQL Server</strong> relational database engine in 1984, and later by Microsoft in <strong>Microsoft MS SQL Server</strong>, TDS packets can be encased in other physical transport dependent protocols, including TCP/IP, Named pipes, and Shared memory. Consequently, access to <strong>MSSQL Server</strong> is available over these protocols. In addition, the <strong>MSSQL Server</strong> API is also exposed over web services.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mywebhostingblog.net/mssql-server-hosting/about-mssql-server/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Difference between SQL Server 2005 and SQL Server 2008</title>
		<link>http://www.mywebhostingblog.net/aspnet-web-hosting/difference-between-sql-server-2005-and-sql-server-2008/</link>
		<comments>http://www.mywebhostingblog.net/aspnet-web-hosting/difference-between-sql-server-2005-and-sql-server-2008/#comments</comments>
		<pubDate>Wed, 14 Jan 2009 14:55:49 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[ASP.NET Web Hosting]]></category>
		<category><![CDATA[MSSQL Server]]></category>
		<category><![CDATA[Window Hosting]]></category>
		<category><![CDATA[Cluster]]></category>
		<category><![CDATA[Difference]]></category>
		<category><![CDATA[Microsoft SQL]]></category>
		<category><![CDATA[MSSQL]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[SQL 2005]]></category>
		<category><![CDATA[SQL 2008]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.mywebhostingblog.net/?p=455</guid>
		<description><![CDATA[MS SQL 2005 Server was released after 5 servers of it previous SQL version, MS SQL 2000, Hence it required allot to revisions to cope up with the current windows development environment. Therefore MS SQL 2005 SP2 had major changes in it, with too many performances and security fixes. Microsoft could not add few revisions [...]]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-456 alignleft" title="difference-between-2005-2008" src="http://www.mywebhostingblog.net/wp-content/uploads/2009/03/difference-between-2005-2008.jpg" alt="difference between 2005 2008 Difference between SQL Server 2005 and SQL Server 2008" width="200" height="252" /></p>
<p><strong>MS SQL 2005 Server</strong> was released after 5 servers of it previous SQL version, <strong>MS SQL 2000</strong>, Hence it required allot to revisions to cope up with the current <strong>windows </strong>development environment. Therefore <strong>MS SQL 2005 SP2</strong> had major changes in it, with too many performances and security fixes. Microsoft could not add few revisions due to its basic development structure however they had all the scope to introduce them in SQL 2008 release. And indeed, MS <strong>SQL 2008</strong> has many installation as well as <strong>performance </strong>fixes being applied to it and allowing <strong>Windows</strong> Administrators to have full control on <strong>SQL </strong>activities. The biggest advantage of <strong>SQL 2008</strong> over <strong>SQL 2005</strong> is the ability to manage and maintain server performance. <strong>SQL 2008</strong> does not require too much resource which is the best deal for today’s <strong>Shared Hosting</strong> environment. Also an upper hand to whose to do not want to invest too much on hardware of their <strong>dedicated servers</strong> just to run <strong>SQL server</strong> on it.</p>
<p><span id="more-455"></span></p>
<p><img class="alignright size-medium wp-image-458" title="difference-between-sql-server1" src="http://www.mywebhostingblog.net/wp-content/uploads/2009/03/difference-between-sql-server1-235x300.jpg" alt="difference between sql server1 235x300 Difference between SQL Server 2005 and SQL Server 2008" width="159" height="203" />I have tried to gather the major improvement introduced by <strong>Microsoft on SQL 2008</strong> from Internet which is an advantage over <strong>SQL 2005</strong> however it all depends on what features are useful to you in the development of your ASP .NET applications. But switching to <strong>Microsoft SQL 2008</strong> is definitely going to improve the performance even if you don&#8217;t use any of the below feature. And not to forget that with the release of SQL 2008, Microsoft will announce<em><strong> &#8220;End Of Life&#8221;</strong></em> for <strong>SQL 2000</strong> version, which will mean that there won&#8217;t be any official support or update release for SQL 2000.</p>
<p><strong>Major difference between SQL 2005 and SQL 2008.</strong></p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-463" title="sql 2008 dedicated hosting" src="http://www.mywebhostingblog.net/wp-content/uploads/2009/03/sql-2008-hosting.png" alt="sql 2008 hosting Difference between SQL Server 2005 and SQL Server 2008" width="363" height="75" /></p>
<p>* <em>Easy Upgrades:</em> Version <strong>upgrades </strong>are now very easy and effective with <strong>SQL 2008</strong>.<br />
* <em>Resource Restriction Governor:</em> We set a restriction on a users or groups from consuming high resources. This is a very good feature that can be used on <strong>Windows shared serve</strong>r with SQL database to maintain the performance.<br />
* <em>Dates and Times settings: </em>New data types such as: Date, Time, Date Time Offset has been introduced.<br />
* <em>Improved Full Text Search:</em> Ability to backup Native Indexes and also thesaurus them as metadata.<br />
* <em>External Key Management:</em> This unique can store Keys separately and not with the data.<br />
* <em>Improved SQL Server Analysis Service:</em> It now has improved Stacks and computes block faster.<br />
* <em>Improved Installation:</em> Microsoft has added an option where you can uninstall Disk images and service packs.<br />
* <em>Data Synchronizing:</em> A Development of databases used in applications that frequently get disconnected.<br />
* <em>Transparent Data Encrypts:</em> It has the ability to encrypt full <strong>SQL database </strong>with different encryption Methods.</p>
<p>* <em>SQL Server Integration Service:</em> SQL 2008 Server has improved multiprocessor support and faster lookups in compare to SQL 2005.<br />
* <em>Change Data Capture:</em> Allows all changes to be captured and queried. (Enterprise). Also allows us to get detailed information on what changes has happened to which rows after a specific version.<br />
* <em><strong>LINQ:</strong></em> A Development query language for accessing multiple type of data like XML and SQL at the same time.<br />
* <em>Hot Plug CPU:</em> With this feature to an add CPUs on fly for your SQL server to use.<br />
* <em><strong>Microsoft Office 2007 integration:</strong></em> One can use MS OFFICE as an SSRS template, like SSRS to WORD.<br />
* <em>Spatial Data types:</em> Data types for storing Longitude, Latitude and GPS entry of a particular database.<br />
* <em><strong>MERGE:</strong></em> A new TSQL command as a combination Update, Insert and Delete.<br />
* <em><strong>Encrypted Backups: </strong></em>We can execute it at the time running backups to prevent tampering from external resource.<br />
* <em><strong>Data Compression:</strong></em> This feature is different as it allows us to manage data compression at table level to enhance performance.<br />
* <em>Dynamic Development:</em> Latest Visual Studio and ADO options along with ASP .Net 3.<br />
* <em>Reporting Server Performance: </em>Unlike in SQL 2005 we can set threshold on Reporting server for memory management.<br />
* <em>Performance Studio:</em> It is a Gallery that has collection of monitoring tools enhanced performance.<br />
* <em><strong>Audits:</strong></em> A very power feature for monitoring the data access of your SQL database.<br />
* <em><strong>Table Value Parameters:</strong></em> SQL 2008 database has ability to insert entire table into a stored procedure.<br />
* <em>Entity Database Services:</em> (LOB) Line Of Business framework and (eSQL) Entity Query Language.</p>
<p>No doubt that <strong>Microsoft </strong>has improved all the features that has been used by <strong>hosting services</strong>. Even <strong>SQL Cluster</strong> in <strong>version 2008</strong> has few major advantages since every one in today world wants to have their site up all the time with<strong> 100% uptime</strong>. I hope I get some time to write on &#8220;<em><strong>MS SQL 2008 Clustering..</strong></em>&#8220;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mywebhostingblog.net/aspnet-web-hosting/difference-between-sql-server-2005-and-sql-server-2008/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
