Database Reference
In-Depth Information
9.
Now, we have to mark each reporting volume as read-only and dismount from the
server. Go to the command prompt window and enter the following commands:
DiskPart
DISKPART> select volume=<drive-number>
DISKPART> attribute set readonly
DISKPART> remove
DISKPART> exit
10. To ensure that the reporting volume is read-only, you should attempt to create a file
on the volume. This attempt must return an error.
11. Next, go to the command prompt window and enter the following commands:
DiskPart
DISKPART> select volume=<drive-number>
DISKPART> assign letter = <drive letter>
DISKPART> exit
The <drive-letter> is
the letter assigned to the
reporting volume.
12. Attach the database to one or more server instances on each of the reporting servers
using the sp_attach_db statement or SSMS tool.
13. Now, the reporting database is made available as a scalable shared database to
process the queries from the application.
These steps complete the process of building and refreshing the scalable shared database
feature by mounting the reporting database volumes.
How it works...
Using the available hardware vendor-specific servers and disk volumes, the scalable shared
database features allow the application to scale out a read-only database built exclusively for
reporting purposes.
The 'build' phase is the process of mounting the reporting volume on the production server
and building the reporting database. After the reporting database is built on the volume, using
the defined data-copy methods, the data is updated. Once it is completed, the process of
setting each reporting volume to read-only and dismount begins.
 
Search WWH ::




Custom Search