I am fairly new to both the technologies.
Scenario:
I have an Exchange server on one machine, with Outlook. I
am looking for a way to get the information from Exchange
servers (mainly public folders) to SQL-server that is
located on a different machine.
My problem is as follows:
a. I need to get data from Exchange to SQL-server, real
time.
I am going through a round-about way of getting this
information. I have created Linked tables in an Access
Database that exports the data to the SQL-server (on the
same machine). It is not real time.
I can not seem to see the Linked tables from Access
when I use DTS.
There has to be a better way to do this.
Please advise.
Deven
for real time, open the outlook to the mailbox, using Outlook VBA NewMessage
write code to the sql server. Just leave the outlook open.
"deven" <anonymous@.discussions.microsoft.com> wrote in message
news:7cfa01c43149$c84894b0$a001280a@.phx.gbl...
> I am fairly new to both the technologies.
> Scenario:
> I have an Exchange server on one machine, with Outlook. I
> am looking for a way to get the information from Exchange
> servers (mainly public folders) to SQL-server that is
> located on a different machine.
> My problem is as follows:
> a. I need to get data from Exchange to SQL-server, real
> time.
> I am going through a round-about way of getting this
> information. I have created Linked tables in an Access
> Database that exports the data to the SQL-server (on the
> same machine). It is not real time.
> I can not seem to see the Linked tables from Access
> when I use DTS.
> There has to be a better way to do this.
> Please advise.
> Deven
>
Showing posts with label fairly. Show all posts
Showing posts with label fairly. Show all posts
Monday, March 19, 2012
Exchange-SQL server connectivity
I am fairly new to both the technologies.
Scenario:
I have an Exchange server on one machine, with Outlook. I
am looking for a way to get the information from Exchange
servers (mainly public folders) to SQL-server that is
located on a different machine.
My problem is as follows:
a. I need to get data from Exchange to SQL-server, real
time.
I am going through a round-about way of getting this
information. I have created Linked tables in an Access
Database that exports the data to the SQL-server (on the
same machine). It is not real time.
I can not seem to see the Linked tables from Access
when I use DTS.
There has to be a better way to do this.
Please advise.
Devenfor real time, open the outlook to the mailbox, using Outlook VBA NewMessage
write code to the sql server. Just leave the outlook open.
"deven" <anonymous@.discussions.microsoft.com> wrote in message
news:7cfa01c43149$c84894b0$a001280a@.phx.gbl...
> I am fairly new to both the technologies.
> Scenario:
> I have an Exchange server on one machine, with Outlook. I
> am looking for a way to get the information from Exchange
> servers (mainly public folders) to SQL-server that is
> located on a different machine.
> My problem is as follows:
> a. I need to get data from Exchange to SQL-server, real
> time.
> I am going through a round-about way of getting this
> information. I have created Linked tables in an Access
> Database that exports the data to the SQL-server (on the
> same machine). It is not real time.
> I can not seem to see the Linked tables from Access
> when I use DTS.
> There has to be a better way to do this.
> Please advise.
> Deven
>
Scenario:
I have an Exchange server on one machine, with Outlook. I
am looking for a way to get the information from Exchange
servers (mainly public folders) to SQL-server that is
located on a different machine.
My problem is as follows:
a. I need to get data from Exchange to SQL-server, real
time.
I am going through a round-about way of getting this
information. I have created Linked tables in an Access
Database that exports the data to the SQL-server (on the
same machine). It is not real time.
I can not seem to see the Linked tables from Access
when I use DTS.
There has to be a better way to do this.
Please advise.
Devenfor real time, open the outlook to the mailbox, using Outlook VBA NewMessage
write code to the sql server. Just leave the outlook open.
"deven" <anonymous@.discussions.microsoft.com> wrote in message
news:7cfa01c43149$c84894b0$a001280a@.phx.gbl...
> I am fairly new to both the technologies.
> Scenario:
> I have an Exchange server on one machine, with Outlook. I
> am looking for a way to get the information from Exchange
> servers (mainly public folders) to SQL-server that is
> located on a different machine.
> My problem is as follows:
> a. I need to get data from Exchange to SQL-server, real
> time.
> I am going through a round-about way of getting this
> information. I have created Linked tables in an Access
> Database that exports the data to the SQL-server (on the
> same machine). It is not real time.
> I can not seem to see the Linked tables from Access
> when I use DTS.
> There has to be a better way to do this.
> Please advise.
> Deven
>
Friday, March 9, 2012
Excesive Space Allocated
Hello,
I have a fairly large database that at one time I used to do a lot of processing on. Now it's nothing but backup for some old data. I've truncated my transaction log and it's down to about 25 megs. The problem is the transaction log is allocated for ar
ound 2.5 gigs and I can't get it to allocated any less so I'm waiting a ton of space on my server. Is there anyway to shrink how much size your allocated for your log file?
Thanks
Check out DBCC SHRINKFILE in BOL.
Andrew J. Kelly SQL MVP
"Chuck" <anonymous@.discussions.microsoft.com> wrote in message
news:9DF0AAF1-1776-4C66-BE74-EE649A3F7CFE@.microsoft.com...
> Hello,
> I have a fairly large database that at one time I used to do a lot of
processing on. Now it's nothing but backup for some old data. I've
truncated my transaction log and it's down to about 25 megs. The problem is
the transaction log is allocated for around 2.5 gigs and I can't get it to
allocated any less so I'm waiting a ton of space on my server. Is there
anyway to shrink how much size your allocated for your log file?
> Thanks
I have a fairly large database that at one time I used to do a lot of processing on. Now it's nothing but backup for some old data. I've truncated my transaction log and it's down to about 25 megs. The problem is the transaction log is allocated for ar
ound 2.5 gigs and I can't get it to allocated any less so I'm waiting a ton of space on my server. Is there anyway to shrink how much size your allocated for your log file?
Thanks
Check out DBCC SHRINKFILE in BOL.
Andrew J. Kelly SQL MVP
"Chuck" <anonymous@.discussions.microsoft.com> wrote in message
news:9DF0AAF1-1776-4C66-BE74-EE649A3F7CFE@.microsoft.com...
> Hello,
> I have a fairly large database that at one time I used to do a lot of
processing on. Now it's nothing but backup for some old data. I've
truncated my transaction log and it's down to about 25 megs. The problem is
the transaction log is allocated for around 2.5 gigs and I can't get it to
allocated any less so I'm waiting a ton of space on my server. Is there
anyway to shrink how much size your allocated for your log file?
> Thanks
Excesive Space Allocated
Hello,
I have a fairly large database that at one time I used to do a lot of proces
sing on. Now it's nothing but backup for some old data. I've truncated my
transaction log and it's down to about 25 megs. The problem is the transact
ion log is allocated for ar
ound 2.5 gigs and I can't get it to allocated any less so I'm waiting a ton
of space on my server. Is there anyway to shrink how much size your allocat
ed for your log file?
ThanksCheck out DBCC SHRINKFILE in BOL.
Andrew J. Kelly SQL MVP
"Chuck" <anonymous@.discussions.microsoft.com> wrote in message
news:9DF0AAF1-1776-4C66-BE74-EE649A3F7CFE@.microsoft.com...
> Hello,
> I have a fairly large database that at one time I used to do a lot of
processing on. Now it's nothing but backup for some old data. I've
truncated my transaction log and it's down to about 25 megs. The problem is
the transaction log is allocated for around 2.5 gigs and I can't get it to
allocated any less so I'm waiting a ton of space on my server. Is there
anyway to shrink how much size your allocated for your log file?
> Thanks
I have a fairly large database that at one time I used to do a lot of proces
sing on. Now it's nothing but backup for some old data. I've truncated my
transaction log and it's down to about 25 megs. The problem is the transact
ion log is allocated for ar
ound 2.5 gigs and I can't get it to allocated any less so I'm waiting a ton
of space on my server. Is there anyway to shrink how much size your allocat
ed for your log file?
ThanksCheck out DBCC SHRINKFILE in BOL.
Andrew J. Kelly SQL MVP
"Chuck" <anonymous@.discussions.microsoft.com> wrote in message
news:9DF0AAF1-1776-4C66-BE74-EE649A3F7CFE@.microsoft.com...
> Hello,
> I have a fairly large database that at one time I used to do a lot of
processing on. Now it's nothing but backup for some old data. I've
truncated my transaction log and it's down to about 25 megs. The problem is
the transaction log is allocated for around 2.5 gigs and I can't get it to
allocated any less so I'm waiting a ton of space on my server. Is there
anyway to shrink how much size your allocated for your log file?
> Thanks
Friday, February 17, 2012
Excel Rendering - Urgent
Hello,
I have a fairly simple report (with a lot of columns) that I'm trying to
export to Excel. Everytime I do this, I get the following error:
"Excel Rendering Extension: Width of excel cell in the excel sheet exceeded
the maximum limit of 1726.5 Points."
I know that 1726.5 equates to 255 characters in a column, but when I export
to CSV and check the lengths of every value, none of them reach 255.
Is there a workaround to this bug?
Any guidance on this matter would be much apprecited.
Best Regards,
Benjamin Pierce
Open Text CorporationThe experience I have is when the report is empty and you want to render it
to Excel, RS will combine all the columns into one single cell in Excel. One
way to solve this is to shrink the width of all the columns so that the total
length is less than 255 characters.
"Benjamin Pierce" wrote:
> Well, after much trial and error I found the problem.
> I had two tables. A summary table then a "data dump" below that. On the
> first table, I had the "PageBreakAtEnd" property set to true. When I
> changed it to False, the error went away.
> As a workaround, I attempted to set the "PageBreakAtStart" property of the
> second table to true, but this re-introduced the error.
> @. Microsoft: Is this a known bug? I'm attaching my RDL for further
> analysis. It seems like a fairly serious flaw in the Excel Renderer.
> Please let me know if you need more info.
>
> Regards,
> Benjamin Pierce
> Open Text Corporation
>
>
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I have a fairly simple report (with a lot of columns) that I'm trying to
> > export to Excel. Everytime I do this, I get the following error:
> >
> > "Excel Rendering Extension: Width of excel cell in the excel sheet
> exceeded
> > the maximum limit of 1726.5 Points."
> >
> > I know that 1726.5 equates to 255 characters in a column, but when I
> export
> > to CSV and check the lengths of every value, none of them reach 255.
> >
> > Is there a workaround to this bug?
> >
> > Any guidance on this matter would be much apprecited.
> >
> >
> >
> > Best Regards,
> >
> > Benjamin Pierce
> > Open Text Corporation
> >
> >
> >
>
>
>|||The fix will be available in the next service pack (SP2).
You may also contact Microsoft Product Support Services. See
http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A hotfix
for the issue is available. The KB article (883501) should be available
soon.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Benjamin Pierce" <bpierce@.opentext.com> wrote in message
news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I have a fairly simple report (with a lot of columns) that I'm trying to
> export to Excel. Everytime I do this, I get the following error:
> "Excel Rendering Extension: Width of excel cell in the excel sheet
exceeded
> the maximum limit of 1726.5 Points."
> I know that 1726.5 equates to 255 characters in a column, but when I
export
> to CSV and check the lengths of every value, none of them reach 255.
> Is there a workaround to this bug?
> Any guidance on this matter would be much apprecited.
>
> Best Regards,
> Benjamin Pierce
> Open Text Corporation
>
>|||This patch appears to fix the stated problem, but creates another.
This is not a catastrophe; I will structure the report differently to work
around the problem, but I thought RS Engineering might want to hear about it.
The report contains a table followed by a textbox. One of the cells in the
table contains a formula like this:
=ReportItems!TextBoxInThisTable.Value *
ReportItems!TextBoxOnTheSecondPage.Value
This is rendered properly within the report designer and to excel. In
excel, the table data and the standalone textbox are rendered correctly and
the cell containing the formula is calculated correctly. The excel version
retains the formula which something like: _123 * _456.
So far so good.
The problem arises when I define a PageBreakAfter attribute on the table.
Before applying the hotfix, when I attempted to save as excel, report
designer generated the error as described in kb883501: "Excel Rendering
Extension : Width of excel cell in the excel sheet exceeded the maximum limit
of 1726.5 Points."
After the hotfix, the report designer saves the file, but the resulting file
contains a fatal flaw:
The cell containing the formula simply displays the value contained in
ReportItems!TextBoxInThisTable. When I click on the offending cell to view
the formula, Excel crashes with this signature:
AppName: excel.exe AppVer: 11.0.6355.0 AppStamp:40aa979f
ModName: excel.exe ModVer: 11.0.6355.0 ModStamp:40aa979f
fDebug: 0 Offset: 0010be7e
My guess is that this is related to the fact that Excel has always disliked
formulae that refer to cells in other sheets, though there are ways of
"tricking it" into working.
Cheers,
Jeff Gilbert|||I've created a simple rdl which reproduces the problem. It can be found
attached to SRX050121600563, or just let me know and I can provide it.
-Jeff|||Does this SP need to be applied to the Report Server as well or simply on
workstations developing?
"Robert Bruckner [MSFT]" wrote:
> The fix will be available in the next service pack (SP2).
> You may also contact Microsoft Product Support Services. See
> http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A hotfix
> for the issue is available. The KB article (883501) should be available
> soon.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I have a fairly simple report (with a lot of columns) that I'm trying to
> > export to Excel. Everytime I do this, I get the following error:
> >
> > "Excel Rendering Extension: Width of excel cell in the excel sheet
> exceeded
> > the maximum limit of 1726.5 Points."
> >
> > I know that 1726.5 equates to 255 characters in a column, but when I
> export
> > to CSV and check the lengths of every value, none of them reach 255.
> >
> > Is there a workaround to this bug?
> >
> > Any guidance on this matter would be much apprecited.
> >
> >
> >
> > Best Regards,
> >
> > Benjamin Pierce
> > Open Text Corporation
> >
> >
> >
>
>|||It needs to be applied on the report server also.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:1B570DFA-5592-4557-914A-740474FBBFDF@.microsoft.com...
> Does this SP need to be applied to the Report Server as well or simply on
> workstations developing?
> "Robert Bruckner [MSFT]" wrote:
>> The fix will be available in the next service pack (SP2).
>> You may also contact Microsoft Product Support Services. See
>> http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A
>> hotfix
>> for the issue is available. The KB article (883501) should be available
>> soon.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
>> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
>> > Hello,
>> >
>> > I have a fairly simple report (with a lot of columns) that I'm trying
>> > to
>> > export to Excel. Everytime I do this, I get the following error:
>> >
>> > "Excel Rendering Extension: Width of excel cell in the excel sheet
>> exceeded
>> > the maximum limit of 1726.5 Points."
>> >
>> > I know that 1726.5 equates to 255 characters in a column, but when I
>> export
>> > to CSV and check the lengths of every value, none of them reach 255.
>> >
>> > Is there a workaround to this bug?
>> >
>> > Any guidance on this matter would be much apprecited.
>> >
>> >
>> >
>> > Best Regards,
>> >
>> > Benjamin Pierce
>> > Open Text Corporation
>> >
>> >
>> >
>>
I have a fairly simple report (with a lot of columns) that I'm trying to
export to Excel. Everytime I do this, I get the following error:
"Excel Rendering Extension: Width of excel cell in the excel sheet exceeded
the maximum limit of 1726.5 Points."
I know that 1726.5 equates to 255 characters in a column, but when I export
to CSV and check the lengths of every value, none of them reach 255.
Is there a workaround to this bug?
Any guidance on this matter would be much apprecited.
Best Regards,
Benjamin Pierce
Open Text CorporationThe experience I have is when the report is empty and you want to render it
to Excel, RS will combine all the columns into one single cell in Excel. One
way to solve this is to shrink the width of all the columns so that the total
length is less than 255 characters.
"Benjamin Pierce" wrote:
> Well, after much trial and error I found the problem.
> I had two tables. A summary table then a "data dump" below that. On the
> first table, I had the "PageBreakAtEnd" property set to true. When I
> changed it to False, the error went away.
> As a workaround, I attempted to set the "PageBreakAtStart" property of the
> second table to true, but this re-introduced the error.
> @. Microsoft: Is this a known bug? I'm attaching my RDL for further
> analysis. It seems like a fairly serious flaw in the Excel Renderer.
> Please let me know if you need more info.
>
> Regards,
> Benjamin Pierce
> Open Text Corporation
>
>
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I have a fairly simple report (with a lot of columns) that I'm trying to
> > export to Excel. Everytime I do this, I get the following error:
> >
> > "Excel Rendering Extension: Width of excel cell in the excel sheet
> exceeded
> > the maximum limit of 1726.5 Points."
> >
> > I know that 1726.5 equates to 255 characters in a column, but when I
> export
> > to CSV and check the lengths of every value, none of them reach 255.
> >
> > Is there a workaround to this bug?
> >
> > Any guidance on this matter would be much apprecited.
> >
> >
> >
> > Best Regards,
> >
> > Benjamin Pierce
> > Open Text Corporation
> >
> >
> >
>
>
>|||The fix will be available in the next service pack (SP2).
You may also contact Microsoft Product Support Services. See
http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A hotfix
for the issue is available. The KB article (883501) should be available
soon.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Benjamin Pierce" <bpierce@.opentext.com> wrote in message
news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I have a fairly simple report (with a lot of columns) that I'm trying to
> export to Excel. Everytime I do this, I get the following error:
> "Excel Rendering Extension: Width of excel cell in the excel sheet
exceeded
> the maximum limit of 1726.5 Points."
> I know that 1726.5 equates to 255 characters in a column, but when I
export
> to CSV and check the lengths of every value, none of them reach 255.
> Is there a workaround to this bug?
> Any guidance on this matter would be much apprecited.
>
> Best Regards,
> Benjamin Pierce
> Open Text Corporation
>
>|||This patch appears to fix the stated problem, but creates another.
This is not a catastrophe; I will structure the report differently to work
around the problem, but I thought RS Engineering might want to hear about it.
The report contains a table followed by a textbox. One of the cells in the
table contains a formula like this:
=ReportItems!TextBoxInThisTable.Value *
ReportItems!TextBoxOnTheSecondPage.Value
This is rendered properly within the report designer and to excel. In
excel, the table data and the standalone textbox are rendered correctly and
the cell containing the formula is calculated correctly. The excel version
retains the formula which something like: _123 * _456.
So far so good.
The problem arises when I define a PageBreakAfter attribute on the table.
Before applying the hotfix, when I attempted to save as excel, report
designer generated the error as described in kb883501: "Excel Rendering
Extension : Width of excel cell in the excel sheet exceeded the maximum limit
of 1726.5 Points."
After the hotfix, the report designer saves the file, but the resulting file
contains a fatal flaw:
The cell containing the formula simply displays the value contained in
ReportItems!TextBoxInThisTable. When I click on the offending cell to view
the formula, Excel crashes with this signature:
AppName: excel.exe AppVer: 11.0.6355.0 AppStamp:40aa979f
ModName: excel.exe ModVer: 11.0.6355.0 ModStamp:40aa979f
fDebug: 0 Offset: 0010be7e
My guess is that this is related to the fact that Excel has always disliked
formulae that refer to cells in other sheets, though there are ways of
"tricking it" into working.
Cheers,
Jeff Gilbert|||I've created a simple rdl which reproduces the problem. It can be found
attached to SRX050121600563, or just let me know and I can provide it.
-Jeff|||Does this SP need to be applied to the Report Server as well or simply on
workstations developing?
"Robert Bruckner [MSFT]" wrote:
> The fix will be available in the next service pack (SP2).
> You may also contact Microsoft Product Support Services. See
> http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A hotfix
> for the issue is available. The KB article (883501) should be available
> soon.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I have a fairly simple report (with a lot of columns) that I'm trying to
> > export to Excel. Everytime I do this, I get the following error:
> >
> > "Excel Rendering Extension: Width of excel cell in the excel sheet
> exceeded
> > the maximum limit of 1726.5 Points."
> >
> > I know that 1726.5 equates to 255 characters in a column, but when I
> export
> > to CSV and check the lengths of every value, none of them reach 255.
> >
> > Is there a workaround to this bug?
> >
> > Any guidance on this matter would be much apprecited.
> >
> >
> >
> > Best Regards,
> >
> > Benjamin Pierce
> > Open Text Corporation
> >
> >
> >
>
>|||It needs to be applied on the report server also.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:1B570DFA-5592-4557-914A-740474FBBFDF@.microsoft.com...
> Does this SP need to be applied to the Report Server as well or simply on
> workstations developing?
> "Robert Bruckner [MSFT]" wrote:
>> The fix will be available in the next service pack (SP2).
>> You may also contact Microsoft Product Support Services. See
>> http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A
>> hotfix
>> for the issue is available. The KB article (883501) should be available
>> soon.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
>> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
>> > Hello,
>> >
>> > I have a fairly simple report (with a lot of columns) that I'm trying
>> > to
>> > export to Excel. Everytime I do this, I get the following error:
>> >
>> > "Excel Rendering Extension: Width of excel cell in the excel sheet
>> exceeded
>> > the maximum limit of 1726.5 Points."
>> >
>> > I know that 1726.5 equates to 255 characters in a column, but when I
>> export
>> > to CSV and check the lengths of every value, none of them reach 255.
>> >
>> > Is there a workaround to this bug?
>> >
>> > Any guidance on this matter would be much apprecited.
>> >
>> >
>> >
>> > Best Regards,
>> >
>> > Benjamin Pierce
>> > Open Text Corporation
>> >
>> >
>> >
>>
Subscribe to:
Posts (Atom)