Extending the number of rows returned per page in RS

Is there a way to extend the number of rows that will be returned so that Reporting services doesn't display such a large number of pages for the users to page through? It would be easier for them to "wheel mouse" through a long page on the screen.

Anyone out there have any thoughts on how this might be accomplished?

Thanks!

Travis

Here are a couple of options:

- set PageBreakAtEnd and PageBreakAtStart to false on your tables/matrices/grouping panels

- make your row heights smaller, use a smaller font

- filter your data better, or group it into smaller groups and have each group rendered into its own table, turn off paging on those tables

But turning off paging looks okay when viewing the report in the browser, but can make the report look like *** when exported to PDF.

Extending SQL Server Management Studio

I am wondering if it is possible to extend the Sql Server Management Studio
user interface by adding plugins. Similar to the way plugins can be
generated for Visual Studio 2005.Not yet--it's something they are talking about adding to a future release.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"Andy S" <AndyS@.discussions.microsoft.com> wrote in message
news:1FFA776D-388F-413E-81C4-B2AA996FD572@.microsoft.com...
>I am wondering if it is possible to extend the Sql Server Management Studio
> user interface by adding plugins. Similar to the way plugins can be
> generated for Visual Studio 2005.
>|||That's what I feared, thanks!
"Adam Machanic" wrote:

> Not yet--it's something they are talking about adding to a future release.
>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "Andy S" <AndyS@.discussions.microsoft.com> wrote in message
> news:1FFA776D-388F-413E-81C4-B2AA996FD572@.microsoft.com...
>
>

Extending RS

I want to know if there is some place where I can find information on how to
extend RS, for example, create my custom controls for use in reports.
--
Eduardo FonsecaThis should help:
http://msdn2.microsoft.com/en-us/library/ms345231(SQL.90).aspx
--
Francisco Padron
www.chartfx.com

Extending ReportingServicesFileShareDeliveryProvider

Hello all,
I need to somehow extend the functionality of the
ReportingServicesFileShareDeliveryProvider so I can ship html formatted
reports along with their chart images to a file share. I've deployed some
reports using the mhtml file format, but alot of our users have problems
viewing reports in this format and our IT dept cannot figure out why...some
computers cannot view the reports unless windows system font is set to small.
Others cannot see the reports at all...and yet other have no problems.
The best thing will be to have the html format and the chart images
exported. The Printer Delivery example does not help 100% because of two
areas:
1) I'm wanting to extend an existing extension if possible...as opposed to
what the Printer Delivery example does...creating an extension from scratch
2) I want to stream the chart images out to the file share as well
Any assistence with this would be awesome. I'll hobble along in the
meantime...
-thanks, brian parkerHi Brian:
I don't see the extensions being too extensible themselves. The
parameters and delivery mechanisms are usually so disparate that it
wouldn't make any sense to inherit from an existing delivery class.
I have another sample that might be useful to you (although I haven't
taken care of delivering images, I plan to try this in the future).
The Blog Delivery Extension
http://odetocode.com/Blogs/scott/archive/2004/08/16/393.aspx
Deliver Reports To A Blog
http://odetocode.com/Blogs/scott/archive/2004/08/16/390.aspx
--
Scott
http://www.OdeToCode.com/
On Fri, 1 Oct 2004 20:03:02 -0700, Brian Parker
<BrianParker@.discussions.microsoft.com> wrote:
>Hello all,
> I need to somehow extend the functionality of the
>ReportingServicesFileShareDeliveryProvider so I can ship html formatted
>reports along with their chart images to a file share. I've deployed some
>reports using the mhtml file format, but alot of our users have problems
>viewing reports in this format and our IT dept cannot figure out why...some
>computers cannot view the reports unless windows system font is set to small.
> Others cannot see the reports at all...and yet other have no problems.
>The best thing will be to have the html format and the chart images
>exported. The Printer Delivery example does not help 100% because of two
>areas:
>1) I'm wanting to extend an existing extension if possible...as opposed to
>what the Printer Delivery example does...creating an extension from scratch
>2) I want to stream the chart images out to the file share as well
>Any assistence with this would be awesome. I'll hobble along in the
>meantime...
>-thanks, brian parker|||Scott, This worked beautifully for me. Thanks for your help...
"Scott Allen" wrote:
> Hi Brian:
> I don't see the extensions being too extensible themselves. The
> parameters and delivery mechanisms are usually so disparate that it
> wouldn't make any sense to inherit from an existing delivery class.
> I have another sample that might be useful to you (although I haven't
> taken care of delivering images, I plan to try this in the future).
> The Blog Delivery Extension
> http://odetocode.com/Blogs/scott/archive/2004/08/16/393.aspx
> Deliver Reports To A Blog
> http://odetocode.com/Blogs/scott/archive/2004/08/16/390.aspx
> --
> Scott
> http://www.OdeToCode.com/
> On Fri, 1 Oct 2004 20:03:02 -0700, Brian Parker
> <BrianParker@.discussions.microsoft.com> wrote:
> >Hello all,
> >
> > I need to somehow extend the functionality of the
> >ReportingServicesFileShareDeliveryProvider so I can ship html formatted
> >reports along with their chart images to a file share. I've deployed some
> >reports using the mhtml file format, but alot of our users have problems
> >viewing reports in this format and our IT dept cannot figure out why...some
> >computers cannot view the reports unless windows system font is set to small.
> > Others cannot see the reports at all...and yet other have no problems.
> >
> >The best thing will be to have the html format and the chart images
> >exported. The Printer Delivery example does not help 100% because of two
> >areas:
> >
> >1) I'm wanting to extend an existing extension if possible...as opposed to
> >what the Printer Delivery example does...creating an extension from scratch
> >2) I want to stream the chart images out to the file share as well
> >
> >Any assistence with this would be awesome. I'll hobble along in the
> >meantime...
> >
> >-thanks, brian parker
>sql

Extending BI studio

Hi,
I need to add a custom menu option say under the Tools menu in the BI studio for SSIS projects. Is it possible to extend BU studio using Visual studio addins, or Visual Studio SDK (VSIP).

The Visual studio addin works fine; however I want my custom menu option to show up only when I have a SSIS project open so that I can perfom my custom step whenever the user selects the menu option

Thanks,
-SuriYou can extend BIDS with standard Visual Studio 2005 add-ins, because it is Visual Studio 2005. If you look at the Help menu, About, you will see it is the full VS IDE. The "Installed Products" list just shows different items depending on if you have installed through SQL Server tools only, VS only, or both SQL & VS together.|||Hi Darren,
The real problem I am facing is that the Visual Studio 2005 addin wizard allows you to specify the contextGUIDS which are defined in the vsContextGuids class. This class has guids defined only for Visual Basic, C# and J# type projects. I am not sure how I can specify a SSIS project using the vsContextGuids class.

-Suri|||Sorry, haven't got that far myself yet, but I look forward to someone else answering as I'm sure I'll need to know.

Just out of interest what does your SSIS specific add-in do?|||In the custom action, I need to load the package, parse it for some specific information, and write that information to a xml file (basically filtered package information) which can be then read and processed by another app we have.

Thanks|||

I'm not positive if this is what you're after, but I have an SSIS deployment add-in that we use to allow developers to deploy packages to a server. We use the following code to determine what packages are in the current solution, it may help? This sample builds nodes on a treeview for each project/package found in the current solution.

Private Const ssisProjectKind As String = "{d183a3d8-5fd8-494b-b014-37f57b35e655}"

If _applicationObject.Solution.Count = 0 Then
Return "Not valid without an open solution"
End If

Dim prjCount As Integer = 0
Dim pkgCount As Integer = 0

For Each proj As Project In _applicationObject.Solution.Projects
If Not proj.Kind = ssisProjectKind Then
Continue For
End If
prjCount += 1
Dim prjNode As TreeNode = Me.tvPackages.Nodes.Add(proj.Name)
For Each pi As ProjectItem In proj.ProjectItems
If pi.Name.EndsWith(".dtsx") Then
Dim pkgNode As TreeNode = prjNode.Nodes.Add(pi.Name)
pkgNode.Tag = pi.FileNames(0)
pkgCount += 1
End If
Next
Next

If prjCount = 0 Then
Return "No SSIS Projects were found in this solution"
End If

If pkgCount = 0 Then
Return "No SSIS Packages were found in this solution"
End If

Thanks!
Harry

Extending BI studio

Hi,
I need to add a custom menu option say under the Tools menu in the BI studio for SSIS projects. Is it possible to extend BU studio using Visual studio addins, or Visual Studio SDK (VSIP).

The Visual studio addin works fine; however I want my custom menu option to show up only when I have a SSIS project open so that I can perfom my custom step whenever the user selects the menu option

Thanks,
-SuriYou can extend BIDS with standard Visual Studio 2005 add-ins, because it is Visual Studio 2005. If you look at the Help menu, About, you will see it is the full VS IDE. The "Installed Products" list just shows different items depending on if you have installed through SQL Server tools only, VS only, or both SQL & VS together.|||Hi Darren,
The real problem I am facing is that the Visual Studio 2005 addin wizard allows you to specify the contextGUIDS which are defined in the vsContextGuids class. This class has guids defined only for Visual Basic, C# and J# type projects. I am not sure how I can specify a SSIS project using the vsContextGuids class.

-Suri
|||Sorry, haven't got that far myself yet, but I look forward to someone else answering as I'm sure I'll need to know.

Just out of interest what does your SSIS specific add-in do?|||In the custom action, I need to load the package, parse it for some specific information, and write that information to a xml file (basically filtered package information) which can be then read and processed by another app we have.

Thanks
|||

I'm not positive if this is what you're after, but I have an SSIS deployment add-in that we use to allow developers to deploy packages to a server. We use the following code to determine what packages are in the current solution, it may help? This sample builds nodes on a treeview for each project/package found in the current solution.

Private Const ssisProjectKind As String = "{d183a3d8-5fd8-494b-b014-37f57b35e655}"

If _applicationObject.Solution.Count = 0 Then
Return "Not valid without an open solution"
End If

Dim prjCount As Integer = 0
Dim pkgCount As Integer = 0

For Each proj As Project In _applicationObject.Solution.Projects
If Not proj.Kind = ssisProjectKind Then
Continue For
End If
prjCount += 1
Dim prjNode As TreeNode = Me.tvPackages.Nodes.Add(proj.Name)
For Each pi As ProjectItem In proj.ProjectItems
If pi.Name.EndsWith(".dtsx") Then
Dim pkgNode As TreeNode = prjNode.Nodes.Add(pi.Name)
pkgNode.Tag = pi.FileNames(0)
pkgCount += 1
End If
Next
Next

If prjCount = 0 Then
Return "No SSIS Projects were found in this solution"
End If

If pkgCount = 0 Then
Return "No SSIS Packages were found in this solution"
End If

Thanks!
Harry

Extended Stored Procedure

I have written extend stored procedure using dblib.
declare @.p1 int
xp_myProc 'select * from table', @.p1 output.
This extended procedure exeute the query and generate the
xml. Using xp_prepardocument it generate the handle.
The output handle i want to use it another procedure to
read the value.
<anonymous@.discussions.microsoft.com> wrote in message
news:717501c47625$ef3aeb60$a401280a@.phx.gbl...
>I have written extend stored procedure using dblib.
> declare @.p1 int
> xp_myProc 'select * from table', @.p1 output.
> This extended procedure exeute the query and generate the
> xml. Using xp_prepardocument it generate the handle.
> The output handle i want to use it another procedure to
> read the value.
Are you having problems with the handle no longer being valid?
Bryant
|||Note that the handle is valid for the duration of a session. If your xp runs
in a different session context, the handle cannot be reused...
Best regards
Michael
"Bryant Likes" <bryant@.suespammers.org> wrote in message
news:%23mDquOsdEHA.712@.TK2MSFTNGP09.phx.gbl...
> <anonymous@.discussions.microsoft.com> wrote in message
> news:717501c47625$ef3aeb60$a401280a@.phx.gbl...
> Are you having problems with the handle no longer being valid?
> --
> Bryant
>

extend to another table

Hi,
I have a table with 3 fileds that are only filled in a few circunstances,
let say 5 out of 100. Is it ok to separate those values into another table?
And in the case it is separated, is it ok to define a different primary key
or it would be the same primary key as the primary table?
Now it looks to me to have 2 options:
First, set a different primary key to the auxiliary table and set a FK to
the primary table.
Second, set the primary key of the auxiliary table the same as the primary
key of the primary table.
I had always thought that 1 to 1 relationship between tables have no sense,
but now I don't know how to design this.
Thanks for any help
apuyinc> I have a table with 3 fileds that are only filled in a few circunstances,
> let say 5 out of 100. Is it ok to separate those values into another
> table?
> And in the case it is separated, is it ok to define a different primary
> key
> or it would be the same primary key as the primary table?
> Now it looks to me to have 2 options:
> First, set a different primary key to the auxiliary table and set a FK to
> the primary table.
What would you set as the primary key, other than the naturally obvious
choice?

> Second, set the primary key of the auxiliary table the same as the primary
> key of the primary table.
> I had always thought that 1 to 1 relationship between tables have no
> sense,
When it's potentially 1 to 0, this makes sense. Why have a bunch of columns
that are NULL 95 out of 100 times? It makes joins more complex, yes, but
you can solve this once with a view.
It can also make sense if you are dealing with two or three columns 90% of
the time, and you only care about the other 80 columns 10% of the time. Why
not leave those other columns out of all the engine's work except when you
actually need them?
A|||What I write below is my opinion :)
Logically, a table should be an entity by itself. I would say its a bad
design to split a few columns because it doesn't usually get filled.
Say for example, middle name doesn't get filled 90% of the time.
So we can say that customer_id and middle_name alone can be moved to a new
table because it will save space.
But email addess, address, telephone may be moved to a seperate table along
with customer_id. In this case you have moved the customer details away from
the customer master. It can make sense.
I would say its better sometimes to denormalize the table.
Do I make sense?
"apuyinc" wrote:

> Hi,
> I have a table with 3 fileds that are only filled in a few circunstances,
> let say 5 out of 100. Is it ok to separate those values into another tabl
e?
> And in the case it is separated, is it ok to define a different primary ke
y
> or it would be the same primary key as the primary table?
> Now it looks to me to have 2 options:
> First, set a different primary key to the auxiliary table and set a FK to
> the primary table.
> Second, set the primary key of the auxiliary table the same as the primary
> key of the primary table.
> I had always thought that 1 to 1 relationship between tables have no sense
,
> but now I don't know how to design this.
> Thanks for any help
> apuyinc|||apuyinc wrote:
> Hi,
> I have a table with 3 fileds that are only filled in a few circunstances,
> let say 5 out of 100. Is it ok to separate those values into another tabl
e?
> And in the case it is separated, is it ok to define a different primary ke
y
> or it would be the same primary key as the primary table?
> Now it looks to me to have 2 options:
> First, set a different primary key to the auxiliary table and set a FK to
> the primary table.
> Second, set the primary key of the auxiliary table the same as the primary
> key of the primary table.
> I had always thought that 1 to 1 relationship between tables have no sense
,
> but now I don't know how to design this.
>
If the 3 columns in the second table are optional then such a
relationship wouldn't be 1 -> 1. It would be 1 -> {0|1}. Yes, it makes
perfect sense but don't forget the foreign key. Example:
CREATE TABLE t1 (key_col INT NOT NULL PRIMARY KEY, ... other columns);
CREATE TABLE t2 (key_col INT NOT NULL PRIMARY KEY REFERENCES t1
(key_col), col1 INT NOT NULL, col2 INT NOT NULL, col3 INT NOT NULL);
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||> > I have a table with 3 fileds that are only filled in a few circunstances,
> What would you set as the primary key, other than the naturally obvious
> choice?
I thought about an identity...

> When it's potentially 1 to 0, this makes sense. Why have a bunch of colum
ns
> that are NULL 95 out of 100 times? It makes joins more complex, yes, but
> you can solve this once with a view.
Mmm... you are right, I will split it and use a view.
Now I have another question regarding views. If the secondary table have a
FK to another table. The view will have it? As far as I know you can't
create a FK relationship using a view, at least in SQL 2k which I am using.

> It can also make sense if you are dealing with two or three columns 90% of
> the time, and you only care about the other 80 columns 10% of the time. W
hy
> not leave those other columns out of all the engine's work except when you
> actually need them?
> A
>
>|||>> What would you set as the primary key, other than the naturally obvious
> I thought about an identity...
That's not really a key, what is your primary key in the first table?

> Now I have another question regarding views. If the secondary table have
> a
> FK to another table. The view will have it? As far as I know you can't
> create a FK relationship using a view, at least in SQL 2k which I am
> using.
Your view doesn't have the constraint; the view is just a query. You would
just write the view as:
CREATE VIEW dbo.MyView
AS
SELECT
t1.col1,
t1.col2,
col3 = COALESCE(t2.col3, '')
-- or just t.col3 if you want NULL to appear
FROM
t1
LEFT OUTER JOIN
t2
ON
t1.PrimaryKey = t2.PrimaryKey
GO|||Thanks for the help..
"Aaron Bertrand [SQL Server MVP]" wrote:

> That's not really a key, what is your primary key in the first table?
The primary key is codeId so... the primary key of the second table will be
codeId too.

> Your view doesn't have the constraint; the view is just a query. You woul
d
> just write the view as:
> CREATE VIEW dbo.MyView
> AS
> SELECT
> t1.col1,
> t1.col2,
> col3 = COALESCE(t2.col3, '')
> -- or just t.col3 if you want NULL to appear
> FROM
> t1
> LEFT OUTER JOIN
> t2
> ON
> t1.PrimaryKey = t2.PrimaryKey
> GO
>
>|||what do you mean by file sorted?
--
"apuyinc" wrote:

> Hi,
> I have a table with 3 fileds that are only filled in a few circunstances,
> let say 5 out of 100. Is it ok to separate those values into another tabl
e?
> And in the case it is separated, is it ok to define a different primary ke
y
> or it would be the same primary key as the primary table?
> Now it looks to me to have 2 options:
> First, set a different primary key to the auxiliary table and set a FK to
> the primary table.
> Second, set the primary key of the auxiliary table the same as the primary
> key of the primary table.
> I had always thought that 1 to 1 relationship between tables have no sense
,
> but now I don't know how to design this.
> Thanks for any help
> apuyinc|||I am terribly sorry. Wrong post.. again :P
--
"Omnibuzz" wrote:
> what do you mean by file sorted?
> --
>
>
> "apuyinc" wrote:
>

extend time out setting

Hi,
I really need some help here. I have a few sql clients that connects to
my sql server through wireless connection. Sometimes, these wireless
connections link is down for a few seconds. When user try to continue
to run some query, the db process dead error message appears. Is the
anyway to extend the time out setting to longer time so that this
problem could be minimise?
Thanks a million.Hi
I think this would be a configuration setting on the wireless adapter rather
than the SQL Server connection. You may want to also try sending some form o
f
keep-alive although this would increase the network traffic!
John
"masterwee@.gmail.com" wrote:

> Hi,
> I really need some help here. I have a few sql clients that connects to
> my sql server through wireless connection. Sometimes, these wireless
> connections link is down for a few seconds. When user try to continue
> to run some query, the db process dead error message appears. Is the
> anyway to extend the time out setting to longer time so that this
> problem could be minimise?
> Thanks a million.
>|||The dbprocess dead error indicates a terminated connection rather than a
timeout. The application needs to be smart enough to attempt to reconnect
following the error.
Hope this helps.
Dan Guzman
SQL Server MVP
<masterwee@.gmail.com> wrote in message
news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> Hi,
> I really need some help here. I have a few sql clients that connects to
> my sql server through wireless connection. Sometimes, these wireless
> connections link is down for a few seconds. When user try to continue
> to run some query, the db process dead error message appears. Is the
> anyway to extend the time out setting to longer time so that this
> problem could be minimise?
> Thanks a million.
>|||I have similar problems on some remote sites. Some are running the client
over ISDN which naturally timesout and should pick up the line again when
there is activity. But when the user generates some activity we get the db
process dead message. We migrated these sites from Sybase which never had
these issues and seemed more robust in these situations.
Is there any config options we can use on the client or server to make the
connections less fickle?
Is there any updated client that might be more reliable?
We are using SQL Server 2000 Sp4 but the client is the one on the original
SQl Server 2000 CD.
Thanks,
"Dan Guzman" wrote:

> The dbprocess dead error indicates a terminated connection rather than a
> timeout. The application needs to be smart enough to attempt to reconnect
> following the error.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <masterwee@.gmail.com> wrote in message
> news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
>|||Hi Marty
Unless you have the SQL Server tools on the client PC then there is no point
in using it on the client. You should make sure that a recent version of MDA
C
is on there, although I don't think this will cure the issue as the server
can not reach the client and it can not instigate the ISDN connection.
As Dan has stated you will need to handle the error and reconnect the client
if you get this error.
Has the client application changed from powerbuilder?
John
"Marty" wrote:
[vbcol=seagreen]
> I have similar problems on some remote sites. Some are running the client
> over ISDN which naturally timesout and should pick up the line again when
> there is activity. But when the user generates some activity we get the db
> process dead message. We migrated these sites from Sybase which never had
> these issues and seemed more robust in these situations.
> Is there any config options we can use on the client or server to make the
> connections less fickle?
> Is there any updated client that might be more reliable?
> We are using SQL Server 2000 Sp4 but the client is the one on the original
> SQl Server 2000 CD.
> Thanks,
>
> "Dan Guzman" wrote:
>|||John,
When any activity happens on the client, it wakes up the ISDN connection and
should carry on where it left off in the application, but it looks like the
Client does not re-connect to the server correctly.
I'm not sure which SQL Server tools you refer to?
As for MDAC, it will be the one on the CD, should there be a later version?
The application is written in C++ not Powerbuilder. It is the database which
has been migrated to SQL Server from Sybase, and the old Sybase Open Client
did not report these errors on the same ISDN line.
Thanks,
M
"John Bell" wrote:
[vbcol=seagreen]
> Hi Marty
> Unless you have the SQL Server tools on the client PC then there is no poi
nt
> in using it on the client. You should make sure that a recent version of M
DAC
> is on there, although I don't think this will cure the issue as the server
> can not reach the client and it can not instigate the ISDN connection.
> As Dan has stated you will need to handle the error and reconnect the clie
nt
> if you get this error.
> Has the client application changed from powerbuilder?
> John
> "Marty" wrote:
>|||Hi Marty
Use the MDAC checker from
http://msdn.microsoft.com/data/ref/mdac/downloads/. MDAC can be updated
through other products such as XP SP1, so you may not be on the same version
at all sites. You will need to change the client application so that if the
error is detected the connection is closed and re-open it. I don't know if
the Open Client has the intellegence to silently reconnect or if it was
sending a keep alive.
John
"Marty" wrote:
[vbcol=seagreen]
> John,
> When any activity happens on the client, it wakes up the ISDN connection a
nd
> should carry on where it left off in the application, but it looks like th
e
> Client does not re-connect to the server correctly.
> I'm not sure which SQL Server tools you refer to?
> As for MDAC, it will be the one on the CD, should there be a later version
?
> The application is written in C++ not Powerbuilder. It is the database whi
ch
> has been migrated to SQL Server from Sybase, and the old Sybase Open Clien
t
> did not report these errors on the same ISDN line.
> Thanks,
> M
>
> "John Bell" wrote:
>

extend time out setting

I have similar problems on some remote sites. Some are running the client
over ISDN which naturally timesout and should pick up the line again when
there is activity. But when the user generates some activity we get the db
process dead message. We migrated these sites from Sybase which never had
these issues and seemed more robust in these situations.
Is there any config options we can use on the client or server to make the
connections less fickle?
Is there any updated client that might be more reliable?
We are using SQL Server 2000 Sp4 but the client is the one on the original
SQl Server 2000 CD.
Thanks,
"Dan Guzman" wrote:

> The dbprocess dead error indicates a terminated connection rather than a
> timeout. The application needs to be smart enough to attempt to reconnect
> following the error.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <masterwee@.gmail.com> wrote in message
> news:1162278624.684826.264940@.m73g2000cwd.googlegr oups.com...
>
Hi Marty
Unless you have the SQL Server tools on the client PC then there is no point
in using it on the client. You should make sure that a recent version of MDAC
is on there, although I don't think this will cure the issue as the server
can not reach the client and it can not instigate the ISDN connection.
As Dan has stated you will need to handle the error and reconnect the client
if you get this error.
Has the client application changed from powerbuilder?
John
"Marty" wrote:
[vbcol=seagreen]
> I have similar problems on some remote sites. Some are running the client
> over ISDN which naturally timesout and should pick up the line again when
> there is activity. But when the user generates some activity we get the db
> process dead message. We migrated these sites from Sybase which never had
> these issues and seemed more robust in these situations.
> Is there any config options we can use on the client or server to make the
> connections less fickle?
> Is there any updated client that might be more reliable?
> We are using SQL Server 2000 Sp4 but the client is the one on the original
> SQl Server 2000 CD.
> Thanks,
>
> "Dan Guzman" wrote:
|||John,
When any activity happens on the client, it wakes up the ISDN connection and
should carry on where it left off in the application, but it looks like the
Client does not re-connect to the server correctly.
I'm not sure which SQL Server tools you refer to?
As for MDAC, it will be the one on the CD, should there be a later version?
The application is written in C++ not Powerbuilder. It is the database which
has been migrated to SQL Server from Sybase, and the old Sybase Open Client
did not report these errors on the same ISDN line.
Thanks,
M
"John Bell" wrote:
[vbcol=seagreen]
> Hi Marty
> Unless you have the SQL Server tools on the client PC then there is no point
> in using it on the client. You should make sure that a recent version of MDAC
> is on there, although I don't think this will cure the issue as the server
> can not reach the client and it can not instigate the ISDN connection.
> As Dan has stated you will need to handle the error and reconnect the client
> if you get this error.
> Has the client application changed from powerbuilder?
> John
> "Marty" wrote:
|||Hi Marty
Use the MDAC checker from
http://msdn.microsoft.com/data/ref/mdac/downloads/. MDAC can be updated
through other products such as XP SP1, so you may not be on the same version
at all sites. You will need to change the client application so that if the
error is detected the connection is closed and re-open it. I don't know if
the Open Client has the intellegence to silently reconnect or if it was
sending a keep alive.
John
"Marty" wrote:
[vbcol=seagreen]
> John,
> When any activity happens on the client, it wakes up the ISDN connection and
> should carry on where it left off in the application, but it looks like the
> Client does not re-connect to the server correctly.
> I'm not sure which SQL Server tools you refer to?
> As for MDAC, it will be the one on the CD, should there be a later version?
> The application is written in C++ not Powerbuilder. It is the database which
> has been migrated to SQL Server from Sybase, and the old Sybase Open Client
> did not report these errors on the same ISDN line.
> Thanks,
> M
>
> "John Bell" wrote:

extend time out setting

Hi,
I really need some help here. I have a few sql clients that connects to
my sql server through wireless connection. Sometimes, these wireless
connections link is down for a few seconds. When user try to continue
to run some query, the db process dead error message appears. Is the
anyway to extend the time out setting to longer time so that this
problem could be minimise?
Thanks a million.Hi
I think this would be a configuration setting on the wireless adapter rather
than the SQL Server connection. You may want to also try sending some form of
keep-alive although this would increase the network traffic!
John
"masterwee@.gmail.com" wrote:
> Hi,
> I really need some help here. I have a few sql clients that connects to
> my sql server through wireless connection. Sometimes, these wireless
> connections link is down for a few seconds. When user try to continue
> to run some query, the db process dead error message appears. Is the
> anyway to extend the time out setting to longer time so that this
> problem could be minimise?
> Thanks a million.
>|||The dbprocess dead error indicates a terminated connection rather than a
timeout. The application needs to be smart enough to attempt to reconnect
following the error.
--
Hope this helps.
Dan Guzman
SQL Server MVP
<masterwee@.gmail.com> wrote in message
news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> Hi,
> I really need some help here. I have a few sql clients that connects to
> my sql server through wireless connection. Sometimes, these wireless
> connections link is down for a few seconds. When user try to continue
> to run some query, the db process dead error message appears. Is the
> anyway to extend the time out setting to longer time so that this
> problem could be minimise?
> Thanks a million.
>|||I have similar problems on some remote sites. Some are running the client
over ISDN which naturally timesout and should pick up the line again when
there is activity. But when the user generates some activity we get the db
process dead message. We migrated these sites from Sybase which never had
these issues and seemed more robust in these situations.
Is there any config options we can use on the client or server to make the
connections less fickle?
Is there any updated client that might be more reliable?
We are using SQL Server 2000 Sp4 but the client is the one on the original
SQl Server 2000 CD.
Thanks,
"Dan Guzman" wrote:
> The dbprocess dead error indicates a terminated connection rather than a
> timeout. The application needs to be smart enough to attempt to reconnect
> following the error.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <masterwee@.gmail.com> wrote in message
> news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> > Hi,
> >
> > I really need some help here. I have a few sql clients that connects to
> > my sql server through wireless connection. Sometimes, these wireless
> > connections link is down for a few seconds. When user try to continue
> > to run some query, the db process dead error message appears. Is the
> > anyway to extend the time out setting to longer time so that this
> > problem could be minimise?
> >
> > Thanks a million.
> >
>|||Hi Marty
Unless you have the SQL Server tools on the client PC then there is no point
in using it on the client. You should make sure that a recent version of MDAC
is on there, although I don't think this will cure the issue as the server
can not reach the client and it can not instigate the ISDN connection.
As Dan has stated you will need to handle the error and reconnect the client
if you get this error.
Has the client application changed from powerbuilder?
John
"Marty" wrote:
> I have similar problems on some remote sites. Some are running the client
> over ISDN which naturally timesout and should pick up the line again when
> there is activity. But when the user generates some activity we get the db
> process dead message. We migrated these sites from Sybase which never had
> these issues and seemed more robust in these situations.
> Is there any config options we can use on the client or server to make the
> connections less fickle?
> Is there any updated client that might be more reliable?
> We are using SQL Server 2000 Sp4 but the client is the one on the original
> SQl Server 2000 CD.
> Thanks,
>
> "Dan Guzman" wrote:
> > The dbprocess dead error indicates a terminated connection rather than a
> > timeout. The application needs to be smart enough to attempt to reconnect
> > following the error.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > <masterwee@.gmail.com> wrote in message
> > news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> > > Hi,
> > >
> > > I really need some help here. I have a few sql clients that connects to
> > > my sql server through wireless connection. Sometimes, these wireless
> > > connections link is down for a few seconds. When user try to continue
> > > to run some query, the db process dead error message appears. Is the
> > > anyway to extend the time out setting to longer time so that this
> > > problem could be minimise?
> > >
> > > Thanks a million.
> > >
> >|||John,
When any activity happens on the client, it wakes up the ISDN connection and
should carry on where it left off in the application, but it looks like the
Client does not re-connect to the server correctly.
I'm not sure which SQL Server tools you refer to?
As for MDAC, it will be the one on the CD, should there be a later version?
The application is written in C++ not Powerbuilder. It is the database which
has been migrated to SQL Server from Sybase, and the old Sybase Open Client
did not report these errors on the same ISDN line.
Thanks,
M
"John Bell" wrote:
> Hi Marty
> Unless you have the SQL Server tools on the client PC then there is no point
> in using it on the client. You should make sure that a recent version of MDAC
> is on there, although I don't think this will cure the issue as the server
> can not reach the client and it can not instigate the ISDN connection.
> As Dan has stated you will need to handle the error and reconnect the client
> if you get this error.
> Has the client application changed from powerbuilder?
> John
> "Marty" wrote:
> > I have similar problems on some remote sites. Some are running the client
> > over ISDN which naturally timesout and should pick up the line again when
> > there is activity. But when the user generates some activity we get the db
> > process dead message. We migrated these sites from Sybase which never had
> > these issues and seemed more robust in these situations.
> >
> > Is there any config options we can use on the client or server to make the
> > connections less fickle?
> > Is there any updated client that might be more reliable?
> > We are using SQL Server 2000 Sp4 but the client is the one on the original
> > SQl Server 2000 CD.
> >
> > Thanks,
> >
> >
> >
> > "Dan Guzman" wrote:
> >
> > > The dbprocess dead error indicates a terminated connection rather than a
> > > timeout. The application needs to be smart enough to attempt to reconnect
> > > following the error.
> > >
> > > --
> > > Hope this helps.
> > >
> > > Dan Guzman
> > > SQL Server MVP
> > >
> > > <masterwee@.gmail.com> wrote in message
> > > news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> > > > Hi,
> > > >
> > > > I really need some help here. I have a few sql clients that connects to
> > > > my sql server through wireless connection. Sometimes, these wireless
> > > > connections link is down for a few seconds. When user try to continue
> > > > to run some query, the db process dead error message appears. Is the
> > > > anyway to extend the time out setting to longer time so that this
> > > > problem could be minimise?
> > > >
> > > > Thanks a million.
> > > >
> > >|||Hi Marty
Use the MDAC checker from
http://msdn.microsoft.com/data/ref/mdac/downloads/. MDAC can be updated
through other products such as XP SP1, so you may not be on the same version
at all sites. You will need to change the client application so that if the
error is detected the connection is closed and re-open it. I don't know if
the Open Client has the intellegence to silently reconnect or if it was
sending a keep alive.
John
"Marty" wrote:
> John,
> When any activity happens on the client, it wakes up the ISDN connection and
> should carry on where it left off in the application, but it looks like the
> Client does not re-connect to the server correctly.
> I'm not sure which SQL Server tools you refer to?
> As for MDAC, it will be the one on the CD, should there be a later version?
> The application is written in C++ not Powerbuilder. It is the database which
> has been migrated to SQL Server from Sybase, and the old Sybase Open Client
> did not report these errors on the same ISDN line.
> Thanks,
> M
>
> "John Bell" wrote:
> > Hi Marty
> >
> > Unless you have the SQL Server tools on the client PC then there is no point
> > in using it on the client. You should make sure that a recent version of MDAC
> > is on there, although I don't think this will cure the issue as the server
> > can not reach the client and it can not instigate the ISDN connection.
> >
> > As Dan has stated you will need to handle the error and reconnect the client
> > if you get this error.
> >
> > Has the client application changed from powerbuilder?
> >
> > John
> >
> > "Marty" wrote:
> >
> > > I have similar problems on some remote sites. Some are running the client
> > > over ISDN which naturally timesout and should pick up the line again when
> > > there is activity. But when the user generates some activity we get the db
> > > process dead message. We migrated these sites from Sybase which never had
> > > these issues and seemed more robust in these situations.
> > >
> > > Is there any config options we can use on the client or server to make the
> > > connections less fickle?
> > > Is there any updated client that might be more reliable?
> > > We are using SQL Server 2000 Sp4 but the client is the one on the original
> > > SQl Server 2000 CD.
> > >
> > > Thanks,
> > >
> > >
> > >
> > > "Dan Guzman" wrote:
> > >
> > > > The dbprocess dead error indicates a terminated connection rather than a
> > > > timeout. The application needs to be smart enough to attempt to reconnect
> > > > following the error.
> > > >
> > > > --
> > > > Hope this helps.
> > > >
> > > > Dan Guzman
> > > > SQL Server MVP
> > > >
> > > > <masterwee@.gmail.com> wrote in message
> > > > news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> > > > > Hi,
> > > > >
> > > > > I really need some help here. I have a few sql clients that connects to
> > > > > my sql server through wireless connection. Sometimes, these wireless
> > > > > connections link is down for a few seconds. When user try to continue
> > > > > to run some query, the db process dead error message appears. Is the
> > > > > anyway to extend the time out setting to longer time so that this
> > > > > problem could be minimise?
> > > > >
> > > > > Thanks a million.
> > > > >
> > > >

Extend the sql server management studio

I'm looking for info/documentation about writing plugins for the management studio.
i'd like to extend the interface, for instance, alter the interface to allow scripting of all indexes for a table, by adding that option to the table context menu.

i'm also looking for a way to create macros in the query editor, so i can have pressing tab after writing a short word expand to a pre-selected template.

any help appreciated.

Check the following URL....

add-in to SQL Server Management Studio

http://www.codeproject.com/useritems/enisey.asp?df=100&forumid=315231&exp=0&select=1908869

|||http://blogs.msdn.com/dtjones/archive/2005/11/16/493440.aspx you can as per Dan's blog out there, I believe your best bet would be to contact Microsoft dev.team for more information.

Extend the metadata

Hi,
I want to add more fields in report list. So instead of just showing the
report name and description, I want hyperlink to some other information as
well. Is it possible? if so how can I do that?
Any help would be highly appreciated
Regards,You can add additonal fields to the table on the report (where you drop the
report fields). Right mouse click on a column and add another column. Then
put some text in the field (like detail ...). I then make it blue and
underlined. The do a right mouse click, properties, advanced properties,
navigation tab and use the jump to URL.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mna" <mna@.somewhere.com> wrote in message
news:%230qKrQ4YFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I want to add more fields in report list. So instead of just showing the
> report name and description, I want hyperlink to some other information as
> well. Is it possible? if so how can I do that?
> Any help would be highly appreciated
> Regards,
>|||Thanks Bruce!
I think this is not what I wanted to know.
What I want to know is when I have created one report, it goes to the main
reports list. That list contains all the reports. Now on that list I want to
add additional columns so before running the report if users want to see
additional information they can do so. For example besides report name I
want to see who actually approved that report or what is the name of the
department this report belongs to.
Regards,
Nadeem
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:uugoGU5YFHA.1368@.tk2msftngp13.phx.gbl...
> You can add additonal fields to the table on the report (where you drop
the
> report fields). Right mouse click on a column and add another column. Then
> put some text in the field (like detail ...). I then make it blue and
> underlined. The do a right mouse click, properties, advanced properties,
> navigation tab and use the jump to URL.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "mna" <mna@.somewhere.com> wrote in message
> news:%230qKrQ4YFHA.2124@.TK2MSFTNGP14.phx.gbl...
> > Hi,
> > I want to add more fields in report list. So instead of just showing the
> > report name and description, I want hyperlink to some other information
as
> > well. Is it possible? if so how can I do that?
> >
> > Any help would be highly appreciated
> >
> > Regards,
> >
> >
>|||The data needs to come from somewhere. If you modify the xml it is being
rendered and any modifications are going to be ignored. I don't think they
would even be accessible by the time the report runs. If you can get the
extra information from a database then you can have an additional dataset
that you get this information from.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mna" <mna@.somewhere.com> wrote in message
news:eiiI8c9YFHA.3620@.TK2MSFTNGP09.phx.gbl...
> Thanks Bruce!
> I think this is not what I wanted to know.
> What I want to know is when I have created one report, it goes to the main
> reports list. That list contains all the reports. Now on that list I want
> to
> add additional columns so before running the report if users want to see
> additional information they can do so. For example besides report name I
> want to see who actually approved that report or what is the name of the
> department this report belongs to.
> Regards,
> Nadeem
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:uugoGU5YFHA.1368@.tk2msftngp13.phx.gbl...
>> You can add additonal fields to the table on the report (where you drop
> the
>> report fields). Right mouse click on a column and add another column.
>> Then
>> put some text in the field (like detail ...). I then make it blue and
>> underlined. The do a right mouse click, properties, advanced properties,
>> navigation tab and use the jump to URL.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "mna" <mna@.somewhere.com> wrote in message
>> news:%230qKrQ4YFHA.2124@.TK2MSFTNGP14.phx.gbl...
>> > Hi,
>> > I want to add more fields in report list. So instead of just showing
>> > the
>> > report name and description, I want hyperlink to some other information
> as
>> > well. Is it possible? if so how can I do that?
>> >
>> > Any help would be highly appreciated
>> >
>> > Regards,
>> >
>> >
>>
>

Extend search function

Hello

In my website I have a textbox to search some products, but it would like to extend my search-function so that it could find special characters.

For example:

When I search Mexico, I would like to find México.

Is there an easy way to do this?

Thanks in Advance
Wesley

Hi Wesley,

As far as I know, there is no way to achieve this automatically. The only way is write custom code to substitute the characters and search again.

Extend MSDE to Enterprise

I have a system that came with the MSDE database, because of the 2G limit I
am trying to point it to the enterprise version of SQL 2000. All connection
strings have been changed to the enterprise (With vendor help). The connec
tion is established and acc
ording to a trace from Profiler, all queries are running and inserting the d
ata in the right table. But there is no data in the tables! No errors eith
er.
One of my tests was to point it to another MSDE and it worked fine. What is
different between these two versions that will cause data not to be written
to the tables.
ThanksHi,
Can you insert few records in to the tables manually and see what is
happening. I feel that application is
still pointing towards a different database.
Thanks
Hari
MCDBA
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:4937BB3E-CD2B-4DA1-9C83-2C03E8470989@.microsoft.com...
> I have a system that came with the MSDE database, because of the 2G limit
I am trying to point it to the enterprise version of SQL 2000. All
connection strings have been changed to the enterprise (With vendor help).
The connection is established and according to a trace from Profiler, all
queries are running and inserting the data in the right table. But there is
no data in the tables! No errors either.
> One of my tests was to point it to another MSDE and it worked fine. What
is different between these two versions that will cause data not to be
written to the tables.
> Thanks|||It is pointing to the right DB because at first I pointed it to a DB that ha
d records and from the front end the viewer showed the Data (but did not ins
ert any) then, I pointed it to an empty DB and the viewer showed empty rows
and still wouldn't insert a
ny records. Are there any differences between MSDE and SQL to cause such th
ing?
Thanks
"Hari Prasad" wrote:

> Hi,
> Can you insert few records in to the tables manually and see what is
> happening. I feel that application is
> still pointing towards a different database.
>
> Thanks
> Hari
> MCDBA
> "Niles" <Niles@.discussions.microsoft.com> wrote in message
> news:4937BB3E-CD2B-4DA1-9C83-2C03E8470989@.microsoft.com...
> I am trying to point it to the enterprise version of SQL 2000. All
> connection strings have been changed to the enterprise (With vendor help).
> The connection is established and according to a trace from Profiler, all
> queries are running and inserting the data in the right table. But there
is
> no data in the tables! No errors either.
> is different between these two versions that will cause data not to be
> written to the tables.
>
>

Extend MSDE to Enterprise

I have a system that came with the MSDE database, because of the 2G limit I am trying to point it to the enterprise version of SQL 2000. All connection strings have been changed to the enterprise (With vendor help). The connection is established and acc
ording to a trace from Profiler, all queries are running and inserting the data in the right table. But there is no data in the tables! No errors either.
One of my tests was to point it to another MSDE and it worked fine. What is different between these two versions that will cause data not to be written to the tables.
Thanks
Hi,
Can you insert few records in to the tables manually and see what is
happening. I feel that application is
still pointing towards a different database.
Thanks
Hari
MCDBA
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:4937BB3E-CD2B-4DA1-9C83-2C03E8470989@.microsoft.com...
> I have a system that came with the MSDE database, because of the 2G limit
I am trying to point it to the enterprise version of SQL 2000. All
connection strings have been changed to the enterprise (With vendor help).
The connection is established and according to a trace from Profiler, all
queries are running and inserting the data in the right table. But there is
no data in the tables! No errors either.
> One of my tests was to point it to another MSDE and it worked fine. What
is different between these two versions that will cause data not to be
written to the tables.
> Thanks
|||It is pointing to the right DB because at first I pointed it to a DB that had records and from the front end the viewer showed the Data (but did not insert any) then, I pointed it to an empty DB and the viewer showed empty rows and still wouldn't insert a
ny records. Are there any differences between MSDE and SQL to cause such thing?
Thanks
"Hari Prasad" wrote:

> Hi,
> Can you insert few records in to the tables manually and see what is
> happening. I feel that application is
> still pointing towards a different database.
>
> Thanks
> Hari
> MCDBA
> "Niles" <Niles@.discussions.microsoft.com> wrote in message
> news:4937BB3E-CD2B-4DA1-9C83-2C03E8470989@.microsoft.com...
> I am trying to point it to the enterprise version of SQL 2000. All
> connection strings have been changed to the enterprise (With vendor help).
> The connection is established and according to a trace from Profiler, all
> queries are running and inserting the data in the right table. But there is
> no data in the tables! No errors either.
> is different between these two versions that will cause data not to be
> written to the tables.
>
>

Extend MSDE to Enterprise

I have a system that came with the MSDE database, because of the 2G limit I am trying to point it to the enterprise version of SQL 2000. All connection strings have been changed to the enterprise (With vendor help). The connection is established and according to a trace from Profiler, all queries are running and inserting the data in the right table. But there is no data in the tables! No errors either.
One of my tests was to point it to another MSDE and it worked fine. What is different between these two versions that will cause data not to be written to the tables.
ThanksHi,
Can you insert few records in to the tables manually and see what is
happening. I feel that application is
still pointing towards a different database.
Thanks
Hari
MCDBA
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:4937BB3E-CD2B-4DA1-9C83-2C03E8470989@.microsoft.com...
> I have a system that came with the MSDE database, because of the 2G limit
I am trying to point it to the enterprise version of SQL 2000. All
connection strings have been changed to the enterprise (With vendor help).
The connection is established and according to a trace from Profiler, all
queries are running and inserting the data in the right table. But there is
no data in the tables! No errors either.
> One of my tests was to point it to another MSDE and it worked fine. What
is different between these two versions that will cause data not to be
written to the tables.
> Thanks

Extend existing report items

Hi,

I'm totally new to SSRS2005 and I was wondering if I could extend the existing report items. For instance, I'd like to add a few extra properties to the textbox report item. I tried wrting a custom Textbox control that inherits from System.Windows.Forms.Textbox. When I imported the dll in VS, the new textbox showed up in the toolbox, but it was grayed out.

Any idea what I'm missing here?

Thanks,
Phil
Best off writing your own and call the RS webservice.

http://msdn2.microsoft.com/en-us/library/aa179578(SQL.80).aspx|||But I want to inherit all existing functionality of the textbox... So why would I create my own from scratch?
|||Sorry, completely barking up the wrong end of the stick.

I was on about report parameter selection.

I'm guessing you can't do it.

Use Crystal Reports instead: from what I have read on these forums, it seems to do most things that RS can't.

The only reason people use RS is because they are too tight to shell out for a decent product (this has been the case where I've worked)

RS is "free". How much time have I wasted at what cost to the companies I have worked for trying to get it to do the simplest of things. Suddenly it's not so cheap, but then MS have figured out that bean counters are incapable of factoring in all this wasted time.

If only dev's got to make the purchasing decisions......

Extend CSV Rendering

Is there anyway to extend the existing CSV rending to change deviceinfo
settings that would be used when export is selected from the standard
ReportServer interface.
Example would be to have TXT rendering capability that used the CSV
rendering components, but changed the deviceinfo settings so that
Extension=txt, FieldDelimiter=|. I want to use the parameter selection
capability, and then allow the user to export to this TXT format instead of
CSV.
Logically I would think that you could added some DeviceInfo settings to the
config file in the Report Service directory where Render is defined. But I
am unable to find any sort of documentation.
Also the BOL talks about extending existing rendering formats, as opposed to
create custom rendering extensions. I have yet to find out how it is
possible to extend the CSV rendering extension to accomplish this. I really
want to be able to leverage the existing CSV rendering extension, to modify
a couple of settings.
I know that this can be done via URL and Hidden values in the calling web
page that shells the Report Services window. But when you click the Export
functionality and pick CSV none of the CSV deviceinfo settings are carried
forward to the Export window that is opened before prompting to Save or Open
the file.
Thanks,
MikeUnfortunately, we do not support setting the device info through report
manager.
Regarding the BOL reference to extending rather than writing your own: I
think this might just be a case of terminology confusion. You cannot extend
a particular format. You can extend the report server by adding your own
formats. I'll see about getting the wording changed.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael McCallum" <mmccallum@.honovi.net> wrote in message
news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
> Is there anyway to extend the existing CSV rending to change deviceinfo
> settings that would be used when export is selected from the standard
> ReportServer interface.
> Example would be to have TXT rendering capability that used the CSV
> rendering components, but changed the deviceinfo settings so that
> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
> capability, and then allow the user to export to this TXT format instead
> of CSV.
> Logically I would think that you could added some DeviceInfo settings to
> the config file in the Report Service directory where Render is defined.
> But I am unable to find any sort of documentation.
> Also the BOL talks about extending existing rendering formats, as opposed
> to create custom rendering extensions. I have yet to find out how it is
> possible to extend the CSV rendering extension to accomplish this. I
> really want to be able to leverage the existing CSV rendering extension,
> to modify a couple of settings.
> I know that this can be done via URL and Hidden values in the calling web
> page that shells the Report Services window. But when you click the
> Export functionality and pick CSV none of the CSV deviceinfo settings are
> carried forward to the Export window that is opened before prompting to
> Save or Open the file.
> Thanks,
> Mike
>|||Thanks for the information. Maybe this could be a wishlist type item?
Mike
"Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
> Unfortunately, we do not support setting the device info through report
> manager.
> Regarding the BOL reference to extending rather than writing your own: I
> think this might just be a case of terminology confusion. You cannot
> extend a particular format. You can extend the report server by adding
> your own formats. I'll see about getting the wording changed.
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
>> Is there anyway to extend the existing CSV rending to change deviceinfo
>> settings that would be used when export is selected from the standard
>> ReportServer interface.
>> Example would be to have TXT rendering capability that used the CSV
>> rendering components, but changed the deviceinfo settings so that
>> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
>> capability, and then allow the user to export to this TXT format instead
>> of CSV.
>> Logically I would think that you could added some DeviceInfo settings to
>> the config file in the Report Service directory where Render is defined.
>> But I am unable to find any sort of documentation.
>> Also the BOL talks about extending existing rendering formats, as opposed
>> to create custom rendering extensions. I have yet to find out how it is
>> possible to extend the CSV rendering extension to accomplish this. I
>> really want to be able to leverage the existing CSV rendering extension,
>> to modify a couple of settings.
>> I know that this can be done via URL and Hidden values in the calling web
>> page that shells the Report Services window. But when you click the
>> Export functionality and pick CSV none of the CSV deviceinfo settings are
>> carried forward to the Export window that is opened before prompting to
>> Save or Open the file.
>> Thanks,
>> Mike
>|||Yes, we plan (at some point :-)) to expose UI around device info settings.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael McCallum" <mmccallum@.honovi.com> wrote in message
news:%23oBG%234OGFHA.1836@.tk2msftngp13.phx.gbl...
> Thanks for the information. Maybe this could be a wishlist type item?
> Mike
> "Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
> news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
>> Unfortunately, we do not support setting the device info through report
>> manager.
>> Regarding the BOL reference to extending rather than writing your own: I
>> think this might just be a case of terminology confusion. You cannot
>> extend a particular format. You can extend the report server by adding
>> your own formats. I'll see about getting the wording changed.
>> -Lukasz
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
>> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
>> Is there anyway to extend the existing CSV rending to change deviceinfo
>> settings that would be used when export is selected from the standard
>> ReportServer interface.
>> Example would be to have TXT rendering capability that used the CSV
>> rendering components, but changed the deviceinfo settings so that
>> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
>> capability, and then allow the user to export to this TXT format instead
>> of CSV.
>> Logically I would think that you could added some DeviceInfo settings to
>> the config file in the Report Service directory where Render is defined.
>> But I am unable to find any sort of documentation.
>> Also the BOL talks about extending existing rendering formats, as
>> opposed to create custom rendering extensions. I have yet to find out
>> how it is possible to extend the CSV rendering extension to accomplish
>> this. I really want to be able to leverage the existing CSV rendering
>> extension, to modify a couple of settings.
>> I know that this can be done via URL and Hidden values in the calling
>> web page that shells the Report Services window. But when you click the
>> Export functionality and pick CSV none of the CSV deviceinfo settings
>> are carried forward to the Export window that is opened before prompting
>> to Save or Open the file.
>> Thanks,
>> Mike
>>
>|||Lukasz, Is there any complexity in rendering dynamically generated matrix
total columns in CSV format? I have been having this problem that when I
export my reports to CSV, if a matrix in the report has column groupings as
well as dynamic total columns, these total columns don't generate in CSV
version. I was thinking of writing my own CSV renderer but then I thought
there's probably a complexity into that, otherwise the Microsoft CSV renderer
would do it. Is that right? Or do you think CSV rendere just wasn't intended
to render dynamic columns in a matrix?
"Lukasz Pawlowski [MSFT]" wrote:
> Yes, we plan (at some point :-)) to expose UI around device info settings.
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Michael McCallum" <mmccallum@.honovi.com> wrote in message
> news:%23oBG%234OGFHA.1836@.tk2msftngp13.phx.gbl...
> > Thanks for the information. Maybe this could be a wishlist type item?
> > Mike
> >
> > "Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
> > news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
> >> Unfortunately, we do not support setting the device info through report
> >> manager.
> >>
> >> Regarding the BOL reference to extending rather than writing your own: I
> >> think this might just be a case of terminology confusion. You cannot
> >> extend a particular format. You can extend the report server by adding
> >> your own formats. I'll see about getting the wording changed.
> >>
> >> -Lukasz
> >>
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >>
> >> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
> >> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
> >> Is there anyway to extend the existing CSV rending to change deviceinfo
> >> settings that would be used when export is selected from the standard
> >> ReportServer interface.
> >>
> >> Example would be to have TXT rendering capability that used the CSV
> >> rendering components, but changed the deviceinfo settings so that
> >> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
> >> capability, and then allow the user to export to this TXT format instead
> >> of CSV.
> >>
> >> Logically I would think that you could added some DeviceInfo settings to
> >> the config file in the Report Service directory where Render is defined.
> >> But I am unable to find any sort of documentation.
> >>
> >> Also the BOL talks about extending existing rendering formats, as
> >> opposed to create custom rendering extensions. I have yet to find out
> >> how it is possible to extend the CSV rendering extension to accomplish
> >> this. I really want to be able to leverage the existing CSV rendering
> >> extension, to modify a couple of settings.
> >>
> >> I know that this can be done via URL and Hidden values in the calling
> >> web page that shells the Report Services window. But when you click the
> >> Export functionality and pick CSV none of the CSV deviceinfo settings
> >> are carried forward to the Export window that is opened before prompting
> >> to Save or Open the file.
> >>
> >> Thanks,
> >> Mike
> >>
> >>
> >>
> >
> >
>
>