seestart parameter parameter . .
Starts a region on the SQL Server instance running either on the local machine or on a specified remote machine.
The event monitor processseemonitor.exe performs region startup processing. By default, the event monitor performing region startup is on the machine invoking the seestart command. However, you can use the -server parameter to specify a remote machine to perform the startup process.
Do not use any properties for region startup processing.
If neither -noproperties nor -properties: is specified, each variable/value in the current environment space is passed as a property to the region startup processing.
You can define properties used by region startup processing to replace pseudo-variables that specified in a region startup file's <location> sections. Pseudo-variables are replaced by the value associated with a property of the same name. If the property does not exist, the value of an environment variable of the same name is used.
If neither -noproperties nor -properties: is specified, each variable/value in the current environment space is passed as a property to the region startup processing.
Name of the region to be started. If -regionfile is omitted, the command uses the first region startup file with the name Region_<region-name>.config that it finds in the following locations:
If (local) is specified, the region startup file is on the local machine. If (server) is specified, the region startup file is on the machine specified by the -server parameter.
If (server) is specified, but the -server parameter is not, (local) is assumed.
The default is (local).
If the -region parameter is not specified, the value of the region startup file's region element's name property is used as the name of the region to be started.
If no region startup path file is specified, the command searches for region startup and resource definition files in the following locations in turn, and uses the first one that it finds:
-regionfile:c:\mydir\region_myregion.config
-regionfile:c:\mydir\region_myregion.config -server:myserver
-regionfile:(local)c:\mydir\region_myregion.config
-regionfile:(local)c:\mydir\region_myregion.config -server:myserver
-regionfile:(server)c:\mydir\region_myregion.config -server:myserver
Default database server on the local machine: | -usedb |
Default database server on the local machine, identical to -usedb: | -usedb:(local) |
Specific database server on the local machine: | -usedb:(local)\SQLEXPRESS |
Default database server instance on a specific machine (SC1 used in example) | -usedb:SC1 |
Specific database server instance on a specific machine (SC1, SQLEXPRESS used in example for machine name, database server name) | -usedb:SC1\SQLEXPRESS |
Warm-start the region. The region initializes using information provided by the region startup file. The resource definition file is not used as the resources created by the previous cold-start (and optionally installed by CINS) are used.
A region can only be warm-started if it has previously been stopped normally. If the region is stopped using the force or immediate option, the region must be cold-started and an error is reported if you attempt a warm-start.
seestartUses the Region_ESDEMO.config file to start the ESDEMO region.
seestart -region:TESTDBUses the Region_TESTDB.config file to start the TESTDB region.
seestart -region:DEMO -regionfile:Region_Common.configUses the Region_Common.config file to start the DEMO region.
seestart -sit:TESTSITUses the Region_ESDEMO.config file to start the ESDEMO region, using TESTSIT instead of the SIT defined in Region_ESDEMO.config.
seestart -usedb:(local)\SQLEXPRESSUses the Region_ESDEMO.config to start the ESDEMO region using the (local)\SQLEXPRESS database instance instead of the database instance defined in Region_ESDEMO.config.