Tuesday, June 26, 2018
Wednesday, November 30, 2016
Steps by steps diagnosing:
Mutual Authentication Required. If the remote access communication is performed between two DTC services, this authentication information must specify a computer account that matches the remote transaction mode computer's host name.Incoming caller Authentication Required. Following Microsoft Best Practices, MSDTC on SQL Server must be clustered. If this is your case, you must configure the Transaction Manager Communication with this option because In a clustered environment, DTC authentication does not use the host name, it uses the name of the virtual service and just for being clustered, the configured DTC already trusts on the destination DTC.No Authentication Required is used in the following instances:
- Running Microsoft Windows 2000. (Non applicable to BizTalk 2006 and above)
- The transaction occurs between servers in two domains that do not have a mutual trust (Could be the case)
- Computers are communicating through workgroup (non applicable to BizTalk)XA TransactionsIn Windows XP , Windows Server 2003, and subsequent versions you can disable XA transactions to help prevent the security risk that arises when a user-specified DLL, used by the DTC to communicate with the XA partner's transaction manager, is loaded directly into the DTC process. This situation exposes a resource manager's databases to serious data corruption and can cause Denial of Service (DOS) attacks. The disabling of XA transactions helps to protect the DTC from this DLL attack.
Friday, April 16, 2010
osql -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -E
Windows Sharepoint Services 3.0 (WSS) installs and uses SSEE 2005.
Thursday, July 30, 2009
In SQL Server 2000, we can use sp_altermessage to suppress the message. However in SQL Server 2005, it does not work. We have to turn on the trace flag -T3688 to suppress it.
The Microsoft kbase article#922578: http://support.microsoft.com/kb/922578 describes the solution.
Monday, June 08, 2009
- Unable to connect to perfmon counter remotely.
- Cannot read remote registry.
The permission issue with "Unable To Connect to Perfmon Counter Remotely" can be fixed using the steps below:
- Open regedit on the machine to which you are trying to connect to perfmon.
- Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Perflib"HKLM\SYSTEM\CurrentControlSet\control\Secure\SecurePipeServer\winreg"
- Right click on Perflib key and select permissions.
- Click Add and add Local Service with full control.
- Save and exit.
- Restart the Remote Registry Service.
To resolve the issue of "Unable to Read Remote Registry", use Registry Editor to grant Read Only permissions to the Local Service user account. To do this, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Expand the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ SecurePipeServers
- Right-click winreg, and then click Permissions.
- Click Add.In the Enter the object names to select box, type Local Service, and then click OK. Alternatively, you can type the name of a user or group that you want to grant access permission.
- In the Permissions for LOCAL SERVICE list, next to Read, click to select the Allow check box.
- Quit Registry Editor, and then restart Remote Registry service.
- Application fundamentals such as concepts and architecture
- Application Installation and configuration
- Patching and Upgrades
- Patch Management and Version Control
- Customization Updates
- Cloning requirements. This can be frequent in an Apps environment
- Concurrent Managers
- Forms/Report Servers
- Web Servers
- All the "ad" utilities
- All the database restrictions for the applications. That is so that the installation is still supportable and conforms to all vendor (Oracle) requirements.
- All special application related regular and maintenance functions. Such as month end and period end functions.
- Understand any backup and recovery constraints. Such as for table imports (NOT) and partial recoveries.
- Special requirements and restrictions for tuning. Example optimizer and index requirements. Printer Configuration
- User Access Administration
Tuesday, October 24, 2006
SQL Server - Oracle
transaction log - redo log
database - schema
instance - instance/database
page - block
simple recovery model - noarchive mode
full recovery model - archive mode
indexed view - materialized view
filegroup - tablespace
clustered index - index organized table (IOT)
- to use it in the dimension table in the star schema. Updating the natural key in the dimension table will not cause the update in the fact table.
- to replace the composite primary key as join to other tables. The guideline is different between SQL Server and Oracle. SQL Server is more aggressive to use the surrogate key: 2-3 columns vs. 4-5 columns in Oracle.