varbinary (max) would automatically limit them to 2 GB size, but your best
bet might be to check the size on the client side if you want to limit them
to say 10 MB or something. If you send it to the server first, someone
might have just spent all that time uploading a 100 MB file only to have it
error on them. That's a waste of time and bandwidth. If you want to ensure
that, for instance, your developers can't work their way around the system
and bypass the client app to insert larger files you might look into
triggers as well.
"Earl" <br******@newsgroups.nospamwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
Looking for an idea here. I've got a .Net app connecting to SQL2005 where
I allow users to add pictures to the database. But I don't want them
adding gigantic images, so I'm looking for an idea on how to control how
big of an image they might add. I'm not interested in simply saving a
pointer to a file here.