TABLE 1: Parameters for the sp_addlinkedserver Stored Procedure
Option	Required?	Description
@server	Yes	The name you want to call your linked server; this doesn't have to be the actual server name. For example, my server name is BKNIGHT, but I'm using the linked server name LINKEDSERVER. Always use all uppercase letters for your linked server names to prevent possible heterogeneous data problems later. Enterprise Manager automatically enforces this rule for you.
@srvproduct	No	This parameter—the logical name for the provider name you select—is simply meta data for your use. For example, if you selected the OLE DB Provider for SQL Server, you would use SQLServer 7.0.
@provider	Yes	The type of OLE DB or ODBC provider that you will use to connect to your linked server. Your choice of providers can range from DB2 to Access (Jet). Custom providers will use the OLE DB Provider for ODBC driver.
@datasrc	No	The name of the data source that the provider translates. This parameter's definition is different depending on which provider you select. For example, for SQL Server and Oracle databases, you would enter the database server name you want to connect to. For Access, you would enter the fully qualified path to the .mdb file document. For ODBC providers, this option would be the Data Source Name (DSN).
@location	No	The location of the data source that the provider translates. This parameter is not required to connect to SQL Server or Oracle servers. Location is passed to the OLE DB provider as the DBPROP_INIT_LOCATION property to initialize the provider.
@provstr	No	Any optional connection string that the OLE DB provider requires. This string isn't required for SQL Server connections. Some ODBC connections, however, do require this option.
@catalog	No	The default database (catalog) that the linked server will connect to.