أنشئ حسابًا أو سجّل الدخول للانضمام إلى مجتمعك المهني.
I do my work which is assigned by querying based on the requirement. If I find its taking too much time, then I try to find out what all process are running on the server or any deadlocks, etc are there causing the problem by running the sp_who system procedure and proceed with the results. Thanks.
I would like to say that always check out the privileges of my login id. Because at first whenever it will clear to me then some point of sql errror reduce during TSQL execution. At first login of SQL server always i am checking the (.mdf & .ldf) file location through TSQL (select * from master.sys.databases;) as well as recovery model of Master Database(mainly msdb , master) & (User Databases) . checking the no. of user database in the sql node, before doing any TSQL in SQL server. Check through the sql server agent , if any user database is in replication or mirroring. Because some time it will help me. Also check out the mail job has assigned for database backup or not. Is there any backup schedule assign for user database or not. if assign then go through the sql server agent log and check out the log details, for maintaining the database proper health.
If database is installed in virtual machine along with WSFC(windows server failover cluster) then check out the VSS & VDI is running or not (for windows environment) . Because apart from sql server native backup, VSS&VDI took snapshot backup of database. In case of any power failure or any disaster time. Also check out the SQL Browser is running or not through SQL server configuration manager. Also verify the port &(for UDP , loop back ip.0.0.1) . etc
Check the overall performance and access log
