<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblogcasts.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">StevenWhite</title><subtitle type="html" /><id>http://sqlblogcasts.com/blogs/stevenwhite/atom.aspx</id><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/stevenwhite/default.aspx" /><link rel="self" type="application/atom+xml" href="http://sqlblogcasts.com/blogs/stevenwhite/atom.aspx" /><generator uri="http://communityserver.org" version="3.1.20917.1142">Community Server</generator><updated>2006-02-14T08:54:00Z</updated><entry><title>Microsoft recommendations on SQL Server service accounts.....</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/08/27/981.aspx" /><id>http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/08/27/981.aspx</id><published>2006-08-27T13:21:00Z</published><updated>2006-08-27T13:21:00Z</updated><content type="html">&lt;P&gt;I've been spending some time reading up on the SQL 2005 Papers.&lt;BR&gt;If you haven't taken a look, there is lots of interesting things to read. Well worth a browse espically the operations section. &lt;A href="http://www.microsoft.com/technet/prodtechnol/sql/2005/library/default.mspx"&gt;http://www.microsoft.com/technet/prodtechnol/sql/2005/library/default.mspx&lt;/A&gt;)&lt;br&gt;Anyway it would be nice to see consistant advice from MS about sql service accounts....&lt;/P&gt;
&lt;P&gt;In&amp;nbsp;the&amp;nbsp; 'Setting Up Windows Service Accounts'&amp;nbsp;&amp;nbsp;document is states &lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Microsoft recommends that you do not use the Network Service account for the SQL Server or SQL Server Agent services. Local User or Domain User accounts are more appropriate for these SQL services. &lt;BR&gt;&lt;/EM&gt;(&lt;A href="http://msdn2.microsoft.com/en-us/library/ms143504.aspx"&gt;http://msdn2.microsoft.com/en-us/library/ms143504.aspx&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;Whereas in the 'Physical Database Storage Design' paper&amp;nbsp; it recommends '&lt;EM&gt;Use the Windows Network Service Account for security&lt;/EM&gt;.'&lt;BR&gt;(&lt;A href="http://www.microsoft.com/technet/prodtechnol/sql/2005/physdbstor.mspx"&gt;http://www.microsoft.com/technet/prodtechnol/sql/2005/physdbstor.mspx&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;Happy Reading&lt;BR&gt;Steven&lt;/P&gt;&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=981" width="1" height="1"&gt;</content><author><name>StevenWhite</name><uri>http://sqlblogcasts.com/members/StevenWhite.aspx</uri></author></entry><entry><title>Run away framework.log file (eating up the space on the c drive)</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/06/29/853.aspx" /><id>http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/06/29/853.aspx</id><published>2006-06-29T14:22:00Z</published><updated>2006-06-29T14:22:00Z</updated><content type="html">&lt;P&gt;Today I noticed that the space on the c drive on one of my sql 2005 servers was going down. After investigation I found that the &lt;FONT face=Arial size=2&gt;c:\windows\system32\wbem\log\Framework.log file was growing above the 64k limit.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Afterway after a quick search I found the fix &lt;A href="http://support.microsoft.com/?kbid=836605"&gt;http://support.microsoft.com/?kbid=836605&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Steven&lt;/P&gt;&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=853" width="1" height="1"&gt;</content><author><name>StevenWhite</name><uri>http://sqlblogcasts.com/members/StevenWhite.aspx</uri></author></entry><entry><title>TheRegister interview with Jim Gray</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/05/30/766.aspx" /><id>http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/05/30/766.aspx</id><published>2006-05-30T13:48:00Z</published><updated>2006-05-30T13:48:00Z</updated><content type="html">&lt;P&gt;The register have just posted an interview with Jim Gray&lt;/P&gt;
&lt;P&gt;&lt;U&gt;&lt;FONT color=#800080&gt;&lt;A href="http://www.regdeveloper.co.uk/2006/05/30/jim_gray/"&gt;http://www.regdeveloper.co.uk/2006/05/30/jim_gray/&lt;/A&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;U&gt;&lt;FONT color=#800080&gt;&lt;/P&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=766" width="1" height="1"&gt;</content><author><name>StevenWhite</name><uri>http://sqlblogcasts.com/members/StevenWhite.aspx</uri></author></entry><entry><title>SQL Server 2005 SP1</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/04/20/414.aspx" /><id>http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/04/20/414.aspx</id><published>2006-04-20T10:18:00Z</published><updated>2006-04-20T10:18:00Z</updated><content type="html">&lt;p&gt;Well I've installed this on my desktop (Core DB, tools and reporting services), and all seems well.&lt;/p&gt;
&lt;p&gt;I see that MS have improved the delivery of the service pack, no more expanding the files into a directory.&lt;/p&gt;
&lt;p&gt;Just waiting&amp;nbsp;&amp;nbsp;for the updated BOL and MOM packs :)&lt;/p&gt;&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=414" width="1" height="1"&gt;</content><author><name>StevenWhite</name><uri>http://sqlblogcasts.com/members/StevenWhite.aspx</uri></author></entry><entry><title>SQL Server 2005 Report Pack for Microsoft SharePoint Portal Server 2003 - Error</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/03/28/413.aspx" /><id>http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/03/28/413.aspx</id><published>2006-03-28T07:15:00Z</published><updated>2006-03-28T07:15:00Z</updated><content type="html">&lt;font size=2&gt;
&lt;p&gt;For those of you thinking of&amp;nbsp;using the new '&lt;strong&gt;SQL Server 2005 Report Pack for Microsoft SharePoint Portal Server 2003&lt;/strong&gt; ' to report on your own sharepoint sites,&amp;nbsp;there in a minor script error in the dbSPSReporting.sql script which is used to create a empty database.&lt;/p&gt;&lt;font size=2&gt;
&lt;p&gt;Basically there is a comma missing after WSSDoc field in&amp;nbsp;the&amp;nbsp;stored procedure usp_Insert_FactWSS &lt;br /&gt;which causes the stored procedure not to be created.&lt;/p&gt;&lt;/font&gt;
&lt;p&gt;The fix is to add a comma at the end of the line.&lt;br /&gt;ie.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;WSSDoc &lt;font color=#0000ff size=2&gt;nvarchar&lt;/font&gt;&lt;font color=#808080 size=2&gt;(&lt;/font&gt;&lt;font size=2&gt;255&lt;/font&gt;&lt;font color=#808080 size=2&gt;),&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font color=#808080 size=2&gt;&lt;/font&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;font color=#808080 size=2&gt;&amp;nbsp;&lt;/font&gt;&lt;/p&gt;&lt;/font&gt;&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=413" width="1" height="1"&gt;</content><author><name>StevenWhite</name><uri>http://sqlblogcasts.com/members/StevenWhite.aspx</uri></author></entry><entry><title>Memory manangement on 64bit version of SQL Server 2005</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/02/21/408.aspx" /><id>http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/02/21/408.aspx</id><published>2006-02-21T09:46:00Z</published><updated>2006-02-21T09:46:00Z</updated><content type="html">&lt;p&gt;I noticed that in the x64 version of Management Studio we have the 'Enable AWE' memory. Why?&lt;/p&gt;
&lt;p&gt;In Books online it states that '64-bit applications do not require AWE because access to memory is not limited to 4&amp;nbsp;GB'&lt;/p&gt;
&lt;p&gt;If that is the case why have the option available on the 64bit version of the product?&lt;br /&gt;What does it do?&lt;/p&gt;&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=408" width="1" height="1"&gt;</content><author><name>StevenWhite</name><uri>http://sqlblogcasts.com/members/StevenWhite.aspx</uri></author></entry><entry><title>Interesting SQL security article</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/02/14/407.aspx" /><id>http://sqlblogcasts.com/blogs/stevenwhite/archive/2006/02/14/407.aspx</id><published>2006-02-14T08:54:00Z</published><updated>2006-02-14T08:54:00Z</updated><content type="html">&lt;p&gt;On one of my regular visits to &lt;a href="http://www.sqlsecurity.com"&gt;http://www.sqlsecurity.com&lt;/a&gt; I noticed a link plugging an interesting article called ‘Article on 10 tricks attackers use to access SQL Server’. Anyway the&amp;nbsp;article can be&amp;nbsp;found&amp;nbsp;&lt;a href="http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1165052_tax301336,00.html?track=NL-464&amp;amp;ad=541873&amp;amp;adg=301324&amp;amp;bucket=ETA’" ref="’http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1165052_tax301336,00.html?track=NL-464&amp;amp;ad=541873&amp;amp;adg=301324&amp;amp;bucket=ETA’"&gt;here&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;Steven&lt;/p&gt;&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=407" width="1" height="1"&gt;</content><author><name>StevenWhite</name><uri>http://sqlblogcasts.com/members/StevenWhite.aspx</uri></author></entry></feed>