Profiler was run against a database looking for "long running" queries. I used the Duration column to filter out the queries that I didn't want. When reviewing the output, I noticed that for some queries the StartTime was equal to the EndTime even though the Duration was set higher.
My question is, "What can account for this discrepancy and what inferences should I draw about the difference?"
Does the difference represent a resouce being locked or some other type of blocking (Duration) and once the query was allowed to run, it completed quickly?
TIA
=======================================
If Tyranny and Oppression come to this land, it will be in the guise of fighting a foreign enemy. -James Madison, fourth US president (1751-1836)
If monitoring for duration with sql profiler, what does the number represent ie 2733906 is it milliseconds, thousandths, looked in BOL no clear definition
Sarfaraz writes "I have captured SQL Profiler data. I was reviewing top running CPU intensive SQL statements. The Duration (in seconds) 1.39, 1.09, 0.16 and CPU (in seconds) 0.97, 0.95, 0.16 respectively for some SQL statements. How do I know what is the normal baseline for duration and CPU in order to determine the CPU intensive SQL statements.
Secondly same question for long running procedure duration 0.14, 0.11. What is the normal baseline here. Is this normal or too long.
We have a VLDB ( few table with above 200 million records ). This database is used for performance testing by simulating for 150 users and executing all necessary functional flows.
When I examined the profiler results , I could see some very high values as shown below in the duration column for many events.
1521729 3462142 1624325 3211255 1248276 3903998
Does it mean that that SP or the T-Sql statement is taking this much time in milliseconds to execute and give the output ?
I have a procedure in a history database that does insert into 3 tables inside a transaction. users complaint that the proc sometimes takes too long during heavy usage. I did some traces to see what is taking up the time, I found that the rpc duration was averaging > 500 ms (should only take 50ms). I checked to see if one of that statements were taking too much time, but only see the commit transaction statement taking around 500 ms). I check the avg disk queue to be around 30. ( this is on a single local disk) .
So is this definitely a disk issue, or is there something else I need to check
I am working with a proprietary database that records the date, time,location, and speed of a vehicle. It is pulling this information fromGPS unit tied to a vehicle. The table is populated with values thatare pulled from the GPS unit every 30 seconds. I need to find theduration of time for when a vehicle is stopped. I have created acursor that runs though all of the tables, and gathers the data forwhen the vehicle's speed is equal to zero. I have inserted this datainto a temp table, where I am having a problem is identifying theduration of time the vehicle is stopped. I cannot figure out how toquery the table and grab the first row when the speed is zero and thelast row where the speed is zero.The data looks like this…Date TimeVehIDLatLongSpeed12/31/2003 66144 295708535220842.92747-83.63003012/31/2003 66159 295708535220842.92696-83.62935012/31/2003 66179 295708535220842.9271 -83.62902 012/31/2003 66269 295708535220842.92709-83.62903012/31/2003 66359 295708535220842.9271 -83.62901012/31/2003 66449 295708535220842.92709-83.62904012/31/2003 66539 295708535220842.92708-83.62903012/31/2003 66629 295708535220842.92708-83.629 012/31/2003 66719 295708535220842.92708-83.62903012/31/2003 67414 295708535220842.9269 -83.630920Any help would be greatly appreciated…Thanks,Dave
I have a very stranger problem that I need to understand... In last days I executed a plan SQL 2005 Profiler to review TSQL Duration. When reviewing the results encounter that a SP displays a value of 4037312 in field DURATION which are not normal. Could to help me to identify why passes this?
Due to the 50000 character limitation; I'll post the remaining part of this issue in a reply to this original message.
With the help of forum members, I was able to put together the code below to display the duration times each patient spend in each care unit. If I un-remark the where clause for a single account number, then the result set (see result set #1) is correct. However, when I run it remarked out to get all patients, then the duration times change (see result set #2). The duration times for patient Jane Doe changes; can anyone see why this might be occurring?
Code Block ;WITH CTE AS ( SELECT CONVERT(NVARCHAR,DATE_IN, 112) as DATE_IN, ACCOUNT_NUMBER, PATIENT_NAME, CAREUNIT_KEY, CARE_UNIT, CARE_UNIT_DESC, DATE_TIME_IN, EPISODE_KEY, TIME_IN, ADMIT_DATE, DISCH_DATE, MEDREC_NO, SERVICECODE, PROVIDER_CODE, PROVIDER_ROLE, PHYSNAME ROW_NUMBER() OVER (ORDER BY DATE_TIME_IN) AS seq FROM reports.CAREUNITS_INFO --where account_number IN ('777777') ) SELECT a.DATE_IN, a.ACCOUNT_NUMBER, a.PATIENT_NAME, a.CAREUNIT_KEY, a.CARE_UNIT, a.CARE_UNIT_DESC, a.DATE_TIME_IN, a.TIME_IN, DATEDIFF(second, a.DATE_TIME_IN, b.DATE_TIME_IN) / 3600 as Duration_Hours, (DATEDIFF(second, a.DATE_TIME_IN, b.DATE_TIME_IN) % 3600 / 60) AS Duration_Minutes, a.ADMIT_DATE, a.DISCH_DATE, a.MEDREC_NO, a.SERVICECODE, a.PROVIDER_CODE, a.PROVIDER_ROLE, a.PHYSNAME FROM cte a INNER JOIN cte b ON a.Seq + 1 = b.Seq order by a.DATE_IN, a.ACCOUNT_NUMBER
Please see my reply for the remainder of this message...
I've set the Duration of my trace to "Greater than or Equal to: 1000". However when I start my trace the Duration column is now empty. Prior to the setting, there were values showing in this column. Any ideas on how to fix this?
I have quick question. Ihave a job which consists of 9 steps. 9th step is: Exec xp_cmdshell 'c:mssql.bat'. in this batch file I am stopping and starting SQL services using net stop and net start command. This job is running perfectly but it is not giving the job history when I right click the job and view job history I can't see anything where as if I check the checkbox for Show step details it showing first 8 steps information but it is not showing 9th step information. Even I checked the Sysjobhistory system table in MSDB it shows only 8 steps information. What is the reason....
New here:) and hoping someone might be able to shed a little light on a problem I am having.
I have a job scheduled, which needs to be periodically stopped and then restarted. After looking through various places I think the start method and stop method are the best bets?:rolleyes: But not really sure to be honest.
Can anyone give me some tips/pointers/opinions on what would be the best way to do this. (have tried to setup a job with the said method in each step - but it doesn't like my syntax.
Is there any way to schedule stop and start of NT services at a particular time daily.
For eg: If i have a service by name TemServer and if i need to stop that service each night at 9:00 and restart as soon as it stops.??
And Is there any way to start and stop the services of NT from workstation. Each and every time i am going to the server room for stopping the service and restarting.
how i can do it?Under Xp/2000, i write a application that stop/start this serices, butunder Win98, how i do it?Exists a method via SqlServer or a dos command to stop/start the MSDEprogram?Thanks a lotTomas--Questa è una firma automatica di MesNews.Sito: http://mesnews.no-ip.com
What is impact, if i stop and start Synchronization, for one subscription.
When i start, will it resync all tables by dropping and recreating at subscription.
On Publisher,  from Location Publiction,   right click on subscription,       select View Synchronization Status,  From here, stop and start
I want to create a package which start and stop the SQL server's services... i know i can achive this via NET COMMAND.... but i coudnt find in which task (SSIS) I can place that command?..
I also came across that I can achieve this using Execute Process task but for this I have to define executable file.... actually i dont want ne thing outside from my SSIS package
I want to tell to user about SQL Server Configuration Manager and wants to allow him "START / PAUSE / STOP" for SQL Server Express in system Tray. It is easy for the end user who don't know SQL Server.
A few service stop/start/restart questions on SQL Server 2005 SP2, whichI'll call SQLS.It looks as if there are *potentially* 6 ways to start/stop SQLSServices like the engine itself, integration services, reportingservice, Agent..-SQLS Configuration Manager-SQLS Surface Area Configuration (for Services and Connections)-Mgmt Studio Local (on server)-Mgmt Studio Remote (on client)-Windows Control Panel->Admin Tools->Services-Command Prompt (ala net start MSSQLSERVER)By policy, I am /not/ Administrator on the server. But I am SysAdminrole in SQLS. I have had various levels of success starting/stoppingservices in the ways listed above. In some I get Access denied, and inothers I get no msg and it simply doesn't work.Is there some special non-Admin OS group I need to be in to start/stopservices? Is this handled differently in the different interfaceslisted above?It seems like my best success for starting/stopping the engine and Agentis in /local/ Mgmt Studio, but /not/ remote Mgmt Studio - the optionsare greyed out on a remote client. Is this by design? Is it a SQLSbug?I'm sure I'm not the only SQLS DBA who does not have Admin rights on hisserver who wants to start/stop services. Generally speaking, how isthis intended to work?Any help appreciated.Allen JantzenA freshly minted DQLS DBA
Hi I have upgraded my local to sql server 2005, but still need to access the remote instance which is still at version 2008/8.0. Enterprise Manager has been removed (by the SQL server 2005 installation) Does anyone know how I can restart older version of SQL server instance (ie 2000/8.0) using SQL server Management Studio?
I don't have admin access on the server which the sql remote instance is hosted. Can get around it by asking the sys admin guy to do it for now but would prefer to continue to be able to do it myself. SQL Server Configuration Manager can only manage SQL server 2005 versions - a nice little caveat!
Is there a way to stop/start remote services using 'net stop/start'? - without having to write code.... I'll continue to search for a solution, but if someon can point me in the right direction, I'd be most greatful.
I'm getting this error message when I upgraded the SQL Server to install SSIS and other components.
===================================
The service did not respond to the start or control request in a timely fashion, you need administrator privileges to be able to start/stop this service. (SQLSAC)
------------------------------ Program Location:
at Microsoft.SqlSac.MainPanel.ServiceProgressBar.RefreshService()
I am attempting to create a new trace but I get the following error message: "failed to start a new trace".
I have been doing some digging and as I understand it, I had to find the directory Profiler uses for temporary files. So, I typed the following in the command window "SET TMP" and I received the following reply:
C:UsersRossAppDataLocalTemp
Now, according to the forum: [URL] ...
I am supposed to check that the system folder pointed to by the TMP environment variable exists and is not crammed with files.
Well, when I went to the directory C:UsersRossAppDataLocalTemp, it is indeed full of both files and directories. The size is 16.3 MB and has 133 files and 63 folders.
When I had a look at the Environment Variables window and chose TMP the value is "%USERPROFILE%AppDataLocalTemp" which according to my limited understanding is the equivalent to C:UsersRossAppDataLocalTemp.
So, what I am wondering is am I supposed to totally clear out this directory? I am not too keen on doing this because I don't want to stuff my PC up.
For some reason the status lights in my Enterprise manager are no longer working. I am connected to the databases, but because the indicator lights are not working, I can`t get a quick visual status of my servers. Any way to get my lights back on?
I have a question about granting enough rights to allow a non admin user to start and stop a sql server service via the SQL Server Management Studio by right clicking on the server node.
I have changed the acl's of the SQL Server service security and gave the user rights to start and stop the service. This does allow them to connect remotly to the server using computer manager and they successifully start and stop the service. But, in SQL Server Management Studio the option still does not show up, unless he is a admin of the server.
Does anyone know what other security settings I need to address for the start and stop to show up when I right click on the server node?
Which works fine, but what I need to calculate the total duration of a request based on the duration of the tasks completed in the request based on Req_ID. I would like to use the CASE statement I have to determine the SLA_Mins for each task and add them together to get total request SLA_Mins.
Below is the create table schema and data
GO /****** Object: Table [dbo].[MidrangeOtherSourceControl] Script Date: 06/03/2015 18:13:15 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[MidrangeOtherSourceControl]( [Req_ID] [float] NULL, [Service_Name] [nvarchar](255) NULL,
I have a SQL Agent job that runs at 4:15 in the morning. The job has 5 steps, each step only runs if the preceding step succeeds. The second step, which calls an SSIS package that does the main processing, appears to finish as it goes on to the next step; however, when looking in 'View History' there are 2 entries for this step - the first one shows it as still running (Circled Green Arrow) but with a start and end time. The second entry says the job succeeded.
I have been seeing conflicts, such as deadlocks, with later jobs. I suspect this job is causing the conflicts - maybe the package is still running in the background instead of having actually completed?
what conditions a job step my be showing in the job history as both running AND completed successfully?
Hello, I have a Question/doubt on SqlDependency.Start/SqlDependency.Stop.
After the implementation of my solution the question sounds "stupid" ... maybe is only the stress due to the fact that I'm going to deploy the application on Test.
Anyway.. I developed this application (windows application) that uses query Notification features to subscribe and get notification from Sql Server 2005 so it use the tipical pattern: SqlDependency.Start, SqlDependency_OnChange,SqlDependency.Stop.
This is application is installed on several client so actually I get have several notifications running on the Server.
When one of the client exit the application and call SqlDependency.Stop the service, queue and procedure are dropped.
Does the command drops all the query notification' service, queue and procedure running on the instance or only the one created by the specific user?
