I also believe that truncation doesn't cause the package failure. I think there is a threshold as how many errors can happen and probably in your case the threshold is...

Hey Roy,

I also thought the same thing but when I run the snapshot this started creating the files even for the tables which already existed. I just executed the snapshot...

Cost Analysis Among EXISTS (SELECT 1), EXISTS (SELECT COUNT(1)), EXISTS (SELECT *) AND EXISTS (SELECT TOP 1) should help

-lucky

MS Sql Server Installation Make Easy should help

-lucky

How to find the path where the SQL server errorlog file is located?

- lucky

Thanks Everyone here. I shall prefer litespeed in my env.

Litespeed Link really helped.

Thanks for the post, Michael.

-lucky

MS SQL Corruption: "Msg 2627 - Violation of PRIMARY KEY constraint"

-Lucky

I like following thread for Resolving Full Log Esp in Simple Recovery Mode and then click on Link

-lucky

Same happened with me some days back. I executed my query and found that some records have the date column NULL. Use SSRSLink to get some other info as well.

lucky

Try

INSERT INTO [Details] ([Location]) VALUES N''@Location

or

INSERT INTO [Details] ([Location]) VALUES N'@Location

one of the above should resolve ur problem

-Lk

TRUNCATE_ONLY is gone in 2008. The logs would be truncated only and only when you take the backups. So be ready to have your backup jobs monitored all the time.

TRY THIS

select * from sys.syscolumns

where length IN (16,8000,-1)

try to use @file_attachments.

What is the size of the file. Default size is 1 MB. U need to change some conf settings if ur file size is > 1 MB.

-Lucky

Ur solution:

SELECT emp.empno,emp.empname,tmp.Dept ,emp.SAL

FROM empdtls emp

INNER JOIN

(SELECT Max(Sal) Salary, Dept

FROM Empdtls

Group by Dept)tmp

ON tmp.dept = emp.dept

WHERE Salary = emp.Sal

order by tmp.Dept

Create table and insert data using following query:

CREATE TABLE EmpDtls(empno...