Image Error In SQL

I have a seperate table that holds employees pictures in it and for some reason I am getting an error all the sudden when I try to insert a picture. I never got that before.. Can anyone help please??It would appear that your image size has grown roughly eight times what it was (or you've added replication, or possibly you changed to a new SQL Server).

The fix is easy, but PLEASE think about this before you make the change... This can have relatively far reaching implications to replication performance.

The problem is the default size limit for replicated data. Your machine appears to have the default setting of 65536 bytes per replicated column. This only affects TEXT and IMAGE columns, since nothing else can be large enough to have problems with that setting. IF you decide to change this setting, the code snippet you need is:EXECUTE sp_configure 'max text repl size (B)', 655360 -- or pick another size to suit you-PatP|||I had forgotten that our techs are moving SQL server and our scanned documents over to its own server and one of the databases I created is there.

Ok Now I understand thank you again

IIS and SQL 2005

I need to have my web server IIS 6 access our database SQL2005. Our web
server holds other web sites so I would like to leave it in the DMZ and the
SQL in the lan. From what I have heard this is not the best method. Has
anyone done this. Is there a better way.
ThanksHello royst,

> I need to have my web server IIS 6 access our database SQL2005. Our
> web server holds other web sites so I would like to leave it in the
> DMZ and the SQL in the lan. From what I have heard this is not the
> best method. Has anyone done this. Is there a better way.
Sometimes is design is about the only secure method making it work. The prob
lem
with it is that its lower perf that having the SQL Server in DMZ because
of need to connect back through a firewall. You may also have to use standar
d
logins, but as long as you're taking reasonable steps to secure your DMZ
to LAN connection, that's probably an acceptable risk.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Thanks Kent
The performance is not an issue. Security on the other hand is. I have
reservations on opening up SQL ports on my firewall. Just tring to find a
more secure way to do this with IIS in the DMZ and SQL in the local Lan.
"Kent Tegels" wrote:

> Hello royst,
>
> Sometimes is design is about the only secure method making it work. The pr
oblem
> with it is that its lower perf that having the SQL Server in DMZ because
> of need to connect back through a firewall. You may also have to use stand
ard
> logins, but as long as you're taking reasonable steps to secure your DMZ
> to LAN connection, that's probably an acceptable risk.
> Thanks!
> Kent Tegels
> DevelopMentor
> http://staff.develop.com/ktegels/
>
>|||Hello royst,
If you have a decent firewall, you should be able to restrict by address
who can initiate a connection on port 1433. You could also require TLS or
SSL encryption on the connection for good measure with with performance impl
ications.
The alternative would be do some form of replication, but that leaves you
with a port (or set of them) open at some point.
Good luck,
kt