Im pretty sure that it is due to the fact that the view (as a general rule) doesn't retain the data and has to go get it everytime a request...

Why not set the Recovery model = SIMPLE, SELECT INTO a "temp" table the data you want to keep, TRUNCATE the "real" table and then INSERT the data back?  After...

Try CAST(SUM(FileSize)) AS BIGINT) MB,  CAST(SUM(FileSize)/1000 AS BIGINT) GB

Another way:

DECLARE @Date CHAR(8)

SET @Date = '06102004'

SELECT

CONVERT(VARCHAR(10), CAST(RIGHT(@Date, 4) + '-' +

  LEFT(@Date, 2) + '-' + SUBSTRING(@Date, 3, 2) AS DATETIME), 104)

What about...

SELECT TOP 1 * FROM [LinkedServer1].DB.Owner.Table

IF @@ERROR <> 0

  BEGIN

    -- Log error stating Server1 failed

END

Repeat as needed??

EXEC sp_changeobjectowner 'you.test', 'dbo'

or

EXEC sp_changeobjectowner 'test', 'dbo'

SELECT * FROM tblTest WHERE ColC IS NOT NULL

I would check the collation of the database and the table and ensure that it is set to a collation that would give you the proper DATETIME format.

I would also...

Not to my knowledge.  However, the database(s) will be created initially as the same size of the model database.  This should help you "guess"

This is possible.  However, instead of a trigger sending e-mail why not have the trigger send information to a send-email table and the last step in the package will be...

Just to add to what Kenneth has said (which is VERY good)...  TRIGGERS may LOCK the table and STOP ALL ACTIVITY on the table until they are DONE.

This means that...

Another thing you could do is :

WHERE ISNULL(address_name, '') LIKE 'M%'.

This would also eliminate NULL values

SELECT CHARINDEX('|', '80339inesh|80339:dinesh badgujar|80339:dinesh badgujar')

SELECT PATINDEX('%|%', '80339inesh|80339:dinesh badgujar|80339:dinesh badgujar')

Depending on how you wrote your application will determine that unfortunately....

I would port the data to SQL and after manually fixing the keys, indexes etc. (unfortunately these are not upsizable)...

Ok.  Sounds like you need to do the following ADD:

HAVING COUNT(AssociateID) = [the number of different role IDs you are looking for].

This would ONLY pull back associates that have the...