1. Click Start, click Run, type regedit, and then click OK.
2. Locate the following registry subkey:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type ServicesPipeTimeout, and then press ENTER.
5. Right-click ServicesPipeTimeout, and then click Modify.
6. In the Value data box, type the desired time-out value in milliseconds (ms), and then click OK. For example, if the new service time-out should be 60 seconds, type 60000 in the Value data box.
7. On the File menu, click Exit.
8. Restart the computer.

Note: You must restart the computer for the Service Control Manager to apply this change.

1. Inclusion
2. Substitutions

===Example===
—text.inc
Hello Collapsed World
—page.rst
Some text before
.. include:: text.inc
Some text after
—result
Some text before
Hello Collapsed World
Some text after

===Example===
—text.inc
.. |expand| replace:: Please Expand Me

.. include:: text.inc
Some text before
|expand|
Some text after
—result
Some text before
Please Expand Me
Some text after

I suppose you can use this tool with the baby carriage as well.

…

По данным французских СМИ, на улице находится около 13% ядерных отходов, отправленных на переработку в небольшой закрытый сибирский город, передает Reuters.

…

"Хранить на территории своей страны радиоактивные вещества с периодом полураспада в 24 тысячи лет слишком дорого, поэтому опасные для жизни грузы везут в Россию", – поясняют эксперты.

http://www.josephnewman.com/

http://video.google.com/videoplay?docid=8837004260826102354#docid=-3747078809628665374

http://www.antigravitytechnology.net/current_anti_gravity4.html

http://nevertalkwhenyoucannod.typepad.com/nevertalk/2009/02/the-truth-behind-rbsis-it-really-all-or-nothing.html

Source: http://technet.microsoft.com/en-us/magazine/2009.06.insidesharepoint.aspx

By default, SharePoint stores BLOB data in the Content column of the AllDocStreams table in the content database. The obvious advantage of this approach is straightforward transactional consistency between relational data and the associated non-relational file contents. For example, it’s not complicated to insert the metadata of a Word document along with the unstructured content into a content database, nor is it complicated to associate metadata with the corresponding unstructured content in select, update, or delete operations. However, the most obvious disadvantage of the default approach is an inefficient use of storage resources. Despite an I/O subsystem optimized for high performance, the SQL Server storage engine is not exactly a file-server replacement.

A SQL Server database consists of transaction log and data files, as illustrated in Figure 1. In order to ensure reliable transactional behavior, SQL Server first writes all transaction records to the log file before it flushes the corresponding data in 8KB pages to the data file on disk. Depending on the selected recovery model, this requires more than twice the BLOB size in storage capacity until you perform a backup and purge the transaction log. Moreover, SQL Server does not store unstructured SharePoint content directly in data pages. Instead, SQL Server uses a separate collection of text/image pages and only stores a 16-byte text pointer to the BLOB’s root node in the data row. Text/image pages are organized in a balanced tree, yet there is only one collection of text/image pages for each table. For the AllDocStreams table, this means that the content of all files is spread across the same text/image page collection. A single text/image page can hold data fragments from multiple BLOBs, or it may hold intermediate nodes for BLOBs larger than 32KB in size.

By default, SharePoint stores BLOB data in the Content column of the AllDocStreams table in the content database. The obvious advantage of this approach is straightforward transactional consistency between relational data and the associated non-relational file contents. For example, it’s not complicated to insert the metadata of a Word document along with the unstructured content into a content database, nor is it complicated to associate metadata with the corresponding unstructured content in select, update, or delete operations. However, the most obvious disadvantage of the default approach is an inefficient use of storage resources. Despite an I/O subsystem optimized for high performance, the SQL Server storage engine is not exactly a file-server replacement.

A SQL Server database consists of transaction log and data files, as illustrated in Figure 1. In order to ensure reliable transactional behavior, SQL Server first writes all transaction records to the log file before it flushes the corresponding data in 8KB pages to the data file on disk. Depending on the selected recovery model, this requires more than twice the BLOB size in storage capacity until you perform a backup and purge the transaction log. Moreover, SQL Server does not store unstructured SharePoint content directly in data pages. Instead, SQL Server uses a separate collection of text/image pages and only stores a 16-byte text pointer to the BLOB’s root node in the data row. Text/image pages are organized in a balanced tree, yet there is only one collection of text/image pages for each table. For the AllDocStreams table, this means that the content of all files is spread across the same text/image page collection. A single text/image page can hold data fragments from multiple BLOBs, or it may hold intermediate nodes for BLOBs larger than 32KB in size.

Figure 1 Default SharePoint BLOB storage in SQL Server

Let’s not dive too deeply into SQL Server internals, though. The point is that when reading unstructured content, SQL Server must go through the data row to get the text pointer and then through the BLOB’s root node and possibly additional intermediate nodes to locate all data fragments spread across any number of text/image pages that SQL Server must load into memory in full to get all data blocks. This is because SQL Server performs I/O operations at the page level. These complexities impair file-streaming performance in comparison to direct access through the file system.