Scenario
In our replication scheme, we replicate several tables, including a table photosthat contains binary image data. All other tables are repeated as expected, but the photo table does not work. I suspect that this is due to the large amount of data in the photo table, or perhaps because the image data is a field varbinary. However, using smaller fields varbinarydid not help.
Configuration information
The following is the configuration information:
- Each image can be anywhere from 65-120 Kb
- The version and the approved copy are saved along with the thumbnails, so one line may be close to ~ 800 KB
- I once had problems with the configuration field
max text repl size, but I set this max value with sp_configureandreconfigure with override - Photos are filtered based on the "published" field, but like other worksheets
- Databases use the same local db server (in development environment) and are configured for transactional replication
- Replicated database uses push subscription
In addition, I noticed that sometimes regenerating a snapshot and reinitializing a subscription causes image replication. With this in mind, I configured the snapshot agent to regenerate the snapshot every minute or so for debugging purposes (obviously this is an excess for the work environment). However, this did not help.
Question
, photos , ? ? , ?
SQL Server Profiler , . . , .
SQL Server 2005 3 (SP3) Windows Server 2003 2 (SP2).
[]
, . , . IIS , .