Konstantin Vlasenko

http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F81802D92C/%5BMS-CSSP%5D.pdf

Let’s imagine that you need to show the same text on the several pages.
This one is not a footer or something like this. Just text you want to be on the several pages.
There are two options available in the reStructuredText:

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

http://github.com/

Have used it just once for a while to suggest SLIM_HOST patch to Fitnesse team. It was useful. But you can find an interesting point of view on stackoverflow

Read this http://www.dahon.com/news/releases/2009/august/dahon-brings-green-power-every-bike-0

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

http://top.rbc.ru/society/12/10/2009/336472.shtml

…

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

…

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

IMAGINE a civilization with an access to virtually unlimited energy

http://www.josephnewman.com/

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

The Lifter works without moving parts, flies silently, uses only electrical energy and is able to lift its own weight plus an additional payload. The Lifter uses the Biefeld-Brown effect discovered by Thomas Townsend Brown in 1928.

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

http://www.law.com/jsp/legaltechnology/pubArticleLT.jsp?id=1202432559096

RBS is implemented in SQL Server and is application agnostic. That’s to say, if you turn RBS on then all BLOB objects from any SQL Server-based application will be externalized. If that’s what you want to happen then that’s great but if you need to be able to apply business logic to what is externalized and whence it goes then you are severely restricted.

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

It looks like not only count of SharePoint objects (count of rows in the SharePoint SQL tables) affects SharePoint performance. The amount of binary contents also influences SharePoint performance based on article below.

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.