Software Applications Programming Errors and solutions.

1>data  2>index  3>text/image  4>GAM/SGAM  5>page free space 6>IAM  7>BCM  8>DCM

These queries can help you  To Identify The Long Running Queries in SQL. 1.SELECT creation_time ,last_execution_time ,total_physical_reads ,total_logical_reads ,total_logical_writes , execution_count , total_worker_time , total_elapsed_time , total_elapsed_time / execution_count avg_elapsed_time ,SUBSTRING(st.text, (qs.statement_start_offset/2) + 1, ((CASE statement_end_offset WHEN -1 THEN DATALENGTH(st.text) ELSE qs.statement_end_offset END - qs.statement_start_offset)/2) + 1) AS statement_text FROM sys.dm_exec_query_stats AS qs CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) st where total_elapsed_time >= 800000000 ORDER BY total_elapsed_time / execution_count DESC; 2.DBCC opentran(This command will display the longest running transactions on the database) and select * from sys.dm_tran_active_snapshot_database_transactions(this command will display the transactions about replication and mirroring and snapshot isolated related transactions)

To  add multiple foreign keys in a table from different reference tables in SQL you can try below methods in sql query editor. 1. Alter table table_name add constraint constraint_name foreign key(col_name) references table_name(col_name) GO. 2.Create foreign constraint WITH NOCHECK first then CHECK it with another alter statement.. Make sure to put GO in between each statement.. Just to safe side, SET ANSI PADDING ON on the top and OFF at the button..

Below query can create ldf file.Its creating second ldf file on Testdb Database. You can create as many as you want. USE [master] GO ALTER DATABASE [TestDb] ADD LOG FILE ( NAME = N'TestDB_Log2', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\Testdb_Log2.ldf' , SIZE = 1024KB , FILEGROWTH = 10%) GO I Hope this could be your expected solution.

Patch the passive node first then reboot the node and then fail over instance on that node and then in similar manner patch the other node. This you can apply for sql 2008 and above. In SQL Server 2012, there is a Cluster Aware Update that will automatically Update all the nodes. Start applying the service pack on the passive node and then failover the instance to passive node after the installation is over on the passive node now start applying the service pack on active node and again fail-over the node. On SQL Server 2008/ 2008R2 : Apply patches/hot-fixes on passive node(N2) first then reboot the server. once the passive node(N2) is up, fail-over the resources from active node(N1) to passive node(N2), perform the same steps on N1 node and fail-over the resources from N2 to N1. On SQL Server 2005 : Apply patches/hot-fixes only on active node(N1), same will be applied on passive node(N2) too. On SQL Server 2005 we need down time during this activity. But on SQL server 2008/2008R2 we

Run log back up job on primary server and disable backup job to make sure not to run any backup jobs further until we enable again. check the log back ups if there are any need to be restored on secondary db, restore them if any until all the log backups complete. Then disable the log shipping add mdf-ldf file take a log backup and restore the same on secondary database them enable log shipping and enable backup job as well. If the drives and path exist on secondary log shipping will not break, if the drives are different obviously log shipping will fail.u have to disable all jobs in primary make sure that in between no backups will happen. restore that log file backup with move option. If the path of both files are same it wont break logshipping. If.If path is different then manually restore that particular log backup with move option.

Microsoft SQL Server provides counters to monitor internal SQL Server resource called latches.Monitoring the latches to determine user activity and resource usage can help you to identify performance bottlenecks like Average Latch Wait Time,Waits/sec We can monitor the performance by using cpu usage and memory usage what is use of latch. Latches are light weight locks which SQL server acquires for pages in buffer. Latch is a synchronization mechanism between threads.Latch protects access to in memory data structures. latches are lightweight as compare to locks. the best example to understand latch is TEMP DB LATCH CONTENTION.

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.)