Software Applications Programming Errors and solutions.

This is a list of ll SQL Server Build versions till Year 2014 6.50.201 SQL Server 6.5 RTM 6.50.213 SQL Server 6.5 SP1 6.50.240 SQL Server 6.5 SP2 6.50.258 SQL Server 6.5 SP3 6.50.281 SQL Server 6.5 SP4 6.50.415 SQL Server 6.5 SP5 6.50.416 SQL Server 6.5 SP5a SQL Server 6.5 7.00.0623 SQL Server 7 RTM 7.00.0699 SQL Server 7 SP1 7.00.0842 SQL Server 7 SP2 7.00.0961 SQL Server 7 SP3 7.00.1063 SQL Server 7 SP4 SQL Server 7 8.00.0194 SQL Server 2000 RTM 8.00.0384 SQL Server 2000 SP1 8.00.0534 SQL Server 2000 SP2 8.00.0760 SQL Server 2000 SP3 8.00.2039 SQL Server 2000 SP4 SQL Server 2000 9.00.1399 SQL Server 2005 RTM 9.00.2047 SQL Server 2005 SP1 9.00.3042 SQL Server 2005 SP2 9.00.3042.01 SQL Server 2005 "SP2a" 9.00.3054 SQL Server 2005 KB934458 9.00.3077 SQL Server 2005 Security Update 9.00.3152 SQL Server 2005 SP2 Cumulative Hotfix 9.00.3161 SQL Server 2005 SP2 CU1 9.00.3175 SQL Server 2005 SP2 CU2 9.00.3186 SQL Server 2005 SP2 CU3 9.00.3200

The server network address "xxxxx" can not be reached or does not exist. Check the network address name and reissue the command. Pls check endpoints on all servers using SELECT * FROM sys.endpoints If 1418 error: check it these, duplicate end points exists, tcp/ip enabled or not, check editions principal and mirror, windows firewall off, check login not created in mirror instance. How to delete duplicate end points if exists ? IF EXISTS (SELECT * FROM sys.endpoints e WHERE e.name = N'EndPoint_name') DROP ENDPOINT [EndPoint_name] GO

I am getting following SQL Error on running of Enterprise portal ,sharepoint site Could you advice solution on this error. Unknown SQL Exception 10054 occured. Additional error information from SQL Server is included below. A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) Possible solution: An error has occurred while establishing a connection to the server. When connecting to SQL Serve and this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.)

There might be some reasons behind it: 1. Blocking situation 2. lack of userfull indexes 3. Lack of updated statistics 4. deadlock situation 5. network issue 6.Check the status of query.It can be either of two reasons.Either external or internal factor.External factors are resource crunches .Internal factors are because of missing index, invalid cache plan, fragmentation,so on.Starting point to identify higher level and then do a deep dive into particular area.

Log shipping, mirroring & replication are various types of HA (high availability) features. Each of them have their own set of pros and cons and various sets of features. Hence there is no compulsion and requirement to implement all of them. Rather the decision to choose them is driven by business requirement and at times the resources available for use. Db mirroring and log shipping are database level HA the replication is object level HA. If you have SSRS, then go for replication, never keep OLTP database to fetch SSRS reports. Replication is never a DR lets take an example that for your reporting environment you habe used transactional replication. On the reporting database server for best performance you build plenty of indexes which are not required on the OLTP environment therefore I believe clustering mirroring and log shipping are the best option always have a powerful backup strategy that will always help you.

Following the steps below to Move Reporting server database instance from one server to another in SQL Server 2005,2008,2012 etc 1. Take the backup report server and report server temp db and restore in another server. ( if you want to move db also) 2. In the new server open reporting service configuration manage and re configure with new server details and start again. 3. Remove the encryption keys . Then reports will work from new server.

Transaction log backup captures the transaction log which contains a record of all committed or uncommitted transactions. In full recovery model, some time log file getting full that and first we will check log bak taken r not the we ill take log backup then it will clear all committed transaction from log file this will happen if have doubt create on database do some bulk(select into or insert into) trans and check log file size and take t log back then compare sizes. Transaction log is a physical file in which SQL server stores the details of all transactions and data modifications performed on the database.In the event of of disaster, that causes SQL server to shutdown unexpectedly (Power failure/hardware failure), the transaction log is used to bring the database in a consistent state while restarting the server.On restarting the server, database goes through the recovery process.During this recovery process , the transaction log is used to make sure that all committed transaction