Software Applications Programming Errors and solutions.

To convert excel sheet data into SQL Table you can use import and export wizard Sql server management studio ->choose the Database and right click on Database->Tasks->Import Data/Export Data will be avvailable on All sql server version then you can do import/export process

1.Check MSDB backup history for that database select * from msdb.dbo.backupset where name='dbname' and type='i' order by backup_finish_date desc 2.dbo.backupset: provides information concerning the most-granular details of the backup process dbo.backupmediafamily: provides metadata for the physical backup files as they relate to backup sets dbo.backupfile: this system view provides the most-granular information for the physical backup files USE AdventureWorks GO SELECT TOP 100 s.database_name, m.physical_device_name, CAST(CAST(s.backup_size / 1000000 AS INT) AS VARCHAR(14)) + ' ' + 'MB' AS bkSize, CAST(DATEDIFF(second, s.backup_start_date, s.backup_finish_date) AS VARCHAR(4)) + ' ' + 'Seconds' TimeTaken, s.backup_start_date, CAST(s.first_lsn AS VARCHAR(50)) AS first_lsn, CAST(s.last_lsn AS VARCHAR(50)) AS last_lsn, CASE s.[type] WHEN 'D' THEN 'Full' WHEN 'I' THEN 'Differential' WHEN &

To change log file auto growth restricted growth to unrestricted growth in SQL you can try option below. I hope it will help you. Right click on "dbname" ->Properties ->Click on files ->you will  find options there

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.