The DBCC SHRINKDATABSE cannot be executed until the previous job step, the differential backup, has been completed. We should increase the time between these two job steps, or even better configure the last job step to run only after the differential backup has been completed.
Note: The DBCC SHRINKDATABASE statement shrinks data files on a per-file basis but shrinks log files as if all the log files existed in one contiguous log pool. The target size for the data and log files cannot be smaller than the minimum size of a file that was specified when the file was originally created, or the last explicit size set with a file size changing operation such as the ALTER DATABASE statement with the MODIFY FILE option or the DBCC SHRINKFILE statement.
The system monitor clearly indicates that the processors are overloaded. We need to decide which processors we should use for SQL Server. Processor 0 is the default CPU for the I/O subsystem. Network Interface Cards (NIC) are assigned to the remaining CPUs, starting from the highest-numbered CPU. The NIC would get processor 3.
SQL Server would be using all four processors by default.
The Windows NT/2000/XP operating system use processor 0. In order to avoid the logon
problems we should not let SQL Server to use this processor. Instead SQL Server should be configured to use processor 1, 2, and 3.
Note 1: The Affinity mask is used to exclude a processor on a multiprocessor computer from processing SQL Server 2000 threads. Default is equal distribution of SQL Server 2000 processes across all processors.
Note 2: Monitoring the Processor and System object counters provides information about the CPU utilization and helps in determining whether or not a bottleneck exists. The %Total Processor Time is used on multiple CPU Severs to gauge the average activity of the processors and shows the percentage of elapsed time that a processor is busy executing a nonidle thread. Values around 100 percent on a Server computer that processes many client requests indicate that processes are queuing up, waiting for processor time, and causing a bottleneck. Such a sustained high level of processor usage is unacceptable for a server.
Error 208 produces the message 'Invalid object name' and occurs when an object that does not exist in the current database is referenced. If the object exists in another database, we must use the USE statement to explicitly switch the context to the correct database or we must qualify the object name with the database name. A third option is to use the sp_defaultdb stored procedure. This stored procedure is used to change the default database for a login. When a client connects with SQL Server, the default database defined for its login becomes the current database without an explicit USE statement. The default database can be defined when the login is added with
sp_addlogin. When executing sp_addlogin the master database is the default database if a database is not specified. In this scenario a SQL Server 2000 login and a user account has been created for Andrew and he has been given database access and the required permissions.
The TABLOCK hint increases the number of locks during the adding process. This is the reason why response time are slows down during this process. By removing the TABLOCK hint the default more granular row-level lock will be used. This would decrease the scope of the locks which would result in less waiting jobs and performance would improve.
Note: The BULK INSERT statement is used to copy a data file into a database table or view in a format specified by the user. The BULK INSERT statement accepts the TABLOCK hint, which allows the user to specify the locking behavior that the BULK INSERT statement should use. TABLOCK specifies that a bulk update table-level lock is taken for the duration of the bulk copy. If TABLOCK is not specified, the default uses row-level locks.
CP. of each share= Rs.(25 + 2% of 25) = Rs.25.50.
Number of shares= = 500
The scenario states that power interruptions have occurred in the past. By buying a battery backup solution for the disk controllers the power interruption problem would be prevented.
Transact-SQL scripts can be used to create defined operators or alerts. Scripting all the
predefined operators and alerts and copying them to the servers if the same group of operators is responsible for responding to the same alerts on other servers can save time.
SQL Server 2000 permits the creation of links to OLE DB data sources called linked servers. After linking to an OLE DB data source, it is possible to reference rowsets from the OLE DB data sources as tables in Transact-SQL statements and to pass commands to the OLE DB data sources and include the resulting rowsets as tables in Transact-SQL statements. Each distributed query can reference multiple linked servers and can perform either update or read operations against each individual linked server. A single distributed query can perform read operations against some linked servers and update operations against other linked servers. The Microsoft OLE DB Provider for Oracle allows distributed queries to query data in Oracle databases.
Comments
There are no comments.Copyright ©CuriousTab. All rights reserved.