Are you getting a specific error message? It may be your database specific configuration that limits packet size for SQL server.

Thanks, Chillax, I think there is no such limits for the 8k. Those tables are generated by Mantis. I could upload huge files to other tables.
Could you adivse how to remove the limits if there are?

Here is the error msg:

Database query failed. Error received from database was 0000206: Operand type clash: text is incompatible with image for the query: INSERT INTO mantis_bug_file_table
(bug_id, title, description, diskfile, filename, folder, filesize, file_type, date_added, content)
VALUES
(6, '', '', 'tmp2\afeeeae6d83d891dc4bf2b7670674c2b', 'Architecture Design.Very Useful Tips.doc', 'tmp2\', 67584, 'application/msword', '2006-05-26 04:58:04PM', 'ÐÏ .................

DISCLAIMER:
I don't use SQL Server, but a google search turned up this:

The easiest way to view your SQL Server's configuration settings is to run the following command in Query Analyzer:

sp_configure

SOURCE: http://www.sql-server-performance.com/sql_server_configuration_settings.asp

I would look into finding something that might be a size limit for inserts and increase it accordingly.

Additionally, you might consider changing your file storage type from database to disk.

Thank you very much,

I checked all of the configurations I could fine, they all look fine.

I think there may be something wrong the M$-SQL configuration, or Mantis persistence on M$-SQL.

If I change this

 # Upload destination: specify actual location in project settings
 # DISK, DATABASE, or FTP.
 $g_file_upload_method    = DATABASE; 

to be:
$g_file_upload_method = DISK;

I could upload files greater than 1M. The only problem is I can not insert the file into the image column.

Here is my configuration:

Name Min Max config_value run_value
affinity mask -2147483648 2147483647 0 0
allow updates 0 1 0 0
awe enabled 0 1 0 0
c2 audit mode 0 1 0 0
cost threshold for parallelism 0 32767 5 5
Cross DB Ownership Chaining 0 1 0 0
cursor threshold -1 2147483647 -1 -1
default full-text language 0 2147483647 1033 1033
default language 0 9999 0 0
fill factor (%) 0 100 0 0
index create memory (KB) 704 2147483647 0 0
lightweight pooling 0 1 0 0
locks 5000 2147483647 0 0
max degree of parallelism 0 32 0 0
max server memory (MB) 4 2147483647 2147483647 2147483647
max text repl size (B) 0 2147483647 65536 65536
max worker threads 32 32767 255 255
media retention 0 365 0 0
min memory per query (KB) 512 2147483647 1024 1024
min server memory (MB) 0 2147483647 0 0
nested triggers 0 1 1 1
network packet size (B) 512 32767 4096 4096
open objects 0 2147483647 0 0
priority boost 0 1 0 0
query governor cost limit 0 2147483647 0 0
query wait (s) -1 2147483647 -1 -1
recovery interval (min) 0 32767 0 0
remote access 0 1 1 1
remote login timeout (s) 0 2147483647 20 20
remote proc trans 0 1 0 0
remote query timeout (s) 0 2147483647 600 600
scan for startup procs 0 1 0 0
set working set size 0 1 0 0
show advanced options 0 1 1 1
two digit year cutoff 1753 9999 2049 2049
user connections 0 32767 0 0
user options 0 32767 0 0

I think this is also a duplicate to 0006063. With my hackish fix from there I'm able to upload files of all sorts, with no size limitation other than what I set.

Fixes for uploading files have been included in 1.1.0a4.

Note, you may need to set mssql php settings:

mssql.textsize = 2147483647
mssql.textlimit = 2147483647

MantisBT currently supports Mysql and has support for other database engines.

The support for other databases is known to be problematic.

Having implemented the current database layer into Mantis 10 years ago, I'm currently working on replacing the current layer.

If you are interested in using Mantis with non-mysql databases - for example, Oracle, PGSQL or MSSQL, and would be willing to help out testing the new database layer, please drop me an email at paul@mantisforge.org

In the meantime, I'd advise running Mantis with Mysql Only to avoid issues.

Thanks
Paul