<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlserver.ro/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Intrebari generale</title><link>http://sqlserver.ro/forums/16/ShowForum.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>Re: SIMPLE vs FULL recovery model - performance of write operations</title><link>http://sqlserver.ro/forums/thread/7608.aspx</link><pubDate>Tue, 15 Sep 2009 08:11:58 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:7608</guid><dc:creator>sageata2002</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/7608.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=16&amp;PostID=7608</wfw:commentRss><description>&lt;P&gt;Trebuie sa subliniez excelentul link furnizat de diana, mai ales ca unele afirmatii de aici par a fi usor inexacte, sau mai degraba trunchiate (datele din transaction log pot fi suprascrise, dar asta se inampla in anumite conditii).&lt;/P&gt;
&lt;P&gt;De asemenea, pot sa va recomand &lt;A href="http://sqlskills.com/articles.asp"&gt;http://sqlskills.com/articles.asp&lt;/A&gt;&amp;nbsp;, unde veti gasi linkurile catre niste articole excelente scrise de Paul Randall, precum si SQL Server 2008 Internals (sau pentru 2005: Inside SQL Server 2005: The Storage Engine) de la Microsoft Press.&lt;/P&gt;
&lt;P&gt;toate cele bune,&lt;BR&gt;calin&lt;/P&gt;</description></item><item><title>Re: SIMPLE vs FULL recovery model - performance of write operations</title><link>http://sqlserver.ro/forums/thread/7590.aspx</link><pubDate>Thu, 10 Sep 2009 06:35:21 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:7590</guid><dc:creator>Diana</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/7590.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=16&amp;PostID=7590</wfw:commentRss><description>Vezi si&lt;br /&gt;http://www.sqlskills.com/BLOGS/KIMBERLY/post/8-Steps-to-better-Transaction-Log-throughput.aspx</description></item><item><title>Re: SIMPLE vs FULL recovery model - performance of write operations</title><link>http://sqlserver.ro/forums/thread/7588.aspx</link><pubDate>Wed, 09 Sep 2009 11:54:00 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:7588</guid><dc:creator>katalyn</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/7588.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=16&amp;PostID=7588</wfw:commentRss><description>Insa poti castiga daca log-ul este pe un alt HDD.&lt;br&gt;</description></item><item><title>Re: SIMPLE vs FULL recovery model - performance of write operations</title><link>http://sqlserver.ro/forums/thread/7586.aspx</link><pubDate>Wed, 09 Sep 2009 09:22:32 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:7586</guid><dc:creator>cardasim</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/7586.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=16&amp;PostID=7586</wfw:commentRss><description>&lt;BLOCKQUOTE&gt;&lt;div&gt;&lt;img src="http://sqlserver.ro/Themes/default/images/icon-quote.gif"&gt; &lt;strong&gt;rsocol:&lt;/strong&gt;&lt;/div&gt;&lt;div&gt;mă aştept ca performanţa să fie cam aceeaşi, deoarece datele se scriu &amp;#238;n transaction log (şi pentru recovery model-ul FULL şi pentru SIMPLE) la toate operaţiile normale (poate cu excepţia celor bulk-logged). Diferenţa este că la recovery model-ul SIMPLE, datele din transaction log pot fi suprascrise imediat ce tranzaţia a fost comisă (şi astfel nu mai creşte &amp;#238;n continuu fişierul).&lt;/div&gt;&lt;/BLOCKQUOTE&gt;&lt;br /&gt;Good point! Multumesc, Razvan.</description></item><item><title>Re: SIMPLE vs FULL recovery model - performance of write operations</title><link>http://sqlserver.ro/forums/thread/7584.aspx</link><pubDate>Wed, 09 Sep 2009 08:57:18 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:7584</guid><dc:creator>rsocol</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/7584.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=16&amp;PostID=7584</wfw:commentRss><description>Nu am făcut teste, dar mă aştept ca performanţa să fie cam aceeaşi, deoarece datele se scriu &amp;#238;n transaction log (şi pentru recovery model-ul FULL şi pentru SIMPLE) la toate operaţiile normale (poate cu excepţia celor bulk-logged). Diferenţa este că la recovery model-ul SIMPLE, datele din transaction log pot fi suprascrise imediat ce tranzaţia a fost comisă (şi astfel nu mai creşte &amp;#238;n continuu fişierul). Eventualul avantaj că se scrie &amp;#238;n acelaşi loc &amp;#238;n fişier nu este relevant pentru că la fiecare commit trebuie să se facă flush pt write cache-ul log-ului (pentru a se asigura durabilitatea transacţiilor), indiferent de recovery model.&lt;br /&gt;&lt;br /&gt;Răzvan</description></item><item><title>SIMPLE vs FULL recovery model - performance of write operations</title><link>http://sqlserver.ro/forums/thread/7581.aspx</link><pubDate>Wed, 09 Sep 2009 08:06:40 GMT</pubDate><guid isPermaLink="false">963f3a18-65dd-4aad-905c-b785cfe1d7c7:7581</guid><dc:creator>cardasim</dc:creator><slash:comments>0</slash:comments><comments>http://sqlserver.ro/forums/thread/7581.aspx</comments><wfw:commentRss>http://sqlserver.ro/forums/commentrss.aspx?SectionID=16&amp;PostID=7581</wfw:commentRss><description>A facut cineva teste care sa compare performanta la scriere intr-o baza de data cu recovery model FULL versus SIMPLE?&lt;br /&gt;Nu ma intereseaza "back in time restore"  sau alte avantaje ale modelului FULL, ci strict performanta la scriere (la citire ma astept sa nu fie diferente) si durata cat mai scurta a transactiilor.</description></item></channel></rss>