LYCOS RETRIEVER
Sql Server 2000
built 242 days ago
SQL Server has always supported triggers, a special class of stored procedures defined to execute automatically when an update, insert, or delete statement is issued against a table. This ability has been extended with the inclusion of an INSTEAD OF trigger, which ... has the ability to be specified on views. An AFTER trigger is now the default trigger, synonymous with previous trigger definitions.
Source:
SQL Server normally supports up to 2 GB memory on x86 hardware, though it can be configured to use up to 64 GB if Address Windowing Extension is used on supporting OS. For x64 hardware, it supports 8 TB of memory, and 7 TB for IA-64 systems. However, when running x86 versions of SQL Server on x64 hardware, it can access 4 GB of memory without any special configuration.[3]
Source:
If you're new to SQL Server 2000, you will benefit from this book's explanation of the different ways to achieve a task, and the benefits and disadvantages of each method. If you're a more experienced SQL Server DBA, this book enables you quickly to reference the specifics of a command or process, brings you up-to-date with the technology, and helps you refine your craft.
Source:
Unlike most books on SQL Server, the SQL Server 2000 Resource Kit is not designed to be read from beginning to end. It is not a tutorial, and it is not designed to teach you how to be a SQL Server DBA. The best way to describe it is that it is a collection of advanced SQL Server information targeted toward experienced DBAs who are looking for very specific information on very specific topics. Most DBAs will only want to read those sections that are of direct interest. Some of these sections include:
Source:
Although SQL Server Express has a number of new features, some MSDE features are no longer included in the new Express edition of SQL Server 2005. The following table provides a comparison of MSDE and SQL Server 2005 Express:
Source:
SQL Server only uses the Queue Reader Agent when you add queued updating subscribers to transactional replication. The Queue Reader Agent runs on the distributor and reads either a queue stored in a table on the subscriber, or a Microsoft Message Queue.
Source: