describe OK- select not

Hello,
I am connecting to SQLserver via an application running on linux.
Under the hood it does a describe which brings back the field types
for any table OK.
a select always fails (no data returned) however. I am troubleshooting
this remotely and have asked the MSSQL dba to run a select with the
same user id/password that I use on the client - this succeeds.
There is a firewall between client and db, but I guess this is OK cos
the describe succeeds.
Anything I can ask the dba to do or check to help diagnose the
problem? Does it follow that if userid is good for selects on MS box
it will be good for remote queries?
TIA
TonTry connecting to the DB remotely via Query Analyzer. I know you are on
Linux , so can you see if you can connect from a Windows, with the
username/password and run the SELECT . Does it return results?
--
Jack Vamvas
___________________________________
Need an IT job? http://www.ITjobfeed.com/SQL
"ton de w" <ton_de_winter@.yahoo.co.uk> wrote in message
news:1190367783.673561.160950@.22g2000hsm.googlegroups.com...
> Hello,
> I am connecting to SQLserver via an application running on linux.
> Under the hood it does a describe which brings back the field types
> for any table OK.
> a select always fails (no data returned) however. I am troubleshooting
> this remotely and have asked the MSSQL dba to run a select with the
> same user id/password that I use on the client - this succeeds.
> There is a firewall between client and db, but I guess this is OK cos
> the describe succeeds.
> Anything I can ask the dba to do or check to help diagnose the
> problem? Does it follow that if userid is good for selects on MS box
> it will be good for remote queries?
> TIA
> Ton
>|||On 21 Sep, 11:23, "Jack Vamvas" <DEL_TO_RE...@.del.com> wrote:
> Try connecting to the DB remotely via Query Analyzer. I know you are on
> Linux , so can you see if you can connect from a Windows, with the
> username/password and run the SELECT . Does it return results?
> --
> Jack Vamvas
> ___________________________________
> Need an IT job? http://www.ITjobfeed.com/SQL
> "ton de w" <ton_de_win...@.yahoo.co.uk> wrote in messagenews:1190367783.673561.160950@.22g2000hsm.googlegroups.com...
>
> > Hello,
> > I am connecting to SQLserver via an application running on linux.
> > Under the hood it does a describe which brings back the field types
> > for any table OK.
> > a select always fails (no data returned) however. I am troubleshooting
> > this remotely and have asked the MSSQL dba to run a select with the
> > same user id/password that I use on the client - this succeeds.
> > There is a firewall between client and db, but I guess this is OK cos
> > the describe succeeds.
> > Anything I can ask the dba to do or check to help diagnose the
> > problem? Does it follow that if userid is good for selects on MS box
> > it will be good for remote queries?
> > TIA
> > Ton- Hide quoted text -
> - Show quoted text -
Thanks for that Query Analyzer works well with userid/password
So does linux commandline tool tsql which allows me to pull back the
data with a "select * from tablename" - it just needs the !P port
username and password to logon.
This works fine.
However the application I am dealing with does not bring the data back
<sigh>
I am not sure how tsql gets the data without a databasename ie i would
have expected "select * from tablename" to fail and a select * from
databasename.tablename to succeed - perhaps cos of my Oracle
experience.
The application that is failing needs the database name before it will
log on OK. but "select * from tablename" generates a syntax error near
FROM - and so does a "select * from databasename.tablename"|||Ton,
sql server's specification of table in a select statement can have up to
four parts. In addition to the name itself, you can have / may need three
qualifiers:
select column_list from server_name.database_name.schema_name.table_name.
It is recommended if you are in the database where the table is located, you
use the schema_name (also know as owner) to qualify the table. If you are
not in the database where the table is, you need to add the database name
too, and then (better) specify the schema as well, which can be omitted if
it is dbo (such as mydb..mytalbe). If you are accessing a liked server, you
then also need to specify the server name.
In your case, if your default database is where the table is located, when
you establish the connection, you can directly run a select * from
tablename. But select * from databasename.tablename will never work unless
the databasename is the same as the schema name by accident, in which case
sql server considers you were doing a select * from schemaname.tablename.
hth
Quentin
"ton de w" <ton_de_winter@.yahoo.co.uk> wrote in message
news:1190390145.227481.285540@.g4g2000hsf.googlegroups.com...
> On 21 Sep, 11:23, "Jack Vamvas" <DEL_TO_RE...@.del.com> wrote:
>> Try connecting to the DB remotely via Query Analyzer. I know you are on
>> Linux , so can you see if you can connect from a Windows, with the
>> username/password and run the SELECT . Does it return results?
>> --
>> Jack Vamvas
>> ___________________________________
>> Need an IT job? http://www.ITjobfeed.com/SQL
>> "ton de w" <ton_de_win...@.yahoo.co.uk> wrote in
>> messagenews:1190367783.673561.160950@.22g2000hsm.googlegroups.com...
>>
>> > Hello,
>> > I am connecting to SQLserver via an application running on linux.
>> > Under the hood it does a describe which brings back the field types
>> > for any table OK.
>> > a select always fails (no data returned) however. I am troubleshooting
>> > this remotely and have asked the MSSQL dba to run a select with the
>> > same user id/password that I use on the client - this succeeds.
>> > There is a firewall between client and db, but I guess this is OK cos
>> > the describe succeeds.
>> > Anything I can ask the dba to do or check to help diagnose the
>> > problem? Does it follow that if userid is good for selects on MS box
>> > it will be good for remote queries?
>> > TIA
>> > Ton- Hide quoted text -
>> - Show quoted text -
> Thanks for that Query Analyzer works well with userid/password
> So does linux commandline tool tsql which allows me to pull back the
> data with a "select * from tablename" - it just needs the !P port
> username and password to logon.
> This works fine.
> However the application I am dealing with does not bring the data back
> <sigh>
> I am not sure how tsql gets the data without a databasename ie i would
> have expected "select * from tablename" to fail and a select * from
> databasename.tablename to succeed - perhaps cos of my Oracle
> experience.
> The application that is failing needs the database name before it will
> log on OK. but "select * from tablename" generates a syntax error near
> FROM - and so does a "select * from databasename.tablename"
>
>|||On 21 Sep, 17:20, "Quentin Ran" <remove_qr...@.yahoo.com> wrote:
> Ton,
> sql server's specification of table in a select statement can have up to
> four parts. In addition to the name itself, you can have / may need three
> qualifiers:
> select column_list from server_name.database_name.schema_name.table_name.
> It is recommended if you are in the database where the table is located, you
> use the schema_name (also know as owner) to qualify the table. If you are
> not in the database where the table is, you need to add the database name
> too, and then (better) specify the schema as well, which can be omitted if
> it is dbo (such as mydb..mytalbe). If you are accessing a liked server, you
> then also need to specify the server name.
> In your case, if your default database is where the table is located, when
> you establish the connection, you can directly run a select * from
> tablename. But select * from databasename.tablename will never work unless
> the databasename is the same as the schema name by accident, in which case
> sql server considers you were doing a select * from schemaname.tablename.
> hth
> Quentin
> "ton de w" <ton_de_win...@.yahoo.co.uk> wrote in messagenews:1190390145.227481.285540@.g4g2000hsf.googlegroups.com...
>
> > On 21 Sep, 11:23, "Jack Vamvas" <DEL_TO_RE...@.del.com> wrote:
> >> Try connecting to the DB remotely via Query Analyzer. I know you are on
> >> Linux , so can you see if you can connect from a Windows, with the
> >> username/password and run the SELECT . Does it return results?
> >> --
> >> Jack Vamvas
> >> ___________________________________
> >> Need an IT job? http://www.ITjobfeed.com/SQL
> >> "ton de w" <ton_de_win...@.yahoo.co.uk> wrote in
> >> messagenews:1190367783.673561.160950@.22g2000hsm.googlegroups.com...
> >> > Hello,
> >> > I am connecting to SQLserver via an application running on linux.
> >> > Under the hood it does a describe which brings back the field types
> >> > for any table OK.
> >> > a select always fails (no data returned) however. I am troubleshooting
> >> > this remotely and have asked the MSSQL dba to run a select with the
> >> > same user id/password that I use on the client - this succeeds.
> >> > There is a firewall between client and db, but I guess this is OK cos
> >> > the describe succeeds.
> >> > Anything I can ask the dba to do or check to help diagnose the
> >> > problem? Does it follow that if userid is good for selects on MS box
> >> > it will be good for remote queries?
> >> > TIA
> >> > Ton- Hide quoted text -
> >> - Show quoted text -
> > Thanks for that Query Analyzer works well with userid/password
> > So does linux commandline tool tsql which allows me to pull back the
> > data with a "select * from tablename" - it just needs the !P port
> > username and password to logon.
> > This works fine.
> > However the application I am dealing with does not bring the data back
> > <sigh>
> > I am not sure how tsql gets the data without a databasename ie i would
> > have expected "select * from tablename" to fail and a select * from
> > databasename.tablename to succeed - perhaps cos of my Oracle
> > experience.
> > The application that is failing needs the database name before it will
> > log on OK. but "select * from tablename" generates a syntax error near
> > FROM - and so does a "select * from databasename.tablename"- Hide quoted text -
> - Show quoted text -
Gosh just what I need to know - thanks very much!
I have an idea I am going to meet a few more problems along the way
tho.
Can I ask the MSSQL dba to capture incoming queries to help me with
troubleshooting BTW?|||yes, get them to run a Profiler trace - asking to then to filter just on
your DatabaseId and Database name.
--
Jack Vamvas
___________________________________
Need an IT job? http://www.ITjobfeed.com/SQL
"ton de w" <ton_de_winter@.yahoo.co.uk> wrote in message
news:1190581978.259876.259490@.d55g2000hsg.googlegroups.com...
> On 21 Sep, 17:20, "Quentin Ran" <remove_qr...@.yahoo.com> wrote:
>> Ton,
>> sql server's specification of table in a select statement can have up to
>> four parts. In addition to the name itself, you can have / may need
>> three
>> qualifiers:
>> select column_list from server_name.database_name.schema_name.table_name.
>> It is recommended if you are in the database where the table is located,
>> you
>> use the schema_name (also know as owner) to qualify the table. If you
>> are
>> not in the database where the table is, you need to add the database name
>> too, and then (better) specify the schema as well, which can be omitted
>> if
>> it is dbo (such as mydb..mytalbe). If you are accessing a liked server,
>> you
>> then also need to specify the server name.
>> In your case, if your default database is where the table is located,
>> when
>> you establish the connection, you can directly run a select * from
>> tablename. But select * from databasename.tablename will never work
>> unless
>> the databasename is the same as the schema name by accident, in which
>> case
>> sql server considers you were doing a select * from schemaname.tablename.
>> hth
>> Quentin
>> "ton de w" <ton_de_win...@.yahoo.co.uk> wrote in
>> messagenews:1190390145.227481.285540@.g4g2000hsf.googlegroups.com...
>>
>> > On 21 Sep, 11:23, "Jack Vamvas" <DEL_TO_RE...@.del.com> wrote:
>> >> Try connecting to the DB remotely via Query Analyzer. I know you are
>> >> on
>> >> Linux , so can you see if you can connect from a Windows, with the
>> >> username/password and run the SELECT . Does it return results?
>> >> --
>> >> Jack Vamvas
>> >> ___________________________________
>> >> Need an IT job? http://www.ITjobfeed.com/SQL
>> >> "ton de w" <ton_de_win...@.yahoo.co.uk> wrote in
>> >> messagenews:1190367783.673561.160950@.22g2000hsm.googlegroups.com...
>> >> > Hello,
>> >> > I am connecting to SQLserver via an application running on linux.
>> >> > Under the hood it does a describe which brings back the field types
>> >> > for any table OK.
>> >> > a select always fails (no data returned) however. I am
>> >> > troubleshooting
>> >> > this remotely and have asked the MSSQL dba to run a select with the
>> >> > same user id/password that I use on the client - this succeeds.
>> >> > There is a firewall between client and db, but I guess this is OK
>> >> > cos
>> >> > the describe succeeds.
>> >> > Anything I can ask the dba to do or check to help diagnose the
>> >> > problem? Does it follow that if userid is good for selects on MS box
>> >> > it will be good for remote queries?
>> >> > TIA
>> >> > Ton- Hide quoted text -
>> >> - Show quoted text -
>> > Thanks for that Query Analyzer works well with userid/password
>> > So does linux commandline tool tsql which allows me to pull back the
>> > data with a "select * from tablename" - it just needs the !P port
>> > username and password to logon.
>> > This works fine.
>> > However the application I am dealing with does not bring the data back
>> > <sigh>
>> > I am not sure how tsql gets the data without a databasename ie i would
>> > have expected "select * from tablename" to fail and a select * from
>> > databasename.tablename to succeed - perhaps cos of my Oracle
>> > experience.
>> > The application that is failing needs the database name before it will
>> > log on OK. but "select * from tablename" generates a syntax error near
>> > FROM - and so does a "select * from databasename.tablename"- Hide
>> > quoted text -
>> - Show quoted text -
> Gosh just what I need to know - thanks very much!
> I have an idea I am going to meet a few more problems along the way
> tho.
> Can I ask the MSSQL dba to capture incoming queries to help me with
> troubleshooting BTW?
>
>

Deployment with SQL

Hi,

I have a project that uses SQL 2000 for the database. It is finished and I am looking for the best way to deploy it via CD.
I am mainly worried about getting the SQL database to install correctly automatically and have it work correctly with the web application.
Any suggestions?

Thanks,

Mikeare you shipping sql server with your application on a cd ?

Deploying Reports to a New Server

I developed some reports on one system that I would like to move to another
system. I copied the rdl file to the new system and uploaded it via Report
Manager.
The data source the report uses is based upon SQL views which I created on
the new server.
I'm having a problem with the data source. I've tried creating a new custom
data source by going to the properties of the report and clicking on Data
Sources. I've also tried creating a new data source by clicking New Data
Source from the home page of the Reports.
I've received login errors using the sa account and I've seen that, despite
picking a new data source, it still seems to use the old data source.
What do I need to do to point the report to a the current server's data?
--
Charles Allen, MVPIf both the servers are accessible on your network, just go to report project
properties and change the server to your new server and deploy it, instead of
you doing it does the job perfectly, including datasource..
Amarnath
"Charles Allen" wrote:
> I developed some reports on one system that I would like to move to another
> system. I copied the rdl file to the new system and uploaded it via Report
> Manager.
> The data source the report uses is based upon SQL views which I created on
> the new server.
> I'm having a problem with the data source. I've tried creating a new custom
> data source by going to the properties of the report and clicking on Data
> Sources. I've also tried creating a new data source by clicking New Data
> Source from the home page of the Reports.
> I've received login errors using the sa account and I've seen that, despite
> picking a new data source, it still seems to use the old data source.
> What do I need to do to point the report to a the current server's data?
> --
> Charles Allen, MVP
>|||Thank you for replying quickly.
In this case, the machines are not on the same network. One is a test
environment I use and the other is a client's production system.
--
Charles Allen, MVP
"Amarnath" wrote:
> If both the servers are accessible on your network, just go to report project
> properties and change the server to your new server and deploy it, instead of
> you doing it does the job perfectly, including datasource..
> Amarnath
> "Charles Allen" wrote:
> > I developed some reports on one system that I would like to move to another
> > system. I copied the rdl file to the new system and uploaded it via Report
> > Manager.
> >
> > The data source the report uses is based upon SQL views which I created on
> > the new server.
> >
> > I'm having a problem with the data source. I've tried creating a new custom
> > data source by going to the properties of the report and clicking on Data
> > Sources. I've also tried creating a new data source by clicking New Data
> > Source from the home page of the Reports.
> >
> > I've received login errors using the sa account and I've seen that, despite
> > picking a new data source, it still seems to use the old data source.
> >
> > What do I need to do to point the report to a the current server's data?
> > --
> > Charles Allen, MVP
> >|||ok, MS has provided a sample script on "how to deploy the reports using
command prompt", you can have a look at that sample for your solution.
Amarnath
"Charles Allen" wrote:
> Thank you for replying quickly.
> In this case, the machines are not on the same network. One is a test
> environment I use and the other is a client's production system.
> --
> Charles Allen, MVP
>
> "Amarnath" wrote:
> > If both the servers are accessible on your network, just go to report project
> > properties and change the server to your new server and deploy it, instead of
> > you doing it does the job perfectly, including datasource..
> >
> > Amarnath
> >
> > "Charles Allen" wrote:
> >
> > > I developed some reports on one system that I would like to move to another
> > > system. I copied the rdl file to the new system and uploaded it via Report
> > > Manager.
> > >
> > > The data source the report uses is based upon SQL views which I created on
> > > the new server.
> > >
> > > I'm having a problem with the data source. I've tried creating a new custom
> > > data source by going to the properties of the report and clicking on Data
> > > Sources. I've also tried creating a new data source by clicking New Data
> > > Source from the home page of the Reports.
> > >
> > > I've received login errors using the sa account and I've seen that, despite
> > > picking a new data source, it still seems to use the old data source.
> > >
> > > What do I need to do to point the report to a the current server's data?
> > > --
> > > Charles Allen, MVP
> > >

Deploying Reports to a different Environment

I am developing some reports and the only way I can deploy the reports to
the production server is via files on a CD.
The project manager would like to encapsulate everything into an .MSI file
for deployment.
Is there any documentation on whether this can be done? or how to go about
deploying reports when all I have is a bunch of files
Thanks
BobYou can deploy using RM from VS or through scripts. Best way for you is to
create scripts and put it in a batch file.
Amarnath,MCTS
"Bob" wrote:
> I am developing some reports and the only way I can deploy the reports to
> the production server is via files on a CD.
> The project manager would like to encapsulate everything into an .MSI file
> for deployment.
> Is there any documentation on whether this can be done? or how to go about
> deploying reports when all I have is a bunch of files
> Thanks
> Bob
>
>

Deploy Reports via Visual Studio 2005

This seems to be a basic issue, but I am having a problem trying to deploy a report to Reporting Services.

I have setup the deployment options under the properties of the Project. But each time I try to deploy a report, I get "The request failed with HTTP status 504: Gateway Time-out"

When I try to connect to connect directly to the TargetServerURL via a web browser from my client or the server itself, I can browse the structure fine. Not sure why I can't deploy via Visual Studio.

Thoughts?

Thanks

This is a guess but it sounds like it could be a problem with a proxy server. Your browser is usually set up to handle requests through a proxy transparently. Visual Studio is not. Does the target server exist outside of your firewall?|||

To localize the test, I put the system running the Visual Studio on the same subnet. It's wide open with NO ACL control or routing from that point.

|||Are you still getting the same error? If you are on the same subnet, the request shouldn't be using a gateway.|||yes, same issue exists.|||try opening a command window and running "tracert <reportserver ip>" this will show you how requests are being routed to your report server. If the ip address of the report server isn't the first on the list, you are using some kind of proxy or gateway to get to the report server.

Deploy Reports via Visual Studio 2005

This seems to be a basic issue, but I am having a problem trying to deploy a report to Reporting Services.

I have setup the deployment options under the properties of the Project. But each time I try to deploy a report, I get "The request failed with HTTP status 504: Gateway Time-out"

When I try to connect to connect directly to the TargetServerURL via a web browser from my client or the server itself, I can browse the structure fine. Not sure why I can't deploy via Visual Studio.

Thoughts?

Thanks

This is a guess but it sounds like it could be a problem with a proxy server. Your browser is usually set up to handle requests through a proxy transparently. Visual Studio is not. Does the target server exist outside of your firewall?|||

To localize the test, I put the system running the Visual Studio on the same subnet. It's wide open with NO ACL control or routing from that point.

|||Are you still getting the same error? If you are on the same subnet, the request shouldn't be using a gateway.|||yes, same issue exists.|||try opening a command window and running "tracert <reportserver ip>" this will show you how requests are being routed to your report server. If the ip address of the report server isn't the first on the list, you are using some kind of proxy or gateway to get to the report server.

Deploy Reports via Visual Studio 2005

This seems to be a basic issue, but I am having a problem trying to deploy a report to Reporting Services.

I have setup the deployment options under the properties of the Project. But each time I try to deploy a report, I get "The request failed with HTTP status 504: Gateway Time-out"

When I try to connect to connect directly to the TargetServerURL via a web browser from my client or the server itself, I can browse the structure fine. Not sure why I can't deploy via Visual Studio.

Thoughts?

Thanks

This is a guess but it sounds like it could be a problem with a proxy server. Your browser is usually set up to handle requests through a proxy transparently. Visual Studio is not. Does the target server exist outside of your firewall?|||

To localize the test, I put the system running the Visual Studio on the same subnet. It's wide open with NO ACL control or routing from that point.

|||Are you still getting the same error? If you are on the same subnet, the request shouldn't be using a gateway.|||yes, same issue exists.|||try opening a command window and running "tracert <reportserver ip>" this will show you how requests are being routed to your report server. If the ip address of the report server isn't the first on the list, you are using some kind of proxy or gateway to get to the report server.

deploy reports directly into right folders

hi,
is it possible to deploy an report directly to a folder from the
business intellegence studio?
or can I only move reports via the Report Manager?
Thanks!Hi,
Create a folder in the Report Manager and specify the folder name and
target url in the project properties.
This automatically move the reports to the desired folder when u deploy
that report.
Thanks.
florian wrote:
> hi,
> is it possible to deploy an report directly to a folder from the
> business intellegence studio?
> or can I only move reports via the Report Manager?
> Thanks!|||but what if I have a project with several reports belonging to
different folders?
Sara schrieb:
> Hi,
> Create a folder in the Report Manager and specify the folder name and
> target url in the project properties.
> This automatically move the reports to the desired folder when u deploy
> that report.
> Thanks.
> florian wrote:
> > hi,
> >
> > is it possible to deploy an report directly to a folder from the
> > business intellegence studio?
> >
> > or can I only move reports via the Report Manager?
> >
> > Thanks!|||Yeah, that's what I want to know. I have the same thing, one project with 10
reports in it. 3 of the reports go in their own folder.
I guess you could argue that because the reports have their own folder in
the UI that they should have their own project. But then that raises the
issue of having to duplicate your shared data sources. As of yet I have not
found a way to share data sources across projects withing the same solution
in VS.Net 2003.
"florian" wrote:
> but what if I have a project with several reports belonging to
> different folders?
> Sara schrieb:
> > Hi,
> > Create a folder in the Report Manager and specify the folder name and
> > target url in the project properties.
> >
> > This automatically move the reports to the desired folder when u deploy
> > that report.
> >
> > Thanks.
> > florian wrote:
> > > hi,
> > >
> > > is it possible to deploy an report directly to a folder from the
> > > business intellegence studio?
> > >
> > > or can I only move reports via the Report Manager?
> > >
> > > Thanks!
>

Deploy a data source via Report Manager

You can deploy both reports and the data sources used by
them in Report Designer. You can also deploy reports by
uploading them in Report Manager. But I can't find a way
to deploy data sources (not creating new data sources)
using Report Manager.
Ideally, when the developers have finished designing and
testing reports, I'd like to have them sending me both rdl
files and rds files so that I can deploy them into
production.
Can I deploy data sources using Report Manager?
JoeHi, data srouces are files with the .rds extension. I think you can deploy
them by uploading them using report manager.
Cédric
"Joe Bourne" <anonymous@.discussions.microsoft.com> wrote in message
news:86a501c4783b$85c5e8c0$a401280a@.phx.gbl...
> You can deploy both reports and the data sources used by
> them in Report Designer. You can also deploy reports by
> uploading them in Report Manager. But I can't find a way
> to deploy data sources (not creating new data sources)
> using Report Manager.
> Ideally, when the developers have finished designing and
> testing reports, I'd like to have them sending me both rdl
> files and rds files so that I can deploy them into
> production.
> Can I deploy data sources using Report Manager?
> Joe
>|||If you upload a rds file using Report Manager, you just get a file, not a
data source. Are you sure that'll work?
Joe
"Cédric Naudy" <cnaudy@.online.microsoft.com> wrote in message
news:OaWljfKeEHA.332@.TK2MSFTNGP09.phx.gbl...
> Hi, data srouces are files with the .rds extension. I think you can deploy
> them by uploading them using report manager.
> Cédric
> "Joe Bourne" <anonymous@.discussions.microsoft.com> wrote in message
> news:86a501c4783b$85c5e8c0$a401280a@.phx.gbl...
> > You can deploy both reports and the data sources used by
> > them in Report Designer. You can also deploy reports by
> > uploading them in Report Manager. But I can't find a way
> > to deploy data sources (not creating new data sources)
> > using Report Manager.
> >
> > Ideally, when the developers have finished designing and
> > testing reports, I'd like to have them sending me both rdl
> > files and rds files so that I can deploy them into
> > production.
> >
> > Can I deploy data sources using Report Manager?
> >
> > Joe
> >
>|||Sorry, this is not supported. You cannot create a shared data source on the
server by uploading an RDS file.
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Linchi Shea" <linchi_shea@.NOSPAM.ml.com> wrote in message
news:O46PeAQeEHA.3792@.TK2MSFTNGP09.phx.gbl...
> If you upload a rds file using Report Manager, you just get a file, not a
> data source. Are you sure that'll work?
> Joe
> "Cédric Naudy" <cnaudy@.online.microsoft.com> wrote in message
> news:OaWljfKeEHA.332@.TK2MSFTNGP09.phx.gbl...
> > Hi, data srouces are files with the .rds extension. I think you can
deploy
> > them by uploading them using report manager.
> >
> > Cédric
> >
> > "Joe Bourne" <anonymous@.discussions.microsoft.com> wrote in message
> > news:86a501c4783b$85c5e8c0$a401280a@.phx.gbl...
> > > You can deploy both reports and the data sources used by
> > > them in Report Designer. You can also deploy reports by
> > > uploading them in Report Manager. But I can't find a way
> > > to deploy data sources (not creating new data sources)
> > > using Report Manager.
> > >
> > > Ideally, when the developers have finished designing and
> > > testing reports, I'd like to have them sending me both rdl
> > > files and rds files so that I can deploy them into
> > > production.
> > >
> > > Can I deploy data sources using Report Manager?
> > >
> > > Joe
> > >
> >
> >
>