Impact of transaction log backups in synchronous DB Mirroring syst

Hello,
We have a site on SQL Server 2005 SP2 EE. They are using synchronous
database mirroring. Both the principal and mirror are on a fast LAN. When
they perform transaction log backups on the principal database, our
application that accesses the principal database freezes for 1 or 2 seconds.
The transaction log backups are being written to the same disk where the
database resides. They have tried reducing the frequency of the transaciton
log backups to every 10 minutes, and that reduced the length of the app
freeze, but did not eliminate it. Has anyone heard of a problem running
transaction log backups when the database is mirrored?
Thanks,
Heather
I would be more concerned as to the placement of the log backups. Why would
you write them to the same disk that hold the data files? This is definitely
a candidate for a performance hit not to mention a problem if the disk
itself crashes. You loose both the data and logs and are probably in line to
update the resume. If you saturate the I/O the db can appear to freeze.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"HeatherK" <HeatherK@.community.nospam> wrote in message
news:E6A9E23D-916B-4CEE-8C3F-8801CD3394EB@.microsoft.com...
> Hello,
> We have a site on SQL Server 2005 SP2 EE. They are using synchronous
> database mirroring. Both the principal and mirror are on a fast LAN. When
> they perform transaction log backups on the principal database, our
> application that accesses the principal database freezes for 1 or 2
> seconds.
> The transaction log backups are being written to the same disk where the
> database resides. They have tried reducing the frequency of the
> transaciton
> log backups to every 10 minutes, and that reduced the length of the app
> freeze, but did not eliminate it. Has anyone heard of a problem running
> transaction log backups when the database is mirrored?
> Thanks,
> Heather
|||Hi Andrew,
Thanks for your post.
Yes, we realize that the placement of the backup files is not optimal. They
are using RAID5 on the drive, so they should be protected from a disk crash.
We realize RAID 5 is not optimal for performance, but that is what they have.
We have not seen a problem with transaction log backups at our other sites
that are not using Database Mirroring. That is why we were wondering if
there were any known issues with taking transaction log backups when you are
using synchronous Database Mirroring.
We will gather more performance metrics to determine if this is strictly
related to I/O or if there is a connection with Database Mirroring.
Thanks,
Heather
"Andrew J. Kelly" wrote:

> I would be more concerned as to the placement of the log backups. Why would
> you write them to the same disk that hold the data files? This is definitely
> a candidate for a performance hit not to mention a problem if the disk
> itself crashes. You loose both the data and logs and are probably in line to
> update the resume. If you saturate the I/O the db can appear to freeze.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "HeatherK" <HeatherK@.community.nospam> wrote in message
> news:E6A9E23D-916B-4CEE-8C3F-8801CD3394EB@.microsoft.com...
>
|||Well mirroring does add overhead and potentially even a little more I/O on
the drive with the logs so I am sure it adds to the whole mess. Doing a log
backup also forces a checkpoint which is I/O intensive as well. What do the
perfmon counters and virtual file statsw say for that drive and the log
files? And by the way you should never count on the fact that it is Raid 5
to avert a crash. They would be better off copying the files to a network
share.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"HeatherK" <HeatherK@.community.nospam> wrote in message
news:C0FB6FB3-9661-4BAA-84D2-17AC2B7C1A6F@.microsoft.com...[vbcol=seagreen]
> Hi Andrew,
> Thanks for your post.
> Yes, we realize that the placement of the backup files is not optimal.
> They
> are using RAID5 on the drive, so they should be protected from a disk
> crash.
> We realize RAID 5 is not optimal for performance, but that is what they
> have.
> We have not seen a problem with transaction log backups at our other sites
> that are not using Database Mirroring. That is why we were wondering if
> there were any known issues with taking transaction log backups when you
> are
> using synchronous Database Mirroring.
> We will gather more performance metrics to determine if this is strictly
> related to I/O or if there is a connection with Database Mirroring.
> Thanks,
> Heather
> "Andrew J. Kelly" wrote:

Impact of transaction log backups in synchronous DB Mirroring syst

Hello,
We have a site on SQL Server 2005 SP2 EE. They are using synchronous
database mirroring. Both the principal and mirror are on a fast LAN. When
they perform transaction log backups on the principal database, our
application that accesses the principal database freezes for 1 or 2 seconds.
The transaction log backups are being written to the same disk where the
database resides. They have tried reducing the frequency of the transaciton
log backups to every 10 minutes, and that reduced the length of the app
freeze, but did not eliminate it. Has anyone heard of a problem running
transaction log backups when the database is mirrored?
Thanks,
HeatherI would be more concerned as to the placement of the log backups. Why would
you write them to the same disk that hold the data files? This is definitely
a candidate for a performance hit not to mention a problem if the disk
itself crashes. You loose both the data and logs and are probably in line to
update the resume:). If you saturate the I/O the db can appear to freeze.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"HeatherK" <HeatherK@.community.nospam> wrote in message
news:E6A9E23D-916B-4CEE-8C3F-8801CD3394EB@.microsoft.com...
> Hello,
> We have a site on SQL Server 2005 SP2 EE. They are using synchronous
> database mirroring. Both the principal and mirror are on a fast LAN. When
> they perform transaction log backups on the principal database, our
> application that accesses the principal database freezes for 1 or 2
> seconds.
> The transaction log backups are being written to the same disk where the
> database resides. They have tried reducing the frequency of the
> transaciton
> log backups to every 10 minutes, and that reduced the length of the app
> freeze, but did not eliminate it. Has anyone heard of a problem running
> transaction log backups when the database is mirrored?
> Thanks,
> Heather|||Hi Andrew,
Thanks for your post.
Yes, we realize that the placement of the backup files is not optimal. They
are using RAID5 on the drive, so they should be protected from a disk crash.
We realize RAID 5 is not optimal for performance, but that is what they have.
We have not seen a problem with transaction log backups at our other sites
that are not using Database Mirroring. That is why we were wondering if
there were any known issues with taking transaction log backups when you are
using synchronous Database Mirroring.
We will gather more performance metrics to determine if this is strictly
related to I/O or if there is a connection with Database Mirroring.
Thanks,
Heather
"Andrew J. Kelly" wrote:
> I would be more concerned as to the placement of the log backups. Why would
> you write them to the same disk that hold the data files? This is definitely
> a candidate for a performance hit not to mention a problem if the disk
> itself crashes. You loose both the data and logs and are probably in line to
> update the resume:). If you saturate the I/O the db can appear to freeze.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "HeatherK" <HeatherK@.community.nospam> wrote in message
> news:E6A9E23D-916B-4CEE-8C3F-8801CD3394EB@.microsoft.com...
> > Hello,
> >
> > We have a site on SQL Server 2005 SP2 EE. They are using synchronous
> > database mirroring. Both the principal and mirror are on a fast LAN. When
> > they perform transaction log backups on the principal database, our
> > application that accesses the principal database freezes for 1 or 2
> > seconds.
> >
> > The transaction log backups are being written to the same disk where the
> > database resides. They have tried reducing the frequency of the
> > transaciton
> > log backups to every 10 minutes, and that reduced the length of the app
> > freeze, but did not eliminate it. Has anyone heard of a problem running
> > transaction log backups when the database is mirrored?
> >
> > Thanks,
> > Heather
>|||Well mirroring does add overhead and potentially even a little more I/O on
the drive with the logs so I am sure it adds to the whole mess. Doing a log
backup also forces a checkpoint which is I/O intensive as well. What do the
perfmon counters and virtual file statsw say for that drive and the log
files? And by the way you should never count on the fact that it is Raid 5
to avert a crash. They would be better off copying the files to a network
share.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"HeatherK" <HeatherK@.community.nospam> wrote in message
news:C0FB6FB3-9661-4BAA-84D2-17AC2B7C1A6F@.microsoft.com...
> Hi Andrew,
> Thanks for your post.
> Yes, we realize that the placement of the backup files is not optimal.
> They
> are using RAID5 on the drive, so they should be protected from a disk
> crash.
> We realize RAID 5 is not optimal for performance, but that is what they
> have.
> We have not seen a problem with transaction log backups at our other sites
> that are not using Database Mirroring. That is why we were wondering if
> there were any known issues with taking transaction log backups when you
> are
> using synchronous Database Mirroring.
> We will gather more performance metrics to determine if this is strictly
> related to I/O or if there is a connection with Database Mirroring.
> Thanks,
> Heather
> "Andrew J. Kelly" wrote:
>> I would be more concerned as to the placement of the log backups. Why
>> would
>> you write them to the same disk that hold the data files? This is
>> definitely
>> a candidate for a performance hit not to mention a problem if the disk
>> itself crashes. You loose both the data and logs and are probably in line
>> to
>> update the resume:). If you saturate the I/O the db can appear to
>> freeze.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "HeatherK" <HeatherK@.community.nospam> wrote in message
>> news:E6A9E23D-916B-4CEE-8C3F-8801CD3394EB@.microsoft.com...
>> > Hello,
>> >
>> > We have a site on SQL Server 2005 SP2 EE. They are using synchronous
>> > database mirroring. Both the principal and mirror are on a fast LAN.
>> > When
>> > they perform transaction log backups on the principal database, our
>> > application that accesses the principal database freezes for 1 or 2
>> > seconds.
>> >
>> > The transaction log backups are being written to the same disk where
>> > the
>> > database resides. They have tried reducing the frequency of the
>> > transaciton
>> > log backups to every 10 minutes, and that reduced the length of the app
>> > freeze, but did not eliminate it. Has anyone heard of a problem
>> > running
>> > transaction log backups when the database is mirrored?
>> >
>> > Thanks,
>> > Heather
>>sql

Impact of transaction log backups in synchronous DB Mirroring syst

Hello,
We have a site on SQL Server 2005 SP2 EE. They are using synchronous
database mirroring. Both the principal and mirror are on a fast LAN. When
they perform transaction log backups on the principal database, our
application that accesses the principal database freezes for 1 or 2 seconds.
The transaction log backups are being written to the same disk where the
database resides. They have tried reducing the frequency of the transaciton
log backups to every 10 minutes, and that reduced the length of the app
freeze, but did not eliminate it. Has anyone heard of a problem running
transaction log backups when the database is mirrored?
Thanks,
HeatherI would be more concerned as to the placement of the log backups. Why would
you write them to the same disk that hold the data files? This is definitely
a candidate for a performance hit not to mention a problem if the disk
itself crashes. You loose both the data and logs and are probably in line to
update the resume. If you saturate the I/O the db can appear to freeze.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"HeatherK" <HeatherK@.community.nospam> wrote in message
news:E6A9E23D-916B-4CEE-8C3F-8801CD3394EB@.microsoft.com...
> Hello,
> We have a site on SQL Server 2005 SP2 EE. They are using synchronous
> database mirroring. Both the principal and mirror are on a fast LAN. When
> they perform transaction log backups on the principal database, our
> application that accesses the principal database freezes for 1 or 2
> seconds.
> The transaction log backups are being written to the same disk where the
> database resides. They have tried reducing the frequency of the
> transaciton
> log backups to every 10 minutes, and that reduced the length of the app
> freeze, but did not eliminate it. Has anyone heard of a problem running
> transaction log backups when the database is mirrored?
> Thanks,
> Heather

Images and PDF Export POST SP2

I've come accross the same problem having also installed SP2. Still looking
for the answer.
I did notice that exporting via the preview window in Visual Studio works
perfectly. It's only exporting to pdf via a browser that causes the
scrambled images.
Does anyone have a work around, besides changing every report to read a png
image? We still need transparency.
Ryan
>On Follow Up.. this appears to be images other than JPEG's, which according
>to documentation are all rendered as PNG's.
>"Rob Johnson" wrote:
>> After installing RS SP2, images included in my reports display fine in
>> HTML
>> View, Excel View and TIFF View, but when exported to PDF they are not
>> displaying properly (they appear garbled, much like a scrambled TV
>> signal).
>>
>> Any ideas or thoughts?Same issue here, although my image is being converted at runtime to png via a
.Net assembly. I get the same results through the browser and VS IDE.
"Ryan Opfer" wrote:
> I've come accross the same problem having also installed SP2. Still looking
> for the answer.
> I did notice that exporting via the preview window in Visual Studio works
> perfectly. It's only exporting to pdf via a browser that causes the
> scrambled images.
> Does anyone have a work around, besides changing every report to read a png
> image? We still need transparency.
> Ryan
> >On Follow Up.. this appears to be images other than JPEG's, which according
> >to documentation are all rendered as PNG's.
> >"Rob Johnson" wrote:
> >> After installing RS SP2, images included in my reports display fine in
> >> HTML
> >> View, Excel View and TIFF View, but when exported to PDF they are not
> >> displaying properly (they appear garbled, much like a scrambled TV
> >> signal).
> >>
> >> Any ideas or thoughts?
>
>|||I use a custom centering/scaling function as the data source for my image
control. Converting the function's output to either GIF or JPEG eliminated
the problem for me. I have my image control's format set to JPEG. The
problem appears for me when the function's output is set to PNG.
"Ryan Opfer" wrote:
> I've come accross the same problem having also installed SP2. Still looking
> for the answer.
> I did notice that exporting via the preview window in Visual Studio works
> perfectly. It's only exporting to pdf via a browser that causes the
> scrambled images.
> Does anyone have a work around, besides changing every report to read a png
> image? We still need transparency.
> Ryan
> >On Follow Up.. this appears to be images other than JPEG's, which according
> >to documentation are all rendered as PNG's.
> >"Rob Johnson" wrote:
> >> After installing RS SP2, images included in my reports display fine in
> >> HTML
> >> View, Excel View and TIFF View, but when exported to PDF they are not
> >> displaying properly (they appear garbled, much like a scrambled TV
> >> signal).
> >>
> >> Any ideas or thoughts?
>
>|||I've tried a couple of images and didn't see PNG corruption when exporting
to PDF. Would one of you please email me a sample PNG that is exhibiting
this behavior so I can take a look? Thank you.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ken Fox" <KenFox@.discussions.microsoft.com> wrote in message
news:DF0704F5-B6DF-4BEF-A042-0DE8D7E0F30D@.microsoft.com...
>I use a custom centering/scaling function as the data source for my image
> control. Converting the function's output to either GIF or JPEG
> eliminated
> the problem for me. I have my image control's format set to JPEG. The
> problem appears for me when the function's output is set to PNG.
> "Ryan Opfer" wrote:
>> I've come accross the same problem having also installed SP2. Still
>> looking
>> for the answer.
>> I did notice that exporting via the preview window in Visual Studio works
>> perfectly. It's only exporting to pdf via a browser that causes the
>> scrambled images.
>> Does anyone have a work around, besides changing every report to read a
>> png
>> image? We still need transparency.
>> Ryan
>> >On Follow Up.. this appears to be images other than JPEG's, which
>> >according
>> >to documentation are all rendered as PNG's.
>> >"Rob Johnson" wrote:
>> >> After installing RS SP2, images included in my reports display fine in
>> >> HTML
>> >> View, Excel View and TIFF View, but when exported to PDF they are not
>> >> displaying properly (they appear garbled, much like a scrambled TV
>> >> signal).
>> >>
>> >> Any ideas or thoughts?
>>|||We don't currently support true color w/alpha PNG files, only indexed color
(color type 3). If your graphics editing program allows you to specify the
color type of your PNG and save it as a type 3 file you should be fine.
Prior to SP2, we converted all images to bitmaps which bloated the PDF file.
We now compress but have less flexibility on certain image types.
I've opened a bug for this issue so we can hopefully get it fixed in Yukon.
The easiest work-around for our SQL Server 2000 release is to save as a type
3 file or use a jpg.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:%23IailDwWFHA.3584@.TK2MSFTNGP14.phx.gbl...
> Thanks Donovan for looking into this. Here is our logo
> (logoRenderedFromBrowser.png). It was originally a GIF image but when
> rendered to the browser it becomes a png image (perhaps a reason why we
> can export to PDF via visual studio but not from the browser). Also
> attached is the scrambled logo (scrambledImage.jpg) screen shot taken
> directly after export to pdf via the browser.
> Again, prior to SP2 all reports exported as expected via the browser to
> pdf. One can only assume that there's been a change with sp2.
> Thanks in advance,
> Ryan
>
> "Donovan Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
> news:%23b0JjJnWFHA.2256@.TK2MSFTNGP14.phx.gbl...
>> I've tried a couple of images and didn't see PNG corruption when
>> exporting
>> to PDF. Would one of you please email me a sample PNG that is exhibiting
>> this behavior so I can take a look? Thank you.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ken Fox" <KenFox@.discussions.microsoft.com> wrote in message
>> news:DF0704F5-B6DF-4BEF-A042-0DE8D7E0F30D@.microsoft.com...
>>I use a custom centering/scaling function as the data source for my image
>> control. Converting the function's output to either GIF or JPEG
>> eliminated
>> the problem for me. I have my image control's format set to JPEG. The
>> problem appears for me when the function's output is set to PNG.
>> "Ryan Opfer" wrote:
>> I've come accross the same problem having also installed SP2. Still
>> looking
>> for the answer.
>> I did notice that exporting via the preview window in Visual Studio
>> works
>> perfectly. It's only exporting to pdf via a browser that causes the
>> scrambled images.
>> Does anyone have a work around, besides changing every report to read a
>> png
>> image? We still need transparency.
>> Ryan
>> >On Follow Up.. this appears to be images other than JPEG's, which
>> >according
>> >to documentation are all rendered as PNG's.
>> >"Rob Johnson" wrote:
>> >> After installing RS SP2, images included in my reports display fine
>> >> in
>> >> HTML
>> >> View, Excel View and TIFF View, but when exported to PDF they are
>> >> not
>> >> displaying properly (they appear garbled, much like a scrambled TV
>> >> signal).
>> >>
>> >> Any ideas or thoughts?
>>
>>
>
>|||Thanks Donovan for the information. I was in error when I had said that we
were originally using a GIF image and that RS was converting it when
rendering for the browser. We are indeed using png files at 24 bit.
I did save the image as png-8 (which I assume is color type 3) which does
fix this problem--although it's lousy quality.
So thanks again for the solution/work around.
Ryan
It is interesting though that you mention that RS doesn't currently support
true color w/alpha PNG files. I'm not even using PNG, it's RS that is
converting it to
"Donovan Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
news:eXILSR1WFHA.3584@.TK2MSFTNGP14.phx.gbl...
> We don't currently support true color w/alpha PNG files, only indexed
> color (color type 3). If your graphics editing program allows you to
> specify the color type of your PNG and save it as a type 3 file you should
> be fine. Prior to SP2, we converted all images to bitmaps which bloated
> the PDF file. We now compress but have less flexibility on certain image
> types.
> I've opened a bug for this issue so we can hopefully get it fixed in
> Yukon. The easiest work-around for our SQL Server 2000 release is to save
> as a type 3 file or use a jpg.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> news:%23IailDwWFHA.3584@.TK2MSFTNGP14.phx.gbl...
>> Thanks Donovan for looking into this. Here is our logo
>> (logoRenderedFromBrowser.png). It was originally a GIF image but when
>> rendered to the browser it becomes a png image (perhaps a reason why we
>> can export to PDF via visual studio but not from the browser). Also
>> attached is the scrambled logo (scrambledImage.jpg) screen shot taken
>> directly after export to pdf via the browser.
>> Again, prior to SP2 all reports exported as expected via the browser to
>> pdf. One can only assume that there's been a change with sp2.
>> Thanks in advance,
>> Ryan
>>
>> "Donovan Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
>> news:%23b0JjJnWFHA.2256@.TK2MSFTNGP14.phx.gbl...
>> I've tried a couple of images and didn't see PNG corruption when
>> exporting
>> to PDF. Would one of you please email me a sample PNG that is
>> exhibiting
>> this behavior so I can take a look? Thank you.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ken Fox" <KenFox@.discussions.microsoft.com> wrote in message
>> news:DF0704F5-B6DF-4BEF-A042-0DE8D7E0F30D@.microsoft.com...
>>I use a custom centering/scaling function as the data source for my
>>image
>> control. Converting the function's output to either GIF or JPEG
>> eliminated
>> the problem for me. I have my image control's format set to JPEG. The
>> problem appears for me when the function's output is set to PNG.
>> "Ryan Opfer" wrote:
>> I've come accross the same problem having also installed SP2. Still
>> looking
>> for the answer.
>> I did notice that exporting via the preview window in Visual Studio
>> works
>> perfectly. It's only exporting to pdf via a browser that causes the
>> scrambled images.
>> Does anyone have a work around, besides changing every report to read
>> a
>> png
>> image? We still need transparency.
>> Ryan
>> >On Follow Up.. this appears to be images other than JPEG's, which
>> >according
>> >to documentation are all rendered as PNG's.
>> >"Rob Johnson" wrote:
>> >> After installing RS SP2, images included in my reports display fine
>> >> in
>> >> HTML
>> >> View, Excel View and TIFF View, but when exported to PDF they are
>> >> not
>> >> displaying properly (they appear garbled, much like a scrambled TV
>> >> signal).
>> >>
>> >> Any ideas or thoughts?
>>
>>
>>
>>
>|||Ah, OK. I couldn't quite understand the GIF part of your message. :)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:ep6g6EAXFHA.3348@.TK2MSFTNGP14.phx.gbl...
> Thanks Donovan for the information. I was in error when I had said that
> we were originally using a GIF image and that RS was converting it when
> rendering for the browser. We are indeed using png files at 24 bit.
> I did save the image as png-8 (which I assume is color type 3) which does
> fix this problem--although it's lousy quality.
> So thanks again for the solution/work around.
> Ryan
> It is interesting though that you mention that RS doesn't currently
> support true color w/alpha PNG files. I'm not even using PNG, it's RS
> that is converting it to
> "Donovan Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
> news:eXILSR1WFHA.3584@.TK2MSFTNGP14.phx.gbl...
>> We don't currently support true color w/alpha PNG files, only indexed
>> color (color type 3). If your graphics editing program allows you to
>> specify the color type of your PNG and save it as a type 3 file you
>> should be fine. Prior to SP2, we converted all images to bitmaps which
>> bloated the PDF file. We now compress but have less flexibility on
>> certain image types.
>> I've opened a bug for this issue so we can hopefully get it fixed in
>> Yukon. The easiest work-around for our SQL Server 2000 release is to save
>> as a type 3 file or use a jpg.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> news:%23IailDwWFHA.3584@.TK2MSFTNGP14.phx.gbl...
>> Thanks Donovan for looking into this. Here is our logo
>> (logoRenderedFromBrowser.png). It was originally a GIF image but when
>> rendered to the browser it becomes a png image (perhaps a reason why we
>> can export to PDF via visual studio but not from the browser). Also
>> attached is the scrambled logo (scrambledImage.jpg) screen shot taken
>> directly after export to pdf via the browser.
>> Again, prior to SP2 all reports exported as expected via the browser to
>> pdf. One can only assume that there's been a change with sp2.
>> Thanks in advance,
>> Ryan
>>
>> "Donovan Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
>> news:%23b0JjJnWFHA.2256@.TK2MSFTNGP14.phx.gbl...
>> I've tried a couple of images and didn't see PNG corruption when
>> exporting
>> to PDF. Would one of you please email me a sample PNG that is
>> exhibiting
>> this behavior so I can take a look? Thank you.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ken Fox" <KenFox@.discussions.microsoft.com> wrote in message
>> news:DF0704F5-B6DF-4BEF-A042-0DE8D7E0F30D@.microsoft.com...
>>I use a custom centering/scaling function as the data source for my
>>image
>> control. Converting the function's output to either GIF or JPEG
>> eliminated
>> the problem for me. I have my image control's format set to JPEG.
>> The
>> problem appears for me when the function's output is set to PNG.
>> "Ryan Opfer" wrote:
>> I've come accross the same problem having also installed SP2. Still
>> looking
>> for the answer.
>> I did notice that exporting via the preview window in Visual Studio
>> works
>> perfectly. It's only exporting to pdf via a browser that causes the
>> scrambled images.
>> Does anyone have a work around, besides changing every report to read
>> a
>> png
>> image? We still need transparency.
>> Ryan
>> >On Follow Up.. this appears to be images other than JPEG's, which
>> >according
>> >to documentation are all rendered as PNG's.
>> >"Rob Johnson" wrote:
>> >> After installing RS SP2, images included in my reports display
>> >> fine in
>> >> HTML
>> >> View, Excel View and TIFF View, but when exported to PDF they are
>> >> not
>> >> displaying properly (they appear garbled, much like a scrambled TV
>> >> signal).
>> >>
>> >> Any ideas or thoughts?
>>
>>
>>
>>
>>
>|||One more export issue. When exporting to pdf using the 8 bit png image
(color type 3) from the browser, transparency doesn't work (and it use to
under SP1). As proof that the image is transparent, I can print using the
new print button and transparency works fine. Also when exporting to pdf
via Visual Studio transparency works fine as well (of course so did the 24
bit png).
At least it's not scrambled though!
Ryan
"Donovan Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
news:%23MmyV8AXFHA.2288@.TK2MSFTNGP14.phx.gbl...
> Ah, OK. I couldn't quite understand the GIF part of your message. :)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> news:ep6g6EAXFHA.3348@.TK2MSFTNGP14.phx.gbl...
>> Thanks Donovan for the information. I was in error when I had said that
>> we were originally using a GIF image and that RS was converting it when
>> rendering for the browser. We are indeed using png files at 24 bit.
>> I did save the image as png-8 (which I assume is color type 3) which does
>> fix this problem--although it's lousy quality.
>> So thanks again for the solution/work around.
>> Ryan
>> It is interesting though that you mention that RS doesn't currently
>> support true color w/alpha PNG files. I'm not even using PNG, it's RS
>> that is converting it to
>> "Donovan Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
>> news:eXILSR1WFHA.3584@.TK2MSFTNGP14.phx.gbl...
>> We don't currently support true color w/alpha PNG files, only indexed
>> color (color type 3). If your graphics editing program allows you to
>> specify the color type of your PNG and save it as a type 3 file you
>> should be fine. Prior to SP2, we converted all images to bitmaps which
>> bloated the PDF file. We now compress but have less flexibility on
>> certain image types.
>> I've opened a bug for this issue so we can hopefully get it fixed in
>> Yukon. The easiest work-around for our SQL Server 2000 release is to
>> save as a type 3 file or use a jpg.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> news:%23IailDwWFHA.3584@.TK2MSFTNGP14.phx.gbl...
>> Thanks Donovan for looking into this. Here is our logo
>> (logoRenderedFromBrowser.png). It was originally a GIF image but when
>> rendered to the browser it becomes a png image (perhaps a reason why we
>> can export to PDF via visual studio but not from the browser). Also
>> attached is the scrambled logo (scrambledImage.jpg) screen shot taken
>> directly after export to pdf via the browser.
>> Again, prior to SP2 all reports exported as expected via the browser to
>> pdf. One can only assume that there's been a change with sp2.
>> Thanks in advance,
>> Ryan
>>
>> "Donovan Smith [MSFT]" <donovans@.online.microsoft.com> wrote in message
>> news:%23b0JjJnWFHA.2256@.TK2MSFTNGP14.phx.gbl...
>> I've tried a couple of images and didn't see PNG corruption when
>> exporting
>> to PDF. Would one of you please email me a sample PNG that is
>> exhibiting
>> this behavior so I can take a look? Thank you.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ken Fox" <KenFox@.discussions.microsoft.com> wrote in message
>> news:DF0704F5-B6DF-4BEF-A042-0DE8D7E0F30D@.microsoft.com...
>>I use a custom centering/scaling function as the data source for my
>>image
>> control. Converting the function's output to either GIF or JPEG
>> eliminated
>> the problem for me. I have my image control's format set to JPEG.
>> The
>> problem appears for me when the function's output is set to PNG.
>> "Ryan Opfer" wrote:
>>> I've come accross the same problem having also installed SP2. Still
>>> looking
>>> for the answer.
>>>
>>> I did notice that exporting via the preview window in Visual Studio
>>> works
>>> perfectly. It's only exporting to pdf via a browser that causes the
>>> scrambled images.
>>>
>>> Does anyone have a work around, besides changing every report to
>>> read a
>>> png
>>> image? We still need transparency.
>>>
>>> Ryan
>>> >On Follow Up.. this appears to be images other than JPEG's, which
>>> >according
>>> >to documentation are all rendered as PNG's.
>>>
>>> >"Rob Johnson" wrote:
>>>
>>> >> After installing RS SP2, images included in my reports display
>>> >> fine in
>>> >> HTML
>>> >> View, Excel View and TIFF View, but when exported to PDF they are
>>> >> not
>>> >> displaying properly (they appear garbled, much like a scrambled
>>> >> TV
>>> >> signal).
>>> >>
>>> >> Any ideas or thoughts?
>>>
>>>
>>>
>>
>>
>>
>>
>

Images and PDF Export POST SP2

After installing RS SP2, images included in my reports display fine in HTML
View, Excel View and TIFF View, but when exported to PDF they are not
displaying properly (they appear garbled, much like a scrambled TV signal).
Any ideas or thoughts?On Follow Up.. this appears to be images other than JPEG's, which according
to documentation are all rendered as PNG's.
"Rob Johnson" wrote:
> After installing RS SP2, images included in my reports display fine in HTML
> View, Excel View and TIFF View, but when exported to PDF they are not
> displaying properly (they appear garbled, much like a scrambled TV signal).
> Any ideas or thoughts?

I'm gonna SHOOT the @#$% server!

Ok, I've had it with this thing!!! I'm running Windows Server 2003, SQL
Server 2000 with SP2 and SQLXML 3.0 SP2. I've configured a virtual directory
using the SQLXML IIS utility and all is well. BUT... when I try connecting
to the web service via VS.NET, I keep getting this...
ERROR: 400.100 Bad Request
HResult: 0x80004005
Source: Microsoft SQL isapi extension
Description: The virtual name could not be recognized
I even get that if I try browsing the WSDL file directly from IE.
Now I've checked the security, I've checked the configuration, I've checked
it all but to no avail! I'm gonna take a #@.$% hammer to this box!!!
Now the odd thing is if I disable the application on that virtual directory
(thus stopping the maaping through the DLL, I can properly browse the WSDL
file. HUH?
So... anyone got any ideas and if not, any bullets or a large mallet?
Mark
Please don't shoot.
I forwarded your problem to one of the people of the SQLXML team and hope he
will reply to you.
Best regards
Michael
"Mark A. Donohoe" <Mark (at) MarkDonohoe.com> wrote in message
news:D27F9BE8-F783-41E8-83B8-8A3393EDF2F4@.microsoft.com...
> Ok, I've had it with this thing!!! I'm running Windows Server 2003, SQL
> Server 2000 with SP2 and SQLXML 3.0 SP2. I've configured a virtual
> directory
> using the SQLXML IIS utility and all is well. BUT... when I try
> connecting
> to the web service via VS.NET, I keep getting this...
> ERROR: 400.100 Bad Request
> HResult: 0x80004005
> Source: Microsoft SQL isapi extension
> Description: The virtual name could not be recognized
> I even get that if I try browsing the WSDL file directly from IE.
> Now I've checked the security, I've checked the configuration, I've
> checked
> it all but to no avail! I'm gonna take a #@.$% hammer to this box!!!
> Now the odd thing is if I disable the application on that virtual
> directory
> (thus stopping the maaping through the DLL, I can properly browse the WSDL
> file. HUH?
> So... anyone got any ideas and if not, any bullets or a large mallet?
> Mark
|||Hi there,
Do you have the SOAP Toolkit 2.0 installed? SqlXml 3.0 SP2 requires it for
using web services. However, if you can wait a bit longer, we will be
releasing SP3 which removes that dependency so SOAP Toolkit is no longer
needed.
Thanks,
Irwin
Irwin Dolobowsky
Program Manager, SqlXml
http://blogs.msdn.com/irwando
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark A. Donohoe" <Mark (at) MarkDonohoe.com> wrote in message
news:D27F9BE8-F783-41E8-83B8-8A3393EDF2F4@.microsoft.com...
> Ok, I've had it with this thing!!! I'm running Windows Server 2003, SQL
> Server 2000 with SP2 and SQLXML 3.0 SP2. I've configured a virtual
> directory
> using the SQLXML IIS utility and all is well. BUT... when I try
> connecting
> to the web service via VS.NET, I keep getting this...
> ERROR: 400.100 Bad Request
> HResult: 0x80004005
> Source: Microsoft SQL isapi extension
> Description: The virtual name could not be recognized
> I even get that if I try browsing the WSDL file directly from IE.
> Now I've checked the security, I've checked the configuration, I've
> checked
> it all but to no avail! I'm gonna take a #@.$% hammer to this box!!!
> Now the odd thing is if I disable the application on that virtual
> directory
> (thus stopping the maaping through the DLL, I can properly browse the WSDL
> file. HUH?
> So... anyone got any ideas and if not, any bullets or a large mallet?
> Mark