Answer:- DBRM denotes Database Request Module. It has the SQL statements that are extracted from the host language program obtained by the pre-compiler. PLAN is the result of the BIND process and has executable code for SQL statements in DBRM.

Answer:- ACQUIRE/RELEASE in BIND determines the point at which DB2 either acquires or releases locks against the table and the table spaces. This includes the intent locks.

Answer:- PACKAGES contain executable codes for SQL statements in respect of one DBRM.

Answer:- When used, PACKAGES help avoid binding of large numbers of DBRM members in one plan. They also dispense with the cost of large BIND and avoid the entire transactions making them unavailable during BIND and automatic REBIND of the plan. Another advantage is that they minimize the fallback complexities when changes result in an error.

Answer:- A collection is a user-defined name that works as the anchor for packages but has no physical existence. It is used for the grouping of packages.

Answer:- Dynamic SQL is the SQL statement created at the time of the execution of a program.

Answer:- SQL Server • Windows and Linux • T-SQL (Transact-SQL) • Simpler and easy to use • Simple Oracle • Windows, Solaris, Linux, and Unix • PL/SQL (Procedural Language/ SQL) • Complex but powerful • Complex

Answer:- To hide a SQL Server instance, we need to make a change in SQL Server Configuration Manager. To do this, we have to follow the below steps: • First, in SQL Server Configuration Manager, we have to expand ‘SQL Server Network Configuration’ • Right-click on Protocols for and select ‘Properties’ • Once we do that, we will find a ‘HideInstance’ box in which, on the ‘Flags’ tab, we have to select ‘Yes’ • After that, click on ‘OK’ Note: While hiding a named instance, we need to provide the port number in the connection string so that even if the browser is running it is possible to connect to the hidden instance.

Answer:- Yes. we can add CPUs physically by adding new hardware, either logically by online hardware partitioning or virtually through a virtualization layer. Starting with its 2008 version, SQL Server supports CPU Hot Add. There are a few requirements to use CPU Hot Add: • Hardware that supports CPU hot add • 64-bit edition of Windows Server 2008 Datacenter or Windows Server 2008 Enterprise Edition for Itanium-based system OS • SQL Server Enterprise Once the CPU is added, we need to run RECONFIGURE, and then SQL Server recognizes the newly added CPU.

Answer:- TELNET PORTNUMBER TELNET PAXT3DEVSQL24 1433 TELNET PAXT3DEVSQL24 1434 Common Ports: MSSQL Server: 1433 HTTP TCP 80 HTTPS TCP 443

Answer:- • Single-user Mode (-m): • sqlcmd –m –d master –S PAXT3DEVSQL11 –c –U sa –P ******* • DAC (-A): • sqlcmd –A –d master –S PAXT3DEVSQL11 –c –U sa –P ******* • Emergency: • ALTER DATABASE test_db SET EMERGENCY

Answer:- • In the SHRINKFILE command, SQL Server isn’t careful about where it puts the pages that are moved from the end of the file toward the beginning of the file. • Data becomes fragmented, potentially up to 100 percent, and hence it is a performance killer for the database. • Slow operation: All pointers, being moved to/from the page/rows, have to be fixed and the SHRINKFILE operation is single-threaded, so it can be really slow (the single-threaded nature of SHRINKFILE is not going to change any time soon) Recommendations: • First, use TRUNCATEONLY to shrink the file. It removes the inactive part of the log and then performs the shrink operation. • Rebuild/reorganize indexes once the shrink is done so that the fragmentation level is decreased.

Answer:- • Preferring NT authentication • Using server, database, and application roles to control access to data • Securing physical database files using NTFS permissions • Using an unusable SA password for restricting physical access to SQL Server • Renaming the Administrator account on the SQL Server computer • Disabling the Guest account • Enabling auditing using multiprotocol encryption • Setting up SSL and firewalls • Isolating SQL Server from the webserver

Answer:- Connect using DAC via CMD or SSMS: • Connect via CMD • SQLCMD -A –U myadminlogin –P mypassword -SMyServer –dmaster • Once you connect to the master database, run the diagnostic queries to find the problem • Correct the issue and restart the server