How can we help you today? How can we help you today?
laker_42
Activity overview Badges (0) Posts (14) Comments (19)

Comments

Sort by recent activity
We have around 30 jobs on this server... / comments
  1. Community
  2. SQL Response v1 RC
  3. long running query
We have around 30 jobs on this server...
0 votes
Nigel, this is a little embarrasing but it returned 135548 rows in about 2 minutes. THere was almost 6 months worth of job history kept! That has been slimmed down so I guess this shouldn't show up as a long running query again. Thanks for following up on this. John / comments
  1. Community
  2. SQL Response v1 RC
  3. long running query
Nigel, this is a little embarrasing but it returned 135548 rows in about 2 minutes. THere was almost 6 months worth of job history kept! That has been slimmed down so I guess this shouldn't show ...
0 votes
I guess you are correct. So the tool should be executing short running queries to gather its info as opposed to connecting up and sit there as an open process continually running? Here is what the tool was executing: CREATE PROCEDURE sp_help_jobhistory_full @job_id UNIQUEIDENTIFIER, @job_name sysname, @step_id INT, @sql_message_id INT, @sql_severity INT, @start_run_date INT, @end_run_date INT, @start_run_time INT, @end_run_time INT, @minimum_run_duration INT, @run_status INT, @minimum_retries INT, @oldest_first INT, @server sysname, @mode VARCHAR(7), @order_by INT, @distributed_job_history BIT AS IF(@distributed_job_history = 1) SELECT null as instance_id, sj.job_id, job_name = sj.name, null as step_id, null as step_name, null as sql_message_id, null as sql_severity, sjh.last_outcome_message as message, sjh.last_run_outcome as run_status, sjh.last_run_date as run_date, sjh.last_run_time as run_time, sjh.last_run_duration as run_duration, null as operator_emailed, null as operator_netsentname, null as operator_paged, null as retries_attempted, sts.server_name as server FROM msdb.dbo.sysjobservers sjh JOIN msdb.dbo.systargetservers sts ON (sts.server_id = sjh.server_id) JOIN msdb.dbo.sysjobs_view sj ON(sj.job_id = sjh.job_id) WHERE (@job_id = sjh.job_id) AND ((@start_run_date IS NULL) OR (sjh.last_run_date >= @start_run_date)) AND ((@end_run_date IS NULL) OR (sjh.last_run_date <= @end_run_date)) AND ((@start_run_time IS NULL) OR (sjh.last_run_time >= @start_run_time)) AND ((@minimum_run_duration IS NULL) OR (sjh.last_run_duration >= @minimum_run_duration)) AND ((@run_status IS NULL) OR (@run_status = sjh.last_run_outcome)) AND ((@server IS NULL) OR (sts.server_name = @server)) ELSE SELECT sjh.instance_id, -- This is included just for ordering purposes sj.job_id, job_name = sj.name, sjh.step_id, sjh.step_name, sjh.sql_message_id, sjh.sql_severity, sjh.message, sjh.run_status, sjh.run_date, sjh.run_time, sjh.run_duration, operator_emailed = so1.name, operator_netsent = so2.name, operator_paged = so3.name, sjh.retries_attempted, sjh.server FROM msdb.dbo.sysjobhistory sjh LEFT OUTER JOIN msdb.dbo.sysoperators so1 ON (sjh.operator_id_emailed = so1.id) LEFT OUTER JOIN msdb.dbo.sysoperators so2 ON (sjh.operator_id_netsent = so2.id) LEFT OUTER JOIN msdb.dbo.sysoperators so3 ON (sjh.operator_id_paged = so3.id), msdb.dbo.sysjobs_view sj WHERE (sj.job_id = sjh.job_id) AND ((@job_id IS NULL) OR (@job_id = sjh.job_id)) AND ((@step_id IS NULL) OR (@step_id = sjh.step_id)) AND ((@sql_message_id IS NULL) OR (@sql_message_id = sjh.sql_message_id)) AND ((@sql_severity IS NULL) OR (@sql_severity = sjh.sql_severity)) AND ((@start_run_date IS NULL) OR (sjh.run_date >= @start_run_date)) AND ((@end_run_date IS NULL) OR (sjh.run_date <= @end_run_date)) AND ((@start_run_time IS NULL) OR (sjh.run_time >= @start_run_time)) AND ((@end_run_time IS NULL) OR (sjh.run_time <= @end_run_time)) AND ((@minimum_run_duration IS NULL) OR (sjh.run_duration >= @minimum_run_duration)) AND ((@run_status IS NULL) OR (@run_status = sjh.run_status)) AND ((@minimum_retries IS NULL) OR (sjh.retries_attempted >= @minimum_retries)) AND ((@server IS NULL) OR (sjh.server = @server)) ORDER BY (sjh.instance_id * @order_by) / comments
  1. Community
  2. SQL Response v1 RC
  3. long running query
I guess you are correct. So the tool should be executing short running queries to gather its info as opposed to connecting up and sit there as an open process continually running? Here is what the...
0 votes
I want to use the force column order option, correct? Is there a way to set this option globally so every new comparison project will have this option checked? I guess I should have done a little more homework before posting! :oops: John / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Feature or a bug?
I want to use the force column order option, correct? Is there a way to set this option globally so every new comparison project will have this option checked? I guess I should have done a little ...
0 votes
Hi James, Thanks for the response. For us, we have a central backup location that all servers have access to. We also standardize on all servers running under the same service account. Also, the dba would be restoring the databases & he has admin access to all the SQL servers so security should not be an issue. However, I understand we may not be the norm. John / comments
  1. Community
  2. SQL Backup 5 Beta
  3. Feature Request
Hi James, Thanks for the response. For us, we have a central backup location that all servers have access to. We also standardize on all servers running under the same service account. Also, the d...
0 votes
Brian, Thanks for the suggestion for the environment variable. That will be very handy. It would still be nice to have the last 2 features: laker_42 wrote: It would be nice if the tool would still present me with the results of the tables that were successfully compared as opposed to forcing me to start all over again with all of the table compares. As I am doing right now. I have to wait another hour or so to get the tables that I do have space for & were already done during the first compare that cancelled. This would be nice for the actual synchronization of the data. If one cancels, only rollback the table changes for the cancelled operation not all of the table changes that were successful. / comments
  1. Community
  2. SQL Data Compare Previous Versions
  3. feature request
Brian, Thanks for the suggestion for the environment variable. That will be very handy. It would still be nice to have the last 2 features: laker_42 wrote: It would be nice if the tool would sti...
0 votes
David, I will try that option to see how it works. Thanks! John / comments
  1. Community
  2. SQL Data Compare Previous Versions
  3. feature request
David, I will try that option to see how it works. Thanks! John
0 votes
Cool, thanks! It will be nice to have that fixed. / comments
  1. Community
  2. SQL Prompt 2
  3. Case Sensitive?
Cool, thanks! It will be nice to have that fixed.
0 votes
Thanks Dom! That clears it up. John / comments
  1. Community
  2. SQL Prompt 2
  3. What does Free until September 1 mean?
Thanks Dom! That clears it up. John
0 votes
If I start to type an objects name & then hit ctl-space to bring up the available objects, it enters a space & then brings up the entire list. Am I missing an option here? This did work in v 1.4. John / comments
  1. Community
  2. SQL Prompt 2.0 Beta
  3. Initial Feedback and bugs I noticed
If I start to type an objects name & then hit ctl-space to bring up the available objects, it enters a space & then brings up the entire list. Am I missing an option here? This did work in v 1.4....
0 votes
Total activity
46
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
13