Why on earth would you use data type FLOAT ????  ( especially if smallint / tinyint ) would do !

Does it hold blobs ? ( of tables that reside in other filegroups TEXTIMAGE_ON yourtroubledfilegroup)

or indexes of tables/views that reside in other filegroups ?

• This reply was modified 2 years, 10 months ago by Johan Bijnens.

Generate your test code:

Select 'DECLARE @test VARCHAR(5) = ''€'';
SELECT convert(char(100),'''+name+''' ) AS DBCollation, @test collate ' + name + ' AS VarcharText;
GO
' SelectQueries
from fn_helpcollations()
where name like '%latin%'
order...

have a look at "SET options"

have a read at: "Encrypt a Column of Data"

Great example on how naming variables ( etc ) can be confusing and lead you totally out of focus

removed - you're talking SSIS ( I assumed SQL DB engine )

Sorry, Johan... I'm not sure how to take that.  To be sure, it wasn't meant as an insult to anyone (especially you).  You hit the nail on...

indeed, Jeff

what security context did you use when you created the linked server?

This is what my test uses. The account is dbo in my case.

btw I prefer...

sys.dm_io_virtual_file_stats returns data since last startup of SQLServer.

To get what you aim for, you should persist its data yourself.

By itself that data means nothing at all.

It's only use is...

I suspect this may be an OP spam post ....

What are you trying to accomplish?

Why should a UDF be able to handle that?

Check "Valid statements in a function"

Here is what I use:

-- Deadlock information analysis
Declare @Debug bit 
Set @Debug = 1 
Set @Debug = 0

Declare @waitresource varchar(128) 
set @waitresource = 'KEY: 7:72057600361103360 (97e5c9409bc8)'
set @waitresource...

your varchar(4000) consumes as much space as your varchar(19) !

That's the whole point of data type varchar !

Do NOT store date/time/datetime date in (var)char columns !

Always use the correct data...