BULK INSERT Data into a SQL Server Table from a CSV file

You want to import your sales orders from a comma delimited file into a SQL Server or MSDE table called orders. The file looks like this:

345,John Doe, 400
346,Mark Smith,450
347,Robert,400

 

Run the following SQL command from the SQL window in Teratrax Database Manager. Replace lower case text with your own:

BULK INSERT [orders]
FROM ‘c:orders.csv
WITH (FIELDTERMINATOR = ‘,’)

 

Result (order table):

OrderID Name Price
345 John Doe 400
346 Mark Smith 450
347 Robert 400

 

 

 

 

Make sure the field terminator (‘,’ in this example) is not part of any actual value. The field Name for instance cannot be ‘Doe, John’ since the ‘,’ would be considered as a field terminator.

The table has to be similar in format to the file (same number of fields and same data type.)

Download MSDE 2000

Unlike SQL Server, MSDE did not ship with its own Enterprise Manager tool. Developers and users of MSDE applications lack the tools necessary for database design, management, and administration.

Downloading MSDE

Download MSDE 2000 from Microsoft

 

Database size

MSDE databases are limited to 2 gigabytes (GB) of data. This limit is per database, and not per server, so a single MSDE server can support multiple MSDE databases, each containing up to the 2 GB limit. If you anticipate that your database is currently or will grow beyond 2 GB, consider upgrading to Microsoft SQL Server™ 2000 Standard Edition for a more scalable database platform on which to build.

Multiple users

MSDE is tuned for desktop and shared solutions where there are fewer than five concurrent workloads hitting the database at any one time (only five concurrent batch workloads or 25 concurrent connections for websites.)  If your solution needs to support more than this number of concurrent batches, you may need to migrate to SQL Server or SQL Server Enterprise editions for optimal performance at this higher level of scalability.

MSDE Replication

MSDE can participate in most types of replication with either a centralized SQL Server or another MSDE. Specifically, MSDE can participate fully in snapshot and merge replication, but only as a subscriber in transactional replication (MSDE cannot be a publisher in transactional replication.) Also note that a per-set Client-Access License (CAL), or processor license is required if MSDE is participating in any type of interaction with a SQL Server, including replication. A CAL or processor license is not required if MSDE is replicating with another MSDE.

MSDE Benefits

MSDE 2000 is a redistributable version of SQL Server 2000. It is a database engine provided by Microsoft that is based on the core SQL Server technology and supports single- and dual-processor desktop computers. In other words, MSDE 2000 is a scaled down copy of SQL Server. MSDE 2000 was introduced to provide application developers a database engine that is more powerful than the Jet engine and at the same time expandable to SQL Server. It is ideal for client applications requiring an embedded database and websites serving up to 25 concurrent users.

The common technology base shared between SQL Server and MSDE 2000 enables developers to build applications that can scale seamlessly from desktop solutions to multiprocessor enterprise clusters.

As an alternative to the Jet engine, MSDE 2000 provides a cost-effective option for developers who need a database server that can be easily distributed and installed. Because it is fully compatible with SQL Server, developers can easily target both SQL Server and MSDE database objects with the same application code base. This provides a seamless upgrade path for MSDE database instances to SQL Server if an application grows beyond the storage and scalability that a MSDE can provide.

Multi-server, multi-transaction operations

Multiple-transaction processes across servers cannot include any machines running MSDE. These advanced operations cannot involve any MSDE databases. MSDE databases cannot request services from a SQL Server without a per seat SQL Server CAL (Client Access License) or processor license.

MSDE and under Windows 95, 98 and Me

MSDE cannot use integrated security features of Microsoft Windows NT® when operating on a Microsoft Windows® 95, Windows 98 or Windows Me platform. Also, MSDE cannot be started remotely, and some third-party network protocols are not supported.

Compare SQL Server 2005 Editions

With the release of SQL Server 2005, Microsoft has introduced the Express edition and the Workgroup edition to better meet the needs of each customer. The new line of SQL Server 2005 editions includes Express, Workgroup, Standard, and Enterprise Edition. The four new editions will offer a range of features including high availability, scalability, and business intelligence tools. The following table lists the various features in each edition:

Express Workgroup Standard Enterprise
Number of CPUs 1 2 4 No Limit
RAM 1 GB 3 GB No Limit No Limit
Database Size 4 GB No Limit No Limit No Limit
Merge Replication
Transactional Replication
Report Server
Management Studio
Report Builder
Backup Log-shipping
Full Text Search
SQL Agent Job Scheduling
Database Mirroring
Failover Clustering
Notification Services
Integration Services
Web Services (HTTP Endpoints)
Analysis Services
Data Mining
Database Tuning Advisor
Advanced Performance Tuning

 

Read more about SQL Server 2005 editions and features…

 

SQL Server Express: Management Studio, Downloads, & Limitations

SQL Server 2005 Express Edition is a scaled down version of Microsoft SQL Server 2005. Although the database server is limited in enterprise features, most of the limitations do not affect the database performance for what it is meant to do.

Performance limitations in SQL Server Express

The SQL engine of SQL Server Express supports 1 CPU, 1 GB RAM and a 4 GB database size. This distinction gives SQL Server Express well defined cut-off points to differentiate it from other SQL Server 2005 editions. Unlike MSDE, SQL Server Express eliminates the confusion created by the workload governor.

1 CPU: SQL Server Express can install and run on multiprocessor machines, but only a single CPU is used at any time. This limitation prevents the use of parallel query execution in SQL Server Express.

1 GB RAM: The 1 GB RAM limit is the memory limit available for the buffer pool. The buffer pool is used to store data pages and other information. However, memory needed to keep track of connections, locks, etc. is not counted toward the buffer pool limit. It is therefore possible that the server will use more than 1 GB in total, but it will never use more than 1GB for the buffer pool. This limitation prevents the use of Address Windowing Extensions (AWE) with SQL Server Express.

4 GB Database Size: The 4 GB database size limit applies only to data files and not to log files. However, there are no limits to the number of databases that can be attached to the server. There are some minor changes to the startup of SQL Server Express. User databases are not automatically started, and DTC is not automatically initialized. For the user experience, though, there should be no difference other than a faster startup. Applications planning to use SQL Server Express are recommended to keep these changes in mind when designing their applications.

SQL Server Management Studio Express (SSMSE)

SQL Server Express does not ship with any management tools. However, you can download basic management tools from Microsoft.

Limitation in enterprise features

The following SQL Server 2005 enterprise level features are not available in SQL Server 2005 Express Edition:

  • Analysis Services (both OLAP and Data Mining)
  • Integration Services (DTS successor)
  • Notification Services
  • Report Builder (although Reporting Services is included)
  • SQL Agent
  • Database Tuning Advisor
  • Full-text search
  • Log shipping

Enterprise availability limitations

Unlike other editions of SQL Server 2005, the Express edition does not support Fail-over Clustering or Database Mirroring.

Database Mirroring: Database Mirroring extends log shipping capabilities and enhances availability of SQL Server systems by providing automatic fail-over to a standby server.

Fail-over Clustering: Fail-over clustering is the ultimate fail-over mechanism SQL Server can provide. A SQL Server node in a cluster of nodes sharing one disk array can fail-over to another node without affecting the availability of the server cluster. The disk array where databases reside is central to the SQL Server cluster.

Networking support in SQL Server 2005 Express

Only the shared memory on the local machine is accessible by default for SQL Server Express, although the user can explicitly turn on other supported protocols such as TCP/IP and Named Pipes. VIA and HTTP protocols are not supported in SQL Server Express. With only shared memory available by default, connections from a remote machine to SQL Server Express will fail unless the networking is turned on. To turn networking on, Use SQL Server Configuration Manager to enable relevant protocols and start SQL Browser.

SQL Browser is a new service in SQL Server 2005 that is used to identify the ports that named instances listen on. Since shared memory does not use it, this service is turned off in SQL Server Express by default. This means that the user will have to start this service so that network access can work.

Note One interesting fact is that SQL Browser listens on UDP port 1434. However, pre-SP3 versions of SQL Server 2000 holding port UDP 1434 may result in failure of SQL Browser name resolution, since they may refuse to give up the port. The workaround is to upgrade all SQL Server 2000/MSDE instances on the machine to SP3 or higher.

SQL Server Express instances

Multiple SQL Server 2005 Express installations can coexist on the same machine along with other installations of SQL Server 2000, SQL Server 2005, or Microsoft Desktop Engine (MSDE). In general, it is best that SQL Server 2000 instances be upgraded to SP3a or higher. The maximum limit to the number of SQL instances is 50 on the same machine. These instances must be uniquely named for the purpose of identifying them.

SQL Server Express by default installs as a named instance called SQLEXPRESS. This particular instance is to be shared among multiple applications and application vendors. We recommend that you use this instance unless your application has special configuration needs. Some configuration needs, such as the requirement of the Secure Socket Layer (SSL) authentication, affect the installation as a whole and hence need a separate named instance. In all other cases, the shared instance should suffice. Another advantage of using the shared instance is that the application vendors need not worry about installing SQL Server Express along with the application, which simplifies application installation.

Software requirements

Microsoft Internet Explorer 6.0 SP1 or higher

Microsoft .NET Framework 2.0

Operating systems

Microsoft Windows 2000 SP4 Professional

Microsoft Windows 2000 SP4 Server

Microsoft Windows 2000 SP4 Advanced

Microsoft Windows 2000 SP4 Data Center

Microsoft Windows XP SP1 Professional or higher

Microsoft Windows 2003 Server or higher

Microsoft Windows 2003 Enterprise or higher

Microsoft Windows 2003 Data Center or higher

Microsoft Windows Small Business Server 2003 Standard or higher

Microsoft Windows Small Business Server 2003 Premium or higher

 

Sources include the Microsoft website

Microsoft SQL Server Cursors

SQL Server cursors are database objects used to manipulate data in a set on a row-by-row basis. You can fetch cursor rows and perform operations on them in a loop just like using any looping mechanism found in any other programming language. Before you can use a cursor, you need to declare it.

DECLARE CURSOR

The DECLARE CURSOR command defines the attributes of a Transact-SQL server cursor, such as its scrolling behavior and the query used to build the result set on which the cursor operates. DECLARE CURSOR accepts both a syntax based on the SQL-92 standard and a syntax using a set of Transact-SQL extensions.

SQL-92 Syntax

DECLARE cursor_name [ INSENSITIVE ] [ SCROLL ] CURSOR
FOR select_statement
[ FOR { READ ONLY | UPDATE [ OF column_name [ ,…n ] ] } ]

Transact-SQL extended syntax

DECLARE cursor_name CURSOR
[ LOCAL | GLOBAL ]
[ FORWARD_ONLY | SCROLL ]
[ STATIC | KEYSET | DYNAMIC | FAST_FORWARD ]
[ READ_ONLY | SCROLL_LOCKS | OPTIMISTIC ]
[ TYPE_WARNING ]
FOR select_statement
[ FOR UPDATE [ OF column_name [ ,…n ] ] ]

SQL-92 arguments

cursor_name is the name of the Transact-SQL server cursor defined. cursor_name must conform to the rules for identifiers.

INSENSITIVE defines a cursor that makes a temporary copy of the data to be used by the cursor. All requests to the cursor are answered from this temporary table in tempdb; therefore, modifications made to base tables are not reflected in the data returned by fetches made to this cursor, and this cursor does not allow modifications. When SQL-92 syntax is used, if INSENSITIVE is omitted, committed deletes and updates made to the underlying tables (by any user) are reflected in subsequent fetches.

SCROLL specifies that all fetch options (FIRST, LAST, PRIOR, NEXT, RELATIVE, ABSOLUTE) are available. If SCROLL is not specified in an SQL-92 DECLARE CURSOR, NEXT is the only fetch option supported. SCROLL cannot be specified if FAST_FORWARD is also specified.

select_statement is a standard SELECT statement that defines the result set of the cursor. The keywords COMPUTE, COMPUTE BY, FOR BROWSE, and INTO are not allowed within select_statement of a cursor declaration.

Microsoft® SQL Server™ implicitly converts the cursor to another type if clauses in select_statement conflict with the functionality of the requested cursor type.

READ ONLY prevents updates made through this cursor. The cursor cannot be referenced in a WHERE CURRENT OF clause in an UPDATE or DELETE statement. This option overrides the default capability of a cursor to be updated.

UPDATE [OF column_name [,…n]] defines updatable columns within the cursor. If OF column_name [,…n] is specified, only the columns listed allow modifications. If UPDATE is specified without a column list, all columns can be updated.

Transact-SQL extended arguments

cursor_name is the name of the Transact-SQL server cursor defined. cursor_name must conform to the rules for identifiers.

LOCAL specifies that the scope of the cursor is local to the batch, stored procedure, or trigger in which the cursor was created. The cursor name is only valid within this scope. The cursor can be referenced by local cursor variables in the batch, stored procedure, or trigger, or a stored procedure OUTPUT parameter. An OUTPUT parameter is used to pass the local cursor back to the calling batch, stored procedure, or trigger, which can assign the parameter to a cursor variable to reference the cursor after the stored procedure terminates. The cursor is implicitly deallocated when the batch, stored procedure, or trigger terminates, unless the cursor was passed back in an OUTPUT parameter. If it is passed back in an OUTPUT parameter, the cursor is deallocated when the last variable referencing it is deallocated or goes out of scope.

GLOBAL specifies that the scope of the cursor is global to the connection. The cursor name can be referenced in any stored procedure or batch executed by the connection. The cursor is only implicitly deallocated at disconnect.

Note If neither GLOBAL or LOCAL is specified, the default is controlled by the setting of the default to local cursor database option. In SQL Server version 7.0, this option defaults to FALSE to match earlier versions of SQL Server, in which all cursors were global. The default of this option may change in future versions of SQL Server.

FORWARD_ONLY specifies that the cursor can only be scrolled from the first to the last row. FETCH NEXT is the only supported fetch option. If FORWARD_ONLY is specified without the STATIC, KEYSET, or DYNAMIC keywords, the cursor operates as a DYNAMIC cursor. When neither FORWARD_ONLY nor SCROLL is specified, FORWARD_ONLY is the default, unless the keywords STATIC, KEYSET, or DYNAMIC are specified. STATIC, KEYSET, and DYNAMIC cursors default to SCROLL. Unlike database APIs such as ODBC and ADO, FORWARD_ONLY is supported with STATIC, KEYSET, and DYNAMIC Transact-SQL cursors. FAST_FORWARD and FORWARD_ONLY are mutually exclusive; if one is specified the other cannot be specified.

STATIC defines a cursor that makes a temporary copy of the data to be used by the cursor. All requests to the cursor are answered from this temporary table in tempdb; therefore, modifications made to base tables are not reflected in the data returned by fetches made to this cursor, and this cursor does not allow modifications.

KEYSET specifies that the membership and order of rows in the cursor are fixed when the cursor is opened. The set of keys that uniquely identify the rows is built into a table in tempdb known as the keyset. Changes to nonkey values in the base tables, either made by the cursor owner or committed by other users, are visible as the owner scrolls around the cursor. Inserts made by other users are not visible (inserts cannot be made through a Transact-SQL server cursor). If a row is deleted, an attempt to fetch the row returns an @@FETCH_STATUS of -2. Updates of key values from outside the cursor resemble a delete of the old row followed by an insert of the new row. The row with the new values is not visible, and attempts to fetch the row with the old values return an @@FETCH_STATUS of -2. The new values are visible if the update is done through the cursor by specifying the WHERE CURRENT OF clause.

DYNAMIC defines a cursor that reflects all data changes made to the rows in its result set as you scroll around the cursor. The data values, order, and membership of the rows can change on each fetch. The ABSOLUTE fetch option is not supported with dynamic cursors.

FAST_FORWARD specifies a FORWARD_ONLY, READ_ONLY cursor with performance optimizations enabled. FAST_FORWARD cannot be specified if SCROLL or FOR_UPDATE is also specified. FAST_FORWARD and FORWARD_ONLY are mutually exclusive; if one is specified the other cannot be specified.

READ_ONLY prevents updates made through this cursor. The cursor cannot be referenced in a WHERE CURRENT OF clause in an UPDATE or DELETE statement. This option overrides the default capability of a cursor to be updated.

SCROLL_LOCKS specifies that positioned updates or deletes made through the cursor are guaranteed to succeed. Microsoft® SQL Server™ locks the rows as they are read into the cursor to ensure their availability for later modifications. SCROLL_LOCKS cannot be specified if FAST_FORWARD is also specified.

OPTIMISTIC specifies that positioned updates or deletes made through the cursor do not succeed if the row has been updated since it was read into the cursor. SQL Server does not lock rows as they are read into the cursor. It instead uses comparisons of timestamp column values, or a checksum value if the table has no timestamp column, to determine whether the row was modified after it was read into the cursor. If the row was modified, the attempted positioned update or delete fails. OPTIMISTIC cannot be specified if FAST_FORWARD is also specified.

TYPE_WARNING specifies that a warning message is sent to the client if the cursor is implicitly converted from the requested type to another.

select_statement is a standard SELECT statement that defines the result set of the cursor. The keywords COMPUTE, COMPUTE BY, FOR BROWSE, and INTO are not allowed within select_statement of a cursor declaration.

SQL Server implicitly converts the cursor to another type if clauses in select_statement conflict with the functionality of the requested cursor type.

FOR UPDATE [OF column_name [,…n]] defines updatable columns within the cursor. If OF column_name [,…n] is supplied, only the columns listed allow modifications. If UPDATE is specified without a column list, all columns can be updated, unless the READ_ONLY concurrency option was specified.

Remarks

DECLARE CURSOR defines the attributes of a Transact-SQL server cursor, such as its scrolling behavior and the query used to build the result set on which the cursor operates. The OPEN statement populates the result set, and FETCH returns a row from the result set. The CLOSE statement releases the current result set associated with the cursor. The DEALLOCATE statement releases the resources used by the cursor.

The first form of the DECLARE CURSOR statement uses the SQL-92 syntax for declaring cursor behaviors. The second form of DECLARE CURSOR uses Transact-SQL extensions that allow you to define cursors using the same cursor types used in the database API cursor functions of ODBC, ADO, and DB-Library.

You cannot mix the two forms. If you specify the SCROLL or INSENSITIVE keywords before the CURSOR keyword, you cannot use any keywords between the CURSOR and FOR select_statement keywords. If you specify any keywords between the CURSOR and FOR select_statement keywords, you cannot specify SCROLL or INSENSITIVE before the CURSOR keyword.

If a DECLARE CURSOR using Transact-SQL syntax does not specify READ_ONLY, OPTIMISTIC, or SCROLL_LOCKS, the default is as follows:

If the SELECT statement does not support updates (insufficient permissions, accessing remote tables that do not support updates, and so on), the cursor is READ_ONLY.

STATIC and FAST_FORWARD cursors default to READ_ONLY.

DYNAMIC and KEYSET cursors default to OPTIMISTIC.

Cursor names can be referenced only by other Transact-SQL statements. They cannot be referenced by database API functions. For example, after declaring a cursor, the cursor name cannot be referenced from OLE DB, ODBC, ADO, or DB-Library functions or methods. The cursor rows cannot be fetched using the fetch functions or methods of the APIs; the rows can be fetched only by Transact-SQL FETCH statements.

After a cursor has been declared, these system stored procedures can be used to determine the characteristics of the cursor.

System stored procedure description

sp_cursor_list: Returns a list of cursors currently visible on the connection and their attributes.
sp_describe_cursor: Describes the attributes of a cursor, such as whether it is a forward-only or scrolling cursor.
sp_describe_cursor_columns: Describes the attributes of the columns in the cursor result set.
sp_describe_cursor_tables: Describes the base tables accessed by the cursor.

Variables may be used as part of the select_statement that declares a cursor. Cursor variable values do not change after a cursor is declared. In SQL Server version 6.5 and earlier, variable values are refreshed every time a cursor is reopened.

Permissions

DECLARE CURSOR permissions default to any user that has SELECT permissions on the views, tables, and columns used in the cursor.

 

 

Sources include the Microsoft website

Difference and Limitations: MSDE vs. SQL Server

When Microsoft first introduced MSDE 1.0, it was called Microsoft Data Engine and it shared the same code base as SQL Server 7.0. With the release of SQL Server 2000, Microsoft introduced MSDE 2000 and called it Microsoft SQL Server 2000 Desktop Engine. This article provides information on MSDE 2000 as it compares to SQL Server.

MSDE 2000 is a redistributable version of SQL Server 2000. It is a database engine provided by Microsoft that is based on the core SQL Server technology and supports single- and dual-processor desktop computers. In other words, MSDE 2000 is a scaled down copy of SQL Server. MSDE 2000 was introduced to provide application developers a database engine that is more powerful than the Jet engine and at the same time expandable to SQL Server. It is ideal for client applications requiring an embedded database and websites serving up to 25 concurrent users.

The common technology base shared between SQL Server and MSDE 2000 enables developers to build applications that can scale seamlessly from desktop solutions to multiprocessor enterprise clusters.

As an alternative to the Jet engine, MSDE 2000 provides a cost-effective option for developers who need a database server that can be easily distributed and installed. Because it is fully compatible with SQL Server, developers can easily target both SQL Server and MSDE 2000 with the same application code base. This provides a seamless upgrade path from MSDE 2000 to SQL Server if an application grows beyond the storage and scalability limits of MSDE 2000.

MSDE Licensing

MSDE is not for sale as a separate product. It is available for royalty-free redistribution by vendors under certain MSDE licensing conditions. You don’t need to buy Client Access License if your application uses MSDE as a back-end. Check Microsoft’s website for details on MSDE licensing.

Managing MSDE Databases – SQL Server Enterprise Manager

Unlike SQL Server, MSDE does not have its own tools for database design and management. MSDE ships with the OSQL utility only.

MSDE Database Limitations

MSDE is intended for single user or small workgroup environments. The following are some of the MSDE limitations in comparison with SQL Server:

  • No Enterprise Manager
  • No Query Analyzer
  • No Index Tuning Wizard
  • Only 2GB RAM
  • Only 2GB database size limit
  • Only 2 CPUs
  • Only five concurrent batch workloads or 25 concurrent connections for websites
  • No Database Server Failover Support
  • No Full-text search
  • No SQL Server Profiler
  • No Import and Export Wizards
  • No OLAP
  • No English Query
  • No SQL Books Online
  • No Full or Bulk-Logged recovery model support (only simple)

(This list covers most of the MSDE limitations. There may be a few omitted.)

MSDE Requirements – Hardware

Processor:

Intel Pentium 166 MHz or higher processor

Memory:

Windows XP: 128 megabytes (MB) of RAM
Windows 2000: 64 MB of RAM
All other operating systems: 32 MB of RAM

Hard disk:

44 MB of available hard disk space

MSDE Requirements – Operating Systems

Windows Server 2003, Standard Edition
Windows Server 2003, Enterprise Edition
Windows Server 2003, Datacenter Edition
Windows Server 2003, Web Edition
Windows 2000 Server
Windows 2000 Advanced Server
Windows 2000 Datacenter Server
Windows NT Server 4.0 with Service Pack 5 (SP5) or later
Windows NT Server 4.0, Enterprise Edition, with SP5 or later
Windows NT Workstation 4.0 with SP5 or later
Windows XP Professional
Windows XP Home Edition
Windows 2000 Professional
Windows Millennium Edition
Windows 98

Microsoft Windows 98 does not provide support for the following features:

  • Microsoft Windows NT® authentication
  • Fiber mode scheduling
  • Asynchronous I/O
  • Read ahead
  • Performance Monitor counters
  • Scatter/Gather I/O
  • Named pipes server network library
  • Appletalk server or client network library
  • Banyan Vines server network library

Remote MSDE Administration

MSDE 2000 can be administered with third-party MSDE tools both locally and remotely. However, it cannot be remotely administered in a multi-server environment where transactions happen across servers.

MDAC Explained (ADO version 2.5, 2.6, 2.7, and 2.8)

Microsoft Data Access Components (MDAC) include three technologies for accessing data: ActiveX Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC).

OLE DB

Microsoft OLE DB is a set of COM interfaces that expose data from a variety of data sources including a bridge to ODBC to enable continued support for the broad range of ODBC database drivers.

ADO

ADO is an interface to OLE DB. It provides access to a variety of database systems and data structures through the OLE DB data provider.

ADO version and Windows

MDAC ships with the Windows operating system. Applications that use ADO can make use of the default version of ADO on the target Windows system. The following is a list of the default ADO versions that ship with Windows:

Windows ADO
Windows 98 ADO 2.1
Windows ME ADO 2.5
Windows 2000 ADO 2.5
Windows XP ADO 2.7
Windows 2003 Server ADO 2.8

 

Visit http://msdn.microsoft.com/data/ for more information about ADO and MDAC downloads.

View SQL Server Agent job history

You created a job to run two SQL statements every day at 1:00pm. When you checked your job (Jobs view in Teratrax Database Manager) the next day, you noticed that it says “Failed” under “Last Run Status”.

Run the following SQL command to determine the cause of failure. It returns the job history of the specified job (replace job name with the name of your job):

 

EXECUTE MSDB.DBO.SP_HELP_JOBHISTORY NULL,
job name‘, @MODE = N’SEM’

 

Result:

step_id step_name message run_status etc…
0 (Job outcome) The job failed. The… 0 etc…
1 Step1 Executed as user… 0 etc…

 

 

 

The middle cell in the second row contains the error messages that were recorded at the time the job ran. If the job was successful, the cell will still indicate the success status.

SQL Server does not exist or access denied

Every day, more enterprises resort to the internet to provide their clients with access to their SQL Server 2000 databases, or to gain access to databases hosted at remote locations. This makes SQL Server 2000 increasingly prone to security attacks. As a result, Microsoft is constantly adding security features to prevent attacks and secure the popular database server. These features make connecting to SQL Server 2000 increasingly difficult to troubleshoot. One of the more common error messages users get is “SQL Server does not exist or access denied” or “Specified SQL Server not found”.

Follow these steps to help you determine the reason you cannot connect to SQL Server 2000:

  1. Verify that SQL Server or MSDE is installed and running (see SQL Server Installation Verification for details).
  2. If you are connecting remotely (to a server on a different machine), make sure your connection is not blocked by any firewalls on either machines including Windows built-in Internet Connection Firewall (ICF) and Windows Firewall. Contact your system administrator for firewall configuration.
  3. If you are referencing an instance of SQL Server 2000 or MSDE 2000 other than the default instance, use the convention <server_name><instance_name> (example ProdServSales).
  4. Make sure you don’t have an older ADO version.
  5. Make sure your client protocols are configured properly.
  6. If you are connecting to a remote server and the server name is not resolved with DNS, use the IP address itself instead of the server name.
  7. Make sure that Windows XP SP2 is not blocking your connection.

SQL Server System Tables and Stored Procedures (SPs)

The following are system tables and stored procedures found in the master database and all user databases. This list contains both documented and undocumented system tables and stored procedures.

Tables in every database

dtproperties
syscolumns
syscomments
sysdepends
sysfilegroups
sysfiles
sysfiles1
sysforeignkeys
sysfulltextcatalogs
sysfulltextnotify
sysindexes
sysindexkeys
sysmembers
sysobjects
syspermissions
sysproperties
sysprotects
sysreferences
systypes
sysusers

Stored Procedures in every database

dt_addtosourcecontrol
dt_addtosourcecontrol_u
dt_adduserobject
dt_adduserobject_vcs
dt_checkinobject
dt_checkinobject_u
dt_checkoutobject
dt_checkoutobject_u
dt_displayoaerror
dt_displayoaerror_u
dt_droppropertiesbyid
dt_dropuserobjectbyid
dt_generateansiname
dt_getobjwithprop
dt_getobjwithprop_u
dt_getpropertiesbyid
dt_getpropertiesbyid_u
dt_getpropertiesbyid_vcs
dt_getpropertiesbyid_vcs_u
dt_isundersourcecontrol
dt_isundersourcecontrol_u
dt_removefromsourcecontrol
dt_setpropertybyid
dt_setpropertybyid_u
dt_validateloginparams
dt_validateloginparams_u
dt_vcsenabled
dt_verstamp006
dt_whocheckedout
dt_whocheckedout_u

Tables the master database

dtproperties
MSreplication_options
spt_datatype_info
spt_datatype_info_ext
spt_fallback_db
spt_fallback_dev
spt_fallback_usg
spt_monitor
spt_provider_types
spt_server_info
spt_values
sysaltfiles
syscacheobjects
syscharsets
syscolumns
syscomments
sysconfigures
syscurconfigs
syscursorcolumns
syscursorrefs
syscursors
syscursortables
sysdatabases
sysdepends
sysdevices
sysfilegroups
sysfiles
sysfiles1
sysforeignkeys
sysfulltextcatalogs
sysfulltextnotify

sysindexes
sysindexkeys
syslanguages
syslockinfo
syslocks
sysmembers
sysmessages
sysobjects
sysperfinfo
syspermissions
sysprocesses
sysproperties
sysprotects
sysreferences
SYSREMOTE_CATALOGS
SYSREMOTE_COLUMN_PRIVILEGES
SYSREMOTE_COLUMNS
SYSREMOTE_FOREIGN_KEYS
SYSREMOTE_INDEXES
SYSREMOTE_PRIMARY_KEYS
SYSREMOTE_PROVIDER_TYPES
SYSREMOTE_SCHEMATA
SYSREMOTE_STATISTICS
SYSREMOTE_TABLE_PRIVILEGES
SYSREMOTE_TABLES
SYSREMOTE_VIEWS
sysservers
systypes
sysusers
sysxlogins

Stored Procedures in the master database

dt_addtosourcecontrol
dt_addtosourcecontrol_u
dt_adduserobject
dt_adduserobject_vcs
dt_checkinobject
dt_checkinobject_u
dt_checkoutobject
dt_checkoutobject_u
dt_displayoaerror
dt_displayoaerror_u
dt_droppropertiesbyid
dt_dropuserobjectbyid
dt_generateansiname
dt_getobjwithprop
dt_getobjwithprop_u
dt_getpropertiesbyid
dt_getpropertiesbyid_u
dt_getpropertiesbyid_vcs
dt_getpropertiesbyid_vcs_u
dt_isundersourcecontrol
dt_isundersourcecontrol_u
dt_removefromsourcecontrol
dt_setpropertybyid
dt_setpropertybyid_u
dt_validateloginparams
dt_validateloginparams_u
dt_vcsenabled
dt_verstamp006
dt_whocheckedout
dt_whocheckedout_u
MS_sqlctrs_users
sp_ActiveDirectory_Obj
sp_ActiveDirectory_SCP
sp_ActiveDirectory_Start
sp_add_agent_parameter
sp_add_agent_profile
sp_add_data_file_recover_suspect_db
sp_add_datatype_mapping
sp_add_file_recover_suspect_db
sp_add_log_file_recover_suspect_db
sp_add_server_sortinfo
sp_add_server_sortinfo75
sp_addalias
sp_addapprole
sp_addarticle
sp_adddistpublisher
sp_adddistributiondb
sp_adddistributor
sp_addextendedproc
sp_addextendedproperty
sp_addgroup
sp_addlinkedserver
sp_addlinkedsrvlogin
sp_addlogin
sp_addmergealternatepublisher
sp_addmergearticle
sp_addmergefilter
sp_addmergepublication
sp_addmergepullsubscription
sp_addmergepullsubscription_agent
sp_addmergesubscription
sp_addmessage
sp_addpublication
sp_addpublication_snapshot
sp_addpublisher
sp_addpullsubscription
sp_addpullsubscription_agent
sp_addqueued_artinfo
sp_addremotelogin
sp_addrole
sp_addrolemember
sp_addscriptexec
sp_addserver
sp_addsrvrolemember
sp_addsubscriber
sp_addsubscriber_schedule
sp_addsubscription
sp_addsynctriggers
sp_addtabletocontents
sp_addtype
sp_addumpdevice
sp_adduser
sp_adjustpublisheridentityrange
sp_altermessage
sp_approlepassword
sp_article_validation
sp_articlecolumn
sp_articlefilter
sp_articlesynctranprocs
sp_articleview
sp_attach_db
sp_attach_single_file_db
sp_attachsubscription
sp_autostats
sp_bcp_dbcmptlevel
sp_bindefault
sp_bindrule
sp_blockcnt
sp_browsemergesnapshotfolder
sp_browsesnapshotfolder
sp_catalogs
sp_catalogs_rowset
sp_certify_removable
sp_change_agent_parameter
sp_change_agent_profile
sp_change_subscription_properties
sp_change_users_login
sp_changearticle
sp_changedbowner
sp_changedistpublisher
sp_changedistributiondb
sp_changedistributor_password
sp_changedistributor_property
sp_changegroup
sp_changemergearticle
sp_changemergefilter
sp_changemergepublication
sp_changemergepullsubscription
sp_changemergesubscription
sp_changeobjectowner
sp_changepublication
sp_changesubscriber
sp_changesubscriber_schedule
sp_changesubscription
sp_changesubscriptiondtsinfo
sp_changesubstatus
sp_check_constbytable_rowset
sp_check_constraints_rowset
sp_check_for_sync_trigger
sp_check_publication_access
sp_check_removable
sp_check_removable_sysusers
sp_check_sync_trigger
sp_checknames
sp_cleanupdbreplication
sp_cleanupwebtask
sp_column_privileges
sp_column_privileges_ex
sp_column_privileges_rowset
sp_columns
sp_columns_ex
sp_columns_rowset
sp_configure
sp_convertwebtasks
sp_copymergesnapshot
sp_copysnapshot
sp_copysubscription
sp_create_removable
sp_createstats
sp_cursor_list
sp_cycle_errorlog
sp_databases
sp_datatype_info
sp_db_upgrade
sp_dbcmptlevel
sp_dbfixedrolepermission
sp_dboption
sp_dbremove
sp_ddopen
sp_defaultdb
sp_defaultlanguage
sp_deletemergeconflictrow
sp_denylogin
sp_depends
sp_describe_cursor
sp_describe_cursor_columns
sp_describe_cursor_tables
sp_detach_db
sp_disableagentoffload
sp_diskdefault
sp_distcounters
sp_drop_agent_parameter
sp_drop_agent_profile
sp_dropalias
sp_dropanonymousagent
sp_dropapprole
sp_droparticle
sp_dropdevice
sp_dropdistpublisher
sp_dropdistributiondb
sp_dropdistributor
sp_dropextendedproc
sp_dropextendedproperty
sp_dropgroup
sp_droplinkedsrvlogin
sp_droplogin
sp_dropmergealternatepublisher
sp_dropmergearticle
sp_dropmergefilter
sp_dropmergepublication
sp_dropmergepullsubscription
sp_dropmergesubscription
sp_dropmessage
sp_droppublication
sp_droppublisher
sp_droppullsubscription
sp_dropremotelogin
sp_droprole
sp_droprolemember
sp_dropserver
sp_dropsrvrolemember
sp_dropsubscriber
sp_dropsubscription
sp_droptype
sp_dropuser
sp_dropwebtask
sp_dsninfo
sp_enableagentoffload
sp_enum_oledb_providers
sp_enumcodepages
sp_enumcustomresolvers
sp_enumdsn
sp_enumerrorlogs
sp_enumfullsubscribers
sp_enumoledbdatasources
sp_eventlog
sp_expired_subscription_cleanup
sp_fallback_MS_sel_fb_svr
sp_fetchshowcmdsinput
sp_fixindex
sp_fkeys
sp_foreign_keys_rowset
sp_foreignkeys
sp_fulltext_catalog
sp_fulltext_column
sp_fulltext_database
sp_fulltext_service
sp_fulltext_table
sp_generate_agent_parameter
sp_generatefilters
sp_get_distributor
sp_getagentoffloadinfo
sp_getapplock
sp_getarticlepkcolbitmap
sp_getmergedeletetype
sp_getqueuedrows
sp_getsubscriptiondtspackagename
sp_gettypestring
sp_grant_publication_access
sp_grantdbaccess
sp_grantlogin
sp_help
sp_help_agent_default
sp_help_agent_parameter
sp_help_agent_profile
sp_help_datatype_mapping
sp_help_fulltext_catalogs
sp_help_fulltext_catalogs_cursor
sp_help_fulltext_columns
sp_help_fulltext_columns_cursor
sp_help_fulltext_tables
sp_help_fulltext_tables_cursor
sp_help_publication_access
sp_helpallowmerge_publication
sp_helparticle
sp_helparticlecolumns
sp_helparticledts
sp_helpconstraint
sp_helpdb
sp_helpdbfixedrole
sp_helpdevice
sp_helpdistpublisher
sp_helpdistributiondb
sp_helpdistributor
sp_helpdistributor_properties
sp_helpextendedproc
sp_helpfile
sp_helpfilegroup
sp_helpgroup
sp_helpindex
sp_helplanguage
sp_helplinkedsrvlogin
sp_helplog
sp_helplogins
sp_helpmergealternatepublisher
sp_helpmergearticle
sp_helpmergearticlecolumn
sp_helpmergearticleconflicts
sp_helpmergecleanupwait
sp_helpmergeconflictrows
sp_helpmergedeleteconflictrows
sp_helpmergefilter
sp_helpmergepublication
sp_helpmergepullsubscription
sp_helpmergesubscription
sp_helpntgroup
sp_helppublication
sp_helppublicationsync
sp_helppullsubscription
sp_helpremotelogin
sp_helpreplfailovermode
sp_helpreplicationdb
sp_helpreplicationdboption
sp_helpreplicationoption
sp_helprole
sp_helprolemember
sp_helprotect
sp_helpserver
sp_helpsort
sp_helpsql
sp_helpsrvrole
sp_helpsrvrolemember
sp_helpstats
sp_helpsubscriberinfo
sp_helpsubscription
sp_helpsubscription_properties
sp_helptext
sp_helptrigger
sp_helpuser
sp_indexes
sp_indexes_rowset
sp_indexoption
sp_invalidate_textptr
sp_isarticlecolbitset
sp_ivindexhasnullcols
sp_link_publication
sp_linkedservers
sp_linkedservers_rowset
sp_lock
sp_logdevice
sp_makewebtask
sp_marksubscriptionvalidation
sp_mergearticlecolumn
sp_mergecleanupmetadata
sp_mergecompletecleanup
sp_mergedummyupdate
sp_mergepreparecleanup
sp_mergesubscription_cleanup
sp_monitor
sp_MS_marksystemobject
sp_MS_replication_installed
sp_MS_upd_sysobj_category
sp_MSacquireHeadofQueueLock
sp_MSacquireserverresourcefordynamicsnapshot
sp_MSacquireSlotLock
sp_MSactivate_auto_sub
sp_MSadd_compensating_cmd
sp_MSadd_distributor_alerts_and_responses
sp_MSadd_mergereplcommand
sp_MSadd_repl_job
sp_MSaddanonymousreplica
sp_MSaddexecarticle
sp_MSaddguidcolumn
sp_MSaddguidindex
sp_MSaddinitialarticle
sp_MSaddinitialpublication
sp_MSaddinitialschemaarticle
sp_MSaddinitialsubscription
sp_MSaddlogin_implicit_ntlogin
sp_MSaddmergedynamicsnapshotjob
sp_MSaddmergepub_snapshot
sp_MSaddmergeschemaarticle
sp_MSaddmergetriggers
sp_MSaddoffloadparameter
sp_MSaddpub_snapshot
sp_MSaddpubtocontents
sp_MSaddschemaarticle
sp_MSaddupdatetrigger
sp_MSadduser_implicit_ntlogin
sp_MSadjustmergeidentity
sp_MSagent_access_check
sp_MSalreadyhavegeneration
sp_MSareallcolumnscomputed
sp_MSarticlecleanup
sp_MSarticlecol
sp_MSarticlecolstatus
sp_MSbelongs
sp_MSBumpupCompLevel
sp_MSchange_priority
sp_MSchange_retention
sp_MSchangearticleresolver
sp_MSchangemergeschemaarticle
sp_MSchangeobjectowner
sp_MSchangeschemaarticle
sp_MScheck_agent_instance
sp_MScheck_subscription
sp_MScheck_uid_owns_anything
sp_MScheckatpublisher
sp_MScheckexistsgeneration
sp_MScheckidentityrange
sp_MSCheckmergereplication
sp_MScheckmetadatamatch
sp_MSchecksnapshotstatus
sp_MScheckvalidsystables
sp_MScleanup_conflict
sp_MScleanup_conflict_table
sp_MScleanup_metadata
sp_MScleanup_publication_ADinfo
sp_MScleanupdynsnapshotvws
sp_MSCleanupForPullReinit
sp_MScleanupmergepublisher
sp_MScleanupmergepublisherdb
sp_MScleanuptask
sp_MSclearcolumnbit
sp_MScompletecleanup
sp_MScomputearticlescreationorder
sp_MScomputemergearticlescreationorder
sp_MScomputemergeunresolvedrefs
sp_MScomputeunresolvedrefs
sp_MScontractsubsnb
sp_MScopyregvalue
sp_MScopyscriptfile
sp_MScopysnapshot
sp_MScreate_dist_tables
sp_MScreate_distributor_tables
sp_MScreate_mergesystables
sp_MScreate_pub_tables
sp_MScreate_replication_checkup_agent
sp_MScreate_replication_status_table
sp_MScreate_sub_tables
sp_MScreatebeforetable
sp_MScreateglobalreplica
sp_MScreateretry
sp_MSdbuseraccess
sp_MSdbuserpriv
sp_MSdefer_check
sp_MSdeletecontents
sp_MSdeletepushagent
sp_MSdeleteretry
sp_MSdeletetranconflictrow
sp_MSdelgenzero
sp_MSdelrow
sp_MSdelsubrows
sp_MSdelsubrowsbatch
sp_MSdependencies
sp_MSdoesfilterhaveparent
sp_MSdrop_6x_replication_agent
sp_MSdrop_distributor_alerts_and_responses
sp_MSdrop_expired_mergesubscription
sp_MSdrop_expired_subscription
sp_MSdrop_mergesystables
sp_MSdrop_object
sp_MSdrop_pub_tables
sp_MSdrop_replcom
sp_MSdrop_repltran
sp_MSdrop_rladmin
sp_MSdrop_rlcore
sp_MSdrop_rlrecon
sp_MSdroparticleconstraints
sp_MSdroparticleprocs
sp_MSdroparticletombstones
sp_MSdroparticletriggers
sp_MSdropconstraints
sp_MSdropdynsnapshotvws
sp_MSdropfkreferencingarticle
sp_MSdropmergedynamicsnapshotjob
sp_MSdropmergepub_snapshot
sp_MSdropretry
sp_MSdroptemptable
sp_MSdummyupdate
sp_MSenum_misc_agents
sp_MSenum_replication_agents
sp_MSenum_replication_job
sp_MSenum_replqueues
sp_MSenum_replsqlqueues
sp_MSenum3rdpartypublications
sp_MSenumallpublications
sp_MSenumallsubscriptions
sp_MSenumchanges
sp_MSenumcolumns
sp_MSenumdeletesmetadata
sp_MSenumgenerations
sp_MSenummergepublications
sp_MSenumpartialchanges
sp_MSenumpartialdeletes
sp_MSenumpubreferences
sp_MSenumreplicas
sp_MSenumretries
sp_MSenumschemachange
sp_MSenumschemachange_70
sp_MSenumschemachange_80
sp_MSenumsubscriptions
sp_MSenumthirdpartypublicationvendornames
sp_MSenumtranpublications
sp_MSestimatemergesnapshotworkload
sp_MSestimatesnapshotworkload
sp_MSevalsubscriberinfo
sp_MSexclause
sp_MSexpandbelongs
sp_MSexpandnotbelongs sp_MSexpandsubsnb
sp_MSexternalfkreferences
sp_MSfetchidentityrange
sp_MSfillupmissingcols
sp_MSfilterclause
sp_MSfix_6x_tasks
sp_MSfixlineageversions
sp_MSfixupagentoffloadinfo
sp_MSfixupaltsnapshotfolder
sp_MSfixupdistributorinfo
sp_MSfixupdistributorsecurity
sp_MSfixupftpinfo
sp_MSfixupsharedagentproperties
sp_MSfixupuseftp
sp_MSfixupworkingdirectory
sp_MSflush_access_cache
sp_MSflush_command
sp_MSforeach_worker
sp_MSforeachdb
sp_MSforeachtable
sp_MSgen_sync_tran_procs
sp_MSgenreplnickname
sp_MSgentablenickname
sp_MSget_agent_names
sp_MSget_attach_state
sp_MSget_col_position
sp_MSget_colinfo
sp_MSget_current_activity
sp_MSget_file_existence
sp_MSget_jobstate
sp_MSget_load_hint
sp_MSget_map_position
sp_MSget_mergepullsubsagent_owner
sp_MSget_oledbinfo
sp_MSget_publication_from_taskname
sp_MSget_publisher_rpc
sp_MSget_pullsubsagent_owner
sp_MSget_qualified_name
sp_MSget_setup_paths
sp_MSget_shared_agent
sp_MSget_subtypedatasrc
sp_MSget_synctran_column
sp_MSget_synctran_commands
sp_MSget_type
sp_MSgetalertinfo
sp_MSgetarticlereinitvalue
sp_MSgetbeforetableinsert
sp_MSgetchangecount
sp_MSgetcolordinalfromcolname
sp_MSgetcolumnlist
sp_MSgetconflictinsertproc
sp_MSgetconflicttablename
sp_MSgetlastrecgen
sp_MSgetlastsentgen
sp_MSgetlastsentrecgens
sp_MSgetlastupdatedtime
sp_MSgetmergelastupdatedtime
sp_MSgetmetadatabatch
sp_MSgetonerow
sp_MSgetpubinfo
sp_MSgetreplicainfo
sp_MSgetreplnick
sp_MSgetrowmetadata
sp_MSGetServerProperties
sp_MSgetsubscriberinfo
sp_MSgettablecontents
sp_MSgettools_path
sp_MSgettrancftsrcrow
sp_MSgettranconflictname
sp_MSgettranconflictrow
sp_MSgettranlastupdatedtime
sp_MSgettypestringudt
sp_MSgetviewcolumnlist
sp_MSguidtostr
sp_MShasdbaccess
sp_MShelp_distdb
sp_MShelp_identity_property
sp_MShelp_replication_status
sp_MShelp_replication_table
sp_MShelpalterbeforetable
sp_MShelpcolumns
sp_MShelpconflictpublications
sp_MShelpcreatebeforetable
sp_MShelpdestowner
sp_MShelpfulltextindex
sp_MShelpfulltextscript
sp_MShelpindex
sp_MShelpmergearticles
sp_MShelpmergeconflictcounts
sp_MShelpmergeconflictpublications
sp_MShelpmergedynamicsnapshotjob
sp_MShelpmergeidentity
sp_MShelpmergeschemaarticles
sp_MShelpobjectpublications
sp_MShelptranconflictcounts
sp_MShelptranconflictpublications
sp_MShelptype
sp_MShelpvalidationdate
sp_MSIfExistsRemoteLogin
sp_MSindexcolfrombin
sp_MSindexspace
sp_MSinit_replication_perfmon
sp_MSinit_subscription_agent
sp_MSinitdynamicsubscriber
sp_MSinsertbeforeimageclause
sp_MSinsertcontents
sp_MSinsertdeleteconflict
sp_MSinserterrorlineage
sp_MSinsertgenerationschemachanges
sp_MSinsertgenhistory
sp_MSinsertschemachange
sp_MSinstance_qv
sp_MSis_col_replicated
sp_MSis_identity_insert
sp_MSis_pk_col
sp_MSispkupdateinconflict
sp_MSkilldb
sp_MSload_replication_status
sp_MSlocalizeinterruptedgenerations
sp_MSlocktable
sp_MSloginmappings
sp_MSmakearticleprocs
sp_MSmakeconflictinsertproc
sp_MSmakeconflicttable
sp_MSmakectsview
sp_MSmakedynsnapshotvws
sp_MSmakeexpandproc
sp_MSmakegeneration
sp_MSmakeinsertproc
sp_MSmakejoinfilter
sp_MSmakeselectproc
sp_MSmakesystableviews
sp_MSmaketempinsertproc
sp_MSmaketrancftproc
sp_MSmakeupdateproc
sp_MSmakeviewproc
sp_MSmaptype
sp_MSmark_proc_norepl
sp_MSmarkreplinfo
sp_MSmarkschemaobject
sp_MSmatchkey
sp_MSmergepublishdb
sp_MSmergesubscribedb
sp_MSmergeupdatelastsyncinfo
sp_MSobjectprivs
sp_MSobjsearch
sp_MSpad_command
sp_MSpost_auto_proc
sp_MSprep_exclusive
sp_MSprepare_mergearticle
sp_MSprepare_sub_for_detach
sp_MSpreparecleanup
sp_MSpropagateschematorepubs
sp_MSproxiedmetadata
sp_MSpub_adjust_identity
sp_MSpublicationcleanup
sp_MSpublicationview
sp_MSpublishdb
sp_MSquerysubtype
sp_MSquiescecheck
sp_MSquiesceforcleanup
sp_MSquiescetriggersoff
sp_MSquiescetriggerson
sp_MSreenable_check
sp_MSrefcnt
sp_MSregistersubscription
sp_MSreinit_article
sp_MSreinit_failed_subscriptions
sp_MSreinit_hub
sp_MSreinitmergepublication
sp_MSreleaseSlotLock
sp_MSremove_mergereplcommand
sp_MSremove_userscript
sp_MSremovedbreplication
sp_MSremoveoffloadparameter
sp_MSrepl_addrolemember
sp_MSrepl_backup_complete
sp_MSrepl_backup_start
sp_MSrepl_check_server
sp_MSrepl_dbrole
sp_MSrepl_droprolemember
sp_MSrepl_gettype_mappings
sp_MSrepl_isdbowner
sp_MSrepl_linkedservers_rowset
sp_MSrepl_schema
sp_MSrepl_startup
sp_MSrepl_validate_dts_package
sp_MSreplcheck_connection
sp_MSreplcheck_name
sp_MSreplcheck_permission
sp_MSreplcheck_publish
sp_MSreplcheck_pull
sp_MSreplcheck_qv
sp_MSreplcheck_subscribe
sp_MSreplcheckoffloadserver
sp_MSreplicationcompatlevel
sp_MSreplraiserror
sp_MSreplrole
sp_MSreplsup_table_has_pk
sp_MSreplupdateschema
sp_MSreseed
sp_MSreset_attach_state
sp_MSreset_queue
sp_MSreset_queued_reinit
sp_MSreset_synctran_bit
sp_MSrestore_sub
sp_MSrestore_sub_merge
sp_MSrestore_sub_tran
sp_MSretrieve_mergepublication
sp_MSretrieve_publication
sp_MSretrieve_publication_attributes
sp_MSscript_article_view
sp_MSscript_beginproc
sp_MSscript_begintrig1
sp_MSscript_begintrig2
sp_MSscript_compensating_insert
sp_MSscript_compensating_send
sp_MSscript_delete_pubwins
sp_MSscript_delete_statement
sp_MSscript_delete_subwins
sp_MSscript_dri
sp_MSscript_endproc
sp_MSscript_endtrig
sp_MSscript_ExecutionMode_stmt
sp_MSscript_insert_pubwins
sp_MSscript_insert_statement
sp_MSscript_insert_subwins
sp_MSscript_missing_row_check
sp_MSscript_multirow_trigger
sp_MSscript_params
sp_MSscript_pkvar_assignment
sp_MSscript_procbodystart
sp_MSscript_pub_upd_trig
sp_MSscript_security
sp_MSscript_singlerow_trigger
sp_MSscript_sync_del_proc
sp_MSscript_sync_del_trig
sp_MSscript_sync_ins_proc
sp_MSscript_sync_ins_trig
sp_MSscript_sync_upd_proc
sp_MSscript_sync_upd_trig
sp_MSscript_trigger_assignment
sp_MSscript_trigger_exec_rpc
sp_MSscript_trigger_fetch_statement
sp_MSscript_trigger_update_checks
sp_MSscript_trigger_updates
sp_MSscript_trigger_variables
sp_MSscript_trigger_version_updates
sp_MSscript_update_pubwins
sp_MSscript_update_statement
sp_MSscript_update_subwins
sp_MSscript_validate_subscription
sp_MSscript_where_clause
sp_MSscriptdatabase
sp_MSscriptdb_worker
sp_MSscriptmvastable
sp_MSscriptmvastableidx
sp_MSscriptmvastablenci
sp_MSscriptmvastablepkc
sp_MSsendtosqlqueue
sp_MSset_current_activity
sp_MSset_sub_guid
sp_MSset_subscription_properties
sp_MSsetaccesslist
sp_MSsetalertinfo
sp_MSsetartprocs
sp_MSsetbit
sp_MSsetconflictscript
sp_MSsetconflicttable
sp_MSsetcontext_replagent
sp_MSsetfilteredstatus
sp_MSsetfilterparent
sp_MSsetlastrecgen
sp_MSsetlastsentgen
sp_MSsetreplicainfo
sp_MSsetreplicastatus
sp_MSsetrowmetadata
sp_MSSetServerProperties
sp_MSsetsubscriberinfo
sp_MSsettopology
sp_MSsetupbelongs
sp_MSsetupbelongs_withoutviewproc
sp_MSsetupnotbelongs
sp_MSsetupworktables
sp_MSSharedFixedDisk
sp_MSSQLDMO70_version
sp_MSSQLDMO80_version
sp_MSSQLOLE_version
sp_MSSQLOLE65_version
sp_MSsub_check_identity
sp_MSsub_cleanup_orphans
sp_MSsub_cleanup_prop_table
sp_MSsub_set_identity
sp_MSsubscription_enabled_for_syncmgr
sp_MSsubscriptionvalidated
sp_MSsubsetpublication
sp_MSsubst_filter_name
sp_MSsubst_filter_names
sp_MStable_has_unique_index
sp_MStable_not_modifiable
sp_MStablechecks
sp_MStablekeys
sp_MStablenamefromnick
sp_MStablenickname
sp_MStablerefs
sp_MStablespace
sp_MStestbit
sp_MSunc_to_drive
sp_MSuniquecolname
sp_MSuniquename
sp_MSuniqueobjectname
sp_MSuniquetempname
sp_MSunmarkifneeded
sp_MSunmarkreplinfo
sp_MSunmarkschemaobject
sp_MSunregistersubscription
sp_MSupdate_agenttype_default
sp_MSupdate_replication_status
sp_MSupdatecontents
sp_MSupdategenhistory
sp_MSupdatelastsyncinfo
sp_MSupdateschemachange
sp_MSupdatesharedagentproperties
sp_MSupdatesysmergearticles
sp_msupg_createcatalogcomputedcols
sp_msupg_dosystabcatalogupgrades
sp_msupg_dropcatalogcomputedcols
sp_msupg_recreatecatalogfaketables
sp_msupg_recreatesystemviews
sp_msupg_removesystemcomputedcolumns
sp_msupg_upgradecatalog
sp_MSUpgradeConflictTable
sp_MSuplineageversion
sp_MSvalidate_agent_parameter
sp_MSvalidate_subscription
sp_MSvalidatearticle
sp_MSverifytranfilter
sp_objectfilegroup
sp_oledb_column_constraints
sp_oledb_database
sp_oledb_defdb
sp_oledb_deflang
sp_oledb_indexinfo
sp_oledb_language
sp_oledb_ro_usrname
sp_oledbinfo
sp_password
sp_pkeys
sp_primary_keys_rowset
sp_primarykeys
sp_procedure_params_rowset
sp_procedures_rowset
sp_processmail
sp_procoption
sp_prop_oledb_provider
sp_provider_types_rowset
sp_publication_validation
sp_publishdb
sp_readerrorlog
sp_readwebtask
sp_recompile
sp_refreshsubscriptions
sp_reinitmergepullsubscription
sp_reinitmergesubscription
sp_reinitpullsubscription
sp_reinitsubscription
sp_releaseapplock
sp_remoteoption
sp_remove_tempdb_file
sp_removedbreplication
sp_removesrvreplication
sp_rename
sp_renamedb
sp_repladdcolumn
sp_repldropcolumn
sp_replica
sp_replication_agent_checkup
sp_replicationdboption
sp_replicationoption
sp_replproberemoteserver
sp_replqueuemonitor
sp_replrestart
sp_replshowcmds
sp_replsqlqgetrows
sp_replsync
sp_resetstatus
sp_resolve_logins
sp_restoredbreplication
sp_resyncmergesubscription
sp_revoke_publication_access
sp_revokedbaccess
sp_revokelogin
sp_runwebtask
sp_schemata_rowset
sp_script_reconciliation_delproc
sp_script_reconciliation_insproc
sp_script_reconciliation_xdelproc
sp_script_synctran_commands
sp_scriptdelproc
sp_scriptinsproc
sp_scriptmappedupdproc
sp_scriptpkwhereclause
sp_scriptreconwhereclause
sp_scriptsubconflicttable
sp_scriptupdateparams
sp_scriptupdproc
sp_scriptxdelproc
sp_scriptxupdproc
sp_server_info
sp_serveroption
sp_setapprole
sp_setnetname
sp_setreplfailovermode
sp_settriggerorder
sp_showrowreplicainfo
sp_spaceused
sp_special_columns
sp_sproc_columns
sp_sqlexec
sp_srvrolepermission
sp_statistics
sp_statistics_rowset
sp_stored_procedures
sp_subscribe
sp_subscription_cleanup
sp_table_constraints_rowset
sp_table_privileges
sp_table_privileges_ex
sp_table_privileges_rowset
sp_table_statistics_rowset
sp_table_validation
sp_tablecollations
sp_tableoption
sp_tables
sp_tables_ex
sp_tables_info_rowset
sp_tables_rowset
sp_tableswc
sp_tempdbspace
sp_trace_getdata
sp_unbindefault
sp_unbindrule
sp_unsubscribe
sp_updateextendedproperty
sp_updatestats
sp_user_counter1
sp_user_counter10
sp_user_counter2
sp_user_counter3
sp_user_counter4
sp_user_counter5
sp_user_counter6
sp_user_counter7
sp_user_counter8
sp_user_counter9
sp_validatelogins
sp_validatemergepublication
sp_validatemergepullsubscription
sp_validatemergesubscription
sp_validatepropertyinputs
sp_validlang
sp_validname
sp_verify_publication
sp_vupgrade_distdb
sp_vupgrade_mergetables
sp_vupgrade_MSsubscription_properties
sp_vupgrade_publisher
sp_vupgrade_publisherdb
sp_vupgrade_registry
sp_vupgrade_replication
sp_vupgrade_replmsdb
sp_vupgrade_subpass
sp_vupgrade_subscription_databases
sp_vupgrade_subscription_tables
sp_vupgrade_syscol_status
sp_who
sp_who2
xp_grantlogin
xp_logininfo
xp_revokelogin