Eamon,

Yes, it is rolling back the transaction. Check if the table is indexed......the rollback will take much longer if so..

If the job is running over a network rather than...

There is also a stored procedure...

sp_helpindex tablename

On a more optimistic note, technology usually catches up, biofuels are not a realistic alternative option to oil now because of the land area which would be needed to grow...

Hi

Yes

You can use this from SQL Query Analyzer...

use master

BACKUP LOG YOUR_DATABASE_NAME WITH TRUNCATE_ONLY

use YOUR_DATABASE_NAME

dbcc shrinkfile (YOUR_LOG_NAME, 0)

Its a good idea to take a backup first...

Hi

Are you scheduling the job from Sql Server Agent, you could check the job history there,  or run this query from Query Analyzer to find the problem....

USE MSDB

select  j.name as 'Name',...

You could also use these SQL Server stored procedures....

to check space on disk....

execute master..usp_diskspace

to check database sizes.....

sp_helpdb

The above error message caused by problem with your connection string....does not recognize server name.....

Why dont you create a DTS Job in SQL Enterpise Manager to load the data and...

Try this procedure, best to run on master database...

CREATE PROCEDURE usp_diskspace  

AS 

SET NOCOUNT ON 

DECLARE @hr int 

DECLARE @fso int 

DECLARE @drive char(1) 

DECLARE @odrive int ...

You could also create a batch file in DOS and call it from scheduled tasks, in this batch file add the date to the file name and copy it to...

I noticed that too and discovered its just the way SQL Server with SP4 reports Latch waits on a process, its nothing to worry about Check out this page for...

PS I borrowed part of this CODE somewhere on this site so if anyone recognizes it thanks very much!!

I have a job running in SQL Server Agent which does this, uses sysprocesses and DBCC INPUTBUFFER, I tried SQL Trace and a few other approaches, mostly 6 of one...

Its also worth adding what tables are used in the code in the comment header ...e.g. .....

-- TABLES REFERENCED - SERVER.DATABASE.DBO.TABLE1

-- ...

Why dont you create a table of your own, and insert the sysprocesses data into it adding a getdate() field, and create a job in Sql Server Agent to run...

You could also call a BCP command using the exec master..xp_cmdshell from within a procedure and pass the file names to it.....something along these lines....

e.g.

declare @sql varchar(512), @filename varchar(50)

--...