Is there any possible way to bundle my reports with references to other
controls to build a visual representation of data? I realize that this is
all informational, but I've got a problem with the stock graphs, they look
HORRIBLE.
Anyway, thanks in advance
WestonNot with this version. I gather the next version will have more options
along this line (release date in November).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Weston Weems" <wweems@.NOSPAMno-span-gmail.com> wrote in message
news:eR18CVagFHA.2444@.tk2msftngp13.phx.gbl...
> Is there any possible way to bundle my reports with references to other
> controls to build a visual representation of data? I realize that this is
> all informational, but I've got a problem with the stock graphs, they look
> HORRIBLE.
> Anyway, thanks in advance
> Weston
>
Showing posts with label controls. Show all posts
Showing posts with label controls. Show all posts
Sunday, February 12, 2012
Thursday, February 9, 2012
Alternative to Microsoft?
Andreas,
there are axtiveX controls to control the execution of=20
the various agents. Have a look at this for more detail:
http://www.windowsitpro.com/Articles/Index.cfm?
ArticleID=3D39079&DisplayTab=3DArticle
As for general options, there are alternatives out there.=20
I recently looked at SQL DataCompare, which could be used=20
in a similar way. Some of these alternatives are also=20
significantly faster. However, consider that merge has a=20
huge amount of inbuilt versatility. Merge has automatic=20
range management, a rich set of conflict resolution=20
techniques and assign priorities, the option to=20
dynamically filter data and prefilter snapshots, the=20
ability to configure unidirectional replication (in=20
either direction), the ability to control the batch size.=20
Along with other replication methods, we have subscriber=20
timeouts and inbuild alerts. The list of extras is huge=20
and the price of this functionality is the increased=20
complexity behind the scenes.
is designed for high autonomy.
>--Original Message--
>I have to implement a simple Merge-Replication, using=20
the MSDE.=20
>That means, I can=B4t using Enterprice-Manager.=20
>I don=B4t want using SQLDMO because of redistribution-
problems.=20
>Using T-SQL, it is quite difficult to implement Merge-
Replication.=20
>Are the thrid-pary-products, ActiveX-Controls,=20
Libraries, assembly,
>etc. that manage SQL-Server-Replication very well?
>What do you think about writing your own merge-
replication tool? I
>just wrote a prototyp, and it seems to be very easy.
>pro:
> - no limitations on changing data strukturs while=20
publishing tables
>!!!
> - using a connection in ONE direction (no re-connect=20
from subscriber
>to distritubor necessary, ideal for replication into=20
internet !! )
> - high level of transparency, you can debug each step,=20
you can log
>each SQL-Statement
> - if you want to use a single-sided replication (like=20
transactional
>replication) the subscriber database need not implement=20
anything (no
>table, no trigger, nothing!!)
> - few overhead: just adding 3 triggers per table (like
>MS-merge-replication does) and 2 or 3 system-tables
> - very simple code to switch on replication (just=20
adding the 3
>triggers to each table, independent on data strukture)
>contra:
> - replication-process itself is not tested, each=20
possible event have
>to be implemented and well tested
>I would be happy if someone would like to diskuss this=20
with me, or if
>someone has just written a tool like this, or have=20
another good idea.
>Andreas Lauffer, Germany
>.
>
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:<086e01c51813$bebd2800$a501280a@.phx.gbl>...
> there are axtiveX controls to control the execution of=20
> the various agents. Have a look at this for more detail:
> http://www.windowsitpro.com/Articles...yTab=3DArticle
OK, I tested these controls. There are not bad, but fare away from
beeing perfect. Sometimes the error messages arent detailed enough,
you dont know why replication doesnt work.
In addition, the controls covers only a part of the whole replication
process.
> As for general options, there are alternatives out there.=20
> I recently looked at SQL DataCompare, which could be used=20
> in a similar way. Some of these alternatives are also=20
> significantly faster.
SQL DataCompare looks very nice, but it seems so that it cannot merge
Datasets. You have to tell the tool, wheater to change the Database B
with the changes from A or vise versa.
Maybe there is a possibilty with C#, if you compare all the changes
from Database A and B and generate SQL-Scripts manually.
> However, consider that merge has a=20
> huge amount of inbuilt versatility. Merge has automatic=20
> range management, a rich set of conflict resolution=20
> techniques and assign priorities, the option to=20
> dynamically filter data and prefilter snapshots, the=20
> ability to configure unidirectional replication (in=20
> either direction), the ability to control the batch size.=20
> Along with other replication methods, we have subscriber=20
> timeouts and inbuild alerts. The list of extras is huge=20
> and the price of this functionality is the increased=20
> complexity behind the scenes.
I dont need range management, assign priorities, Data filters, etc.
Comflict management is even much much simpler and comfortable if you
implement this inside your code.
[vbcol=seagreen]
>
>
> is designed for high autonomy.
> the MSDE.=20
> problems.=20
> Replication.=20
> Libraries, assembly,
> replication tool? I
> publishing tables
> from subscriber
> internet !! )
> you can log
> transactional
> anything (no
> adding the 3
> possible event have
> with me, or if
> another good idea.
there are axtiveX controls to control the execution of=20
the various agents. Have a look at this for more detail:
http://www.windowsitpro.com/Articles/Index.cfm?
ArticleID=3D39079&DisplayTab=3DArticle
As for general options, there are alternatives out there.=20
I recently looked at SQL DataCompare, which could be used=20
in a similar way. Some of these alternatives are also=20
significantly faster. However, consider that merge has a=20
huge amount of inbuilt versatility. Merge has automatic=20
range management, a rich set of conflict resolution=20
techniques and assign priorities, the option to=20
dynamically filter data and prefilter snapshots, the=20
ability to configure unidirectional replication (in=20
either direction), the ability to control the batch size.=20
Along with other replication methods, we have subscriber=20
timeouts and inbuild alerts. The list of extras is huge=20
and the price of this functionality is the increased=20
complexity behind the scenes.
is designed for high autonomy.
>--Original Message--
>I have to implement a simple Merge-Replication, using=20
the MSDE.=20
>That means, I can=B4t using Enterprice-Manager.=20
>I don=B4t want using SQLDMO because of redistribution-
problems.=20
>Using T-SQL, it is quite difficult to implement Merge-
Replication.=20
>Are the thrid-pary-products, ActiveX-Controls,=20
Libraries, assembly,
>etc. that manage SQL-Server-Replication very well?
>What do you think about writing your own merge-
replication tool? I
>just wrote a prototyp, and it seems to be very easy.
>pro:
> - no limitations on changing data strukturs while=20
publishing tables
>!!!
> - using a connection in ONE direction (no re-connect=20
from subscriber
>to distritubor necessary, ideal for replication into=20
internet !! )
> - high level of transparency, you can debug each step,=20
you can log
>each SQL-Statement
> - if you want to use a single-sided replication (like=20
transactional
>replication) the subscriber database need not implement=20
anything (no
>table, no trigger, nothing!!)
> - few overhead: just adding 3 triggers per table (like
>MS-merge-replication does) and 2 or 3 system-tables
> - very simple code to switch on replication (just=20
adding the 3
>triggers to each table, independent on data strukture)
>contra:
> - replication-process itself is not tested, each=20
possible event have
>to be implemented and well tested
>I would be happy if someone would like to diskuss this=20
with me, or if
>someone has just written a tool like this, or have=20
another good idea.
>Andreas Lauffer, Germany
>.
>
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:<086e01c51813$bebd2800$a501280a@.phx.gbl>...
> there are axtiveX controls to control the execution of=20
> the various agents. Have a look at this for more detail:
> http://www.windowsitpro.com/Articles...yTab=3DArticle
OK, I tested these controls. There are not bad, but fare away from
beeing perfect. Sometimes the error messages arent detailed enough,
you dont know why replication doesnt work.
In addition, the controls covers only a part of the whole replication
process.
> As for general options, there are alternatives out there.=20
> I recently looked at SQL DataCompare, which could be used=20
> in a similar way. Some of these alternatives are also=20
> significantly faster.
SQL DataCompare looks very nice, but it seems so that it cannot merge
Datasets. You have to tell the tool, wheater to change the Database B
with the changes from A or vise versa.
Maybe there is a possibilty with C#, if you compare all the changes
from Database A and B and generate SQL-Scripts manually.
> However, consider that merge has a=20
> huge amount of inbuilt versatility. Merge has automatic=20
> range management, a rich set of conflict resolution=20
> techniques and assign priorities, the option to=20
> dynamically filter data and prefilter snapshots, the=20
> ability to configure unidirectional replication (in=20
> either direction), the ability to control the batch size.=20
> Along with other replication methods, we have subscriber=20
> timeouts and inbuild alerts. The list of extras is huge=20
> and the price of this functionality is the increased=20
> complexity behind the scenes.
I dont need range management, assign priorities, Data filters, etc.
Comflict management is even much much simpler and comfortable if you
implement this inside your code.
[vbcol=seagreen]
>
>
> is designed for high autonomy.
> the MSDE.=20
> problems.=20
> Replication.=20
> Libraries, assembly,
> replication tool? I
> publishing tables
> from subscriber
> internet !! )
> you can log
> transactional
> anything (no
> adding the 3
> possible event have
> with me, or if
> another good idea.
Subscribe to:
Posts (Atom)