Escolar Documentos
Profissional Documentos
Cultura Documentos
***************************************************************
contents
***************************************************************
1.0 introduction
2.0 installing sql server 2000
2.1 system requirements
2.2 do not install analysis services to a dbcs folder
2.3 installing analysis services samples
2.4 updating statistics after upgrading from sql server 7.0
2.5 minimum sql server installation components
2.6 requirements for active directory integration
2.7 silverston samples are not installed
2.8 installation help on windows 95
2.9 installing sql server 2000 with sql server version 6.5
3.0 documentation notes
3.1 sql server core components notes
3.1.1 replication and host integration server
3.1.2 backup/restore apis for independent software vendors
3.1.3 executing dts custom tasks created in visual basic
3.1.4 desktop engine setup parameters
3.1.5 adding properties to dts custom tasks
3.1.6 @@trancount and commit in triggers
3.1.7 behavior of wildcard and escape characters
3.1.8 changing the sql server agent service account
3.1.9 adding pure unicode error messages
3.1.10 dts using activex scripting after uninstalling
sql server 7.0
3.1.11 removing secondary databases for log shipping
3.1.12 odbc api: sqlgetconnectattr
3.1.13 connecting early version clients to named instances
3.1.14 sql server sometimes cannot open static ip port
addresses
3.1.15 sqlsetconnectattr and the connection attribute
sql_copt_ss_preserve_cursors
3.1.16 sqlendtran
3.1.17 permissions for active directory integration
3.1.18 srv_pfield (extended stored procedures programming)
3.1.19 using the msx wizard with windows authentication
3.1.20 updating a table on a linked server
3.1.21 effects of locking hints on read_only cursors
3.1.22 adding dependencies to the sql server resource
3.1.23 upgrading from msde 1.0 to sql server 2000
desktop engine
3.1.24 microsoft search service
3.1.25 references to windows 95
3.1.26 full-text catalogs inaccessible after changing
sql server account
3.1.27 recommendations for designing distributed
partitioned views
3.1.28 requirements for the desktop engine setup file
3.1.29 desktop engine setup targetdir and datadir
3.1.30 reinstalling sql server 2000 desktop engine
3.2 sql server books online functionality notes
3.2.1 link to mdac and xml documentation does not work
3.2.2 printing limitations
3.2.3. incorrect hyperlinks to the ado connection object
from ado dynamic properties topics
3.3 english query
3.3.1 saveprojecttoxmldom method
3.3.2 automatic clarification of questions feature
3.4 analysis services
3.4.1 before registering analysis services performance
monitoring counters on windows nt 4.0
3.4.2 distinct count aggregate function
3.4.3 update cube statement
3.4.4 process databases after upgrading from beta 2
***************************************************************
1.0 introduction
***************************************************************
this file contains important information you should read
before installing microsoft sql server 2000.
***************************************************************
2.0 installing sql server 2000
***************************************************************
microsoft sql server 2000 documentation is available from these
sources:
use the autorun setup program on the sql server 2000 compact
disc to install the sql server 2000 components. the autorun
setup program is executed automatically when you insert the
compact disc in the drive. you can also execute it by selecting
the autorun.exe program in the root folder of the sql server
2000 compact disc. although there is a setup.exe program in the
sqlmsde folder of the sql server 2000 compact disc, this program
is intended to be used by applications that must install the
sql server 2000 desktop engine during their installation
process. the desktop engine setup is not intended for installing
the sql server 2000 components from the compact disc. for more
information about distributing sql server applications, see
sql server books online.
for users of sql server version 7.0 who are installing sql
server 2000 for the first time, these new features are chosen
during setup:
service pack 5a, which is the most current service pack for
sql server version 6.5, is available at
http://support.microsoft.com/support/sql.
-----------------------
2.1 system requirements
-----------------------
microsoft sql server 2000 operates on computers running intel
or compatible pentium, pentium pro, or pentium ii processors.
the processor must be running at a minimum of 166 mhz.
* windows 2000
* microsoft windows nt version 4.0 service pack 5 or later
* windows millennium edition
* windows 98
* windows 95 (client connectivity option only)
-----------------------------------------------------
2.2 do not install analysis services to a dbcs folder
-----------------------------------------------------
analysis services should not be installed to a folder that uses
characters from a double-byte character set (dbcs) in the path
or name. install analysis services to a folder that uses only
single-byte characters in the path and name.
----------------------------------------
2.3 installing analysis services samples
----------------------------------------
to install the analysis services samples, you must install
analysis services from the sql server compact disc. the samples
are installed at
x:\program files\microsoft analysis services\samples.
-----------------------------------------------------------
2.4 updating statistics after upgrading from sql server 7.0
-----------------------------------------------------------
after upgrading from sql server 7.0, run sp_updatestats
'resample' to update the statistics on the user tables in your
databases.
----------------------------------------------
2.5 minimum sql server installation components
----------------------------------------------
full-text search is not included in a minimum installation of
sql server 2000.
-------------------------------------------------
2.6 requirements for active directory integration
-------------------------------------------------
to register an instance of microsoft sql server 2000 in
active directory, the instance of sql server must be installed
on a computer running microsoft windows 2000 with the
active directory service enabled. the sql server service must
also be configured to run under either the windows localsystem
account or a windows domain account in the local administrators
group. this requirement must be met to add databases and
publications from the instance to active directory. instances
of sql server 2000 configured to run under a power user account
do not have sufficient permissions to invoke all of the
sql server components required to work with active directory.
----------------------------------------
2.7 silverston samples are not installed
----------------------------------------
microsoft sql server 2000 enterprise edition includes a license
for four popular database schema samples. instructions for
installing these samples using the setup program are provided
in the topic "database schema samples"; however, setup does
not install these samples. to install the database schema
samples, double-click unzip_silverstondb.exe located at
\devtools\samples\silverstondb on the sql server 2000
compact disc.
-----------------------------------
2.8 installation help on windows 95
-----------------------------------
if you want to use help during the installation of client
connectivity on microsoft windows 95, you may need to upgrade
to microsoft internet explorer 5.0 and html help 1.3. you can
update internet explorer and html help by downloading the
latest versions from http://www.microsoft.com. the html help
update file is named hhupd.exe.
----------------------------------------------------------
2.9 installing sql server 2000 with sql server version 6.5
----------------------------------------------------------
sql server books online contains contradictory statements
about installing microsoft sql server 2000 on a computer
running sql server version 6.5. the resulting installation
depends on whether you are installing a named instance or
a default instance of sql server 2000:
you can run either the default instance of sql server 2000
or the instance of sql server 6.5, but not both at the same
time. to switch between the two versions of sql server, use
the microsoft sql server-verswitch entry on the start menu.
when you switch from sql server 2000 to sql server 6.5, the
instance of sql server 2000 becomes inactive, and the sql
server 6.5 program group replaces the sql server 2000 program
group on the start menu. when you switch from sql server 6.5
to sql server 2000, the process is reversed.
***************************************************************
3.0 documentation notes
***************************************************************
these are issues that arose after the sql server books online
documentation was completed.
-----------------------------------
3.1 sql server core component notes
-----------------------------------
these notes relate to the sql server core components, including
the database engine, client components, connectivity components,
graphical tools, and command prompt utilities.
sql server books online topics "merging the desktop engine into
windows installer" and "sql server 2000 desktop engine setup"
document two parameters that are ignored by the final version
of the desktop engine setup: usedefaultsapwd and sapassword.
a set of desktop engine merge modules that have been merged into
a windows installer setup has the same behavior. on the windows
nt 4.0 and windows 2000 operating systems, the instance of sql
server is configured to use windows authentication if
securitymode=sql is not specified, and is configured to use sql
server authentication if securitymode=sql is specified. the
instance is always configured to use sql server authentication
on the windows 98 operating system.
the manage sql server messages dialog box does not support
adding pure unicode messages to the sysmessages table. to add
such messages, use the sp_addmessage stored procedure. be
sure to use the n prefix on the 'msg' parameter (for example,
@msgtext = n'xxx').
the sql server books online topic "working with named and
multiple instances of sql server 2000" states that you must use
sql server 2000 client components to connect to named instances
of sql server 2000. however, the sql server version 7.0 client
network utility can be used to configure a server alias name
that the sql server version 7.0 client components can use to
connect to a named instance of sql server 2000. this is
documented in the sql server books online topics "sql server
2000 and sql server version 7.0" and "communicating with
multiple instances."
3.1.16 sqlendtran
* upgrade=1
specifies that desktop engine setup or windows installer
is upgrading an instance of msde 1.0 to sql server 2000
desktop engine. the only value supported is 1.
* upgradeuser='loginaccount'
specifies the sql server authentication login account that
desktop engine setup or windows installer will use when
connecting to the instance of msde 1.0 to upgrade the
master database. the login account must have a blank
password and must be a member of the sysadmin fixed server
role. specify this parameter if you want setup or windows
installer to connect using sql server authentication.
the recommended option is to not specify upgradeuser,
which causes desktop engine setup or windows installer to
use windows authentication to connect to the instance of
msde 1.0. when using windows authentication, you must
run desktop engine setup or windows installer under a
windows account that has been included in the sql server
sysadmin fixed server role. if you do specify upgradeuser,
protect your security by minimizing the amount of time the
sysadmin login can have a blank password, such as by
assigning the login a valid password immediately after
the upgrade is complete.
[options]
upgrade=1
upgradeuser=setuplogin
ensure that the instance of msde 1.0 has been stopped before
you try to upgrade it to sql server 2000 desktop engine.
the topic "sql server 2000 desktop engine setup" in sql server
books online provides an incomplete list of the files required to
successfully run setup. in addition to the files mentioned in the
topic, the following files must also be copied from the sql server
2000 compact disc to the folder containing setup.exe:
these files must also be copied for the desktop engine installation
sample to work.
the file paths specified for microsoft sql server desktop engine
setup targetdir and datadir parameters must be terminated with a
backslash. for example:
* reinstall=all
specifies that desktop engine setup or windows installer install
all sql server 2000 desktop engine features. the only value
supported is all.
* reinstallmode={ omus | a }
specifies the level of processing performed by desktop engine
setup or windows installer. specify reinstallmode=omus when
resuming a failed setup. with this option, the entire installation
process is verified and completed. specify reinstallmode=a when
you have to rebuild only the master database, such as after a
failure of the disk drive holding the master database.
-----------------------------------------------
3.2 sql server books online functionality notes
-----------------------------------------------
these are issues that relate to the functionality of sql server
books online.
when sql server books online is opened using f1 or the help menu
in an mmc snap-in (such as sql server enterprise manager), the
link to the mdac and xml documentation does not work. to view
the mdac and xml documentation, open mdacxml.chm located in
c:\program files\microsoft sql server\80\tools\books.
note: the link works correctly when sql server books online
is started directly from the sql server program group on the
start menu, or from running sql80.col.
-----------------
3.3 english query
-----------------
these are issues in english query that are not reflected in the
documentation.
* lookupqueries
returns an array of querycmd objects of the size specified in
itemcount, or is null. each lookupquery corresponds to an item
in the items array. if the query returns no rows, the
corresponding item may not be the correct default choice for
the inputlist object.
for example, for the question "how many awards did john
fortune win?", an english query application might not have
"john fortune" in its dictionary; therefore, a
userclarification response is returned containing an inputlist
with the text, "which of these do you mean by john fortune?"
the choices are: the name of an actor, which selects actors
named john fortune, or the name of a movie, which selects
movies named john fortune. a lookupquery is associated
with each choice. if only one of these queries returns rows,
the client application can use the corresponding item as the
user selection for the inputlist, and can respond to the
userclarificationresponse without user intervention.
* entityids property
returns an array of entityids of the size specified in itemcount.
each entityid corresponds to an item in the items array. if the
choice in the items array is an entity (for example, the name of
an actor), the entityid contains the id of that entity
(for example, author_name). if the choice in the items array is
not an entity (for example, first name), the entityid is empty.
for example, for the question "list the old people", the english
query application might not have a threshold specified for "old".
a userclarificationresponse is returned containing an inputtext
with the text, "an old person is a person whose age is over ___."
the lookupquery selects the median age. the client application
can choose to use the returned value as the response to the
inputtext and can respond to the userclarificationresponse
without user intervention.
---------------------
3.4 analysis services
---------------------
these are issues in analysis services that are not reflected in
the documentation.