![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Besides the default SQL 2005 trace comes with the box, I enabled SQL profiler tracing with a stored procedure. And the trace files size was set to 25GB; however, I noticed the trace has been terminated when it hit 4GB and shouted out error in sql server log that there is not enough space on the disk and restart the trace after correcting the problem. but my drive still have 86GB free space. Are there something else set the file size limit besides what's the book online mentioned an upper limit of 1 gigabyte (GB) for the maximum file size option and default maximum file size is 5 megabytes (MB)? |
#3
| |||
| |||
|
|
xo (xo555... (AT) gmail (DOT) com) writes: Besides the default SQL 2005 trace comes with the box, I enabled SQL profiler tracing with a stored procedure. *And the trace files size was set to 25GB; however, I noticed the trace has been terminated when it hit 4GB and shouted out error in sql server log that there is not enough space on the disk and restart the trace after correcting the problem. but my drive still have 86GB free space. Are there something else set the file size limit besides what's the book online mentioned an upper limit of 1 gigabyte (GB) for the maximum file size option and default maximum file size is 5 megabytes (MB)? So you started a trace from Profiler, and asked for to be saved to disk? That's not a good idea. Profiler is good for short monitoring, but longer traces you should run server-side. These are actually not difficult to set up. Use Profiler, and you might try for a short while to see that they look good. Then you can select the Export option from the File menu to get a script. In the script you can set the maximum file size. -- Erland Sommarskog, SQL Server MVP, esq... (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000:http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#4
| |||
| |||
|
|
The trace only set to run for a short duration each day. And I did get a script and changed the max file size and scheduled the trace. But for some reasons, the trace file still only goes up to 4.2GB. |
#5
| |||
| |||
|
|
xo (xo555... (AT) gmail (DOT) com) writes: Besides the default SQL 2005 trace comes with the box, I enabled SQL profiler tracing with a stored procedure. And the trace files size was set to 25GB; however, I noticed the trace has been terminated when it hit 4GB and shouted out error in sql server log that there is not enough space on the disk and restart the trace after correcting the problem. but my drive still have 86GB free space. Are there something else set the file size limit besides what's the book online mentioned an upper limit of 1 gigabyte (GB) for the maximum file size option and default maximum file size is 5 megabytes (MB)? |
#6
| |||
| |||
|
|
"xo" <xo555... (AT) gmail (DOT) com> a écrit dans le message de news: 01eca383-df41-45b3-b72e-deb2e1371... (AT) n19g2000prf (DOT) googlegroups.com... On Aug 18, 2:25 pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote: xo (xo555... (AT) gmail (DOT) com) writes: Besides the default SQL 2005 trace comes with the box, I enabled SQL profiler tracing with a stored procedure. And the trace files size was set to 25GB; however, I noticed the trace has been terminated when it hit 4GB and shouted out error in sql server log that there is not enough space on the disk and restart the trace after correcting the problem. but my drive still have 86GB free space. Are there something else set the file size limit besides what's the book online mentioned an upper limit of 1 gigabyte (GB) for the maximum file size option and default maximum file size is 5 megabytes (MB)? Hi, Are you on a FAT32 file system The max file size is 4GB on FAT32 |
![]() |
| Thread Tools | |
| Display Modes | |
| |