Is that possible with RS?

Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web application.
The way I'd like it to work is to click a button and launch a page with the
report. I have stored procedures that the reports would use and I'd like to
manually fill a dataset and assign it to the report.
Is that possible?
All examples I see create a report project, a datasource, and the report.
If I do that, first I have to use a dataset for each report, and I can't use
that reports in the web project.
--
Regards,
Diego F.VS 2005 has report controls for both win and web forms. You can use them in
local mode where you give it a report and the dataset. However it is
definitely more work to use them in local mode. If you already have stored
procedure then create a report that uses the stored procedures. Test and
make sure you like it. Then if possible (VB.Net pro is the cheapest version
that has the controls I believe) get the new controls for your app. With the
new controls it is very easy to embed in your application, set the
parameters and away you go.
Otherwise, look at URL integration to call the report from your app.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Diego F." <diegofrNO@.terra.es> wrote in message
news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web application.
> The way I'd like it to work is to click a button and launch a page with
> the report. I have stored procedures that the reports would use and I'd
> like to manually fill a dataset and assign it to the report.
> Is that possible?
> All examples I see create a report project, a datasource, and the report.
> If I do that, first I have to use a dataset for each report, and I can't
> use that reports in the web project.
> --
> Regards,
> Diego F.
>
>|||I tried creating a report in a report project, with my stored procedures.
But then, I have problems with deployment; it's unable to connect with the
server. I created a site in the server, but if I put
http://server:port/reportserver/reports in the report project properties,
and the conexion isn't possible.
--
Regards,
Diego F.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> escribió en el mensaje
news:uvfMW$gEGHA.2072@.TK2MSFTNGP10.phx.gbl...
> VS 2005 has report controls for both win and web forms. You can use them
> in local mode where you give it a report and the dataset. However it is
> definitely more work to use them in local mode. If you already have stored
> procedure then create a report that uses the stored procedures. Test and
> make sure you like it. Then if possible (VB.Net pro is the cheapest
> version that has the controls I believe) get the new controls for your
> app. With the new controls it is very easy to embed in your application,
> set the parameters and away you go.
> Otherwise, look at URL integration to call the report from your app.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Diego F." <diegofrNO@.terra.es> wrote in message
> news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web
>> application.
>> The way I'd like it to work is to click a button and launch a page with
>> the report. I have stored procedures that the reports would use and I'd
>> like to manually fill a dataset and assign it to the report.
>> Is that possible?
>> All examples I see create a report project, a datasource, and the report.
>> If I do that, first I have to use a dataset for each report, and I can't
>> use that reports in the web project.
>> --
>> Regards,
>> Diego F.
>>
>|||I'm confused. Have your successfully deployed the report? Can you view the
report with Report Manager? Those two things need to happen before you try
to integrate with your app.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Diego F." <diegofrNO@.terra.es> wrote in message
news:%23I0rHJhEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>I tried creating a report in a report project, with my stored procedures.
>But then, I have problems with deployment; it's unable to connect with the
>server. I created a site in the server, but if I put
>http://server:port/reportserver/reports in the report project properties,
>and the conexion isn't possible.
> --
> Regards,
> Diego F.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> escribió en el mensaje
> news:uvfMW$gEGHA.2072@.TK2MSFTNGP10.phx.gbl...
>> VS 2005 has report controls for both win and web forms. You can use them
>> in local mode where you give it a report and the dataset. However it is
>> definitely more work to use them in local mode. If you already have
>> stored procedure then create a report that uses the stored procedures.
>> Test and make sure you like it. Then if possible (VB.Net pro is the
>> cheapest version that has the controls I believe) get the new controls
>> for your app. With the new controls it is very easy to embed in your
>> application, set the parameters and away you go.
>> Otherwise, look at URL integration to call the report from your app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web
>> application.
>> The way I'd like it to work is to click a button and launch a page with
>> the report. I have stored procedures that the reports would use and I'd
>> like to manually fill a dataset and assign it to the report.
>> Is that possible?
>> All examples I see create a report project, a datasource, and the
>> report.
>> If I do that, first I have to use a dataset for each report, and I can't
>> use that reports in the web project.
>> --
>> Regards,
>> Diego F.
>>
>>
>|||You don't have to deploy the report from your dev box. Just copy the RDL
file to somewhere where you can add it to your Report Manager site, and add
it to Report Manager by clicking the Upload file button.
You might have to create data sources manually, just click on New Data
Source button. Connect the report to the datasource and test it.
Kaisa M. Lindahl
"Diego F." <diegofrNO@.terra.es> wrote in message
news:%23I0rHJhEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>I tried creating a report in a report project, with my stored procedures.
>But then, I have problems with deployment; it's unable to connect with the
>server. I created a site in the server, but if I put
>http://server:port/reportserver/reports in the report project properties,
>and the conexion isn't possible.
> --
> Regards,
> Diego F.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> escribió en el mensaje
> news:uvfMW$gEGHA.2072@.TK2MSFTNGP10.phx.gbl...
>> VS 2005 has report controls for both win and web forms. You can use them
>> in local mode where you give it a report and the dataset. However it is
>> definitely more work to use them in local mode. If you already have
>> stored procedure then create a report that uses the stored procedures.
>> Test and make sure you like it. Then if possible (VB.Net pro is the
>> cheapest version that has the controls I believe) get the new controls
>> for your app. With the new controls it is very easy to embed in your
>> application, set the parameters and away you go.
>> Otherwise, look at URL integration to call the report from your app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web
>> application.
>> The way I'd like it to work is to click a button and launch a page with
>> the report. I have stored procedures that the reports would use and I'd
>> like to manually fill a dataset and assign it to the report.
>> Is that possible?
>> All examples I see create a report project, a datasource, and the
>> report.
>> If I do that, first I have to use a dataset for each report, and I can't
>> use that reports in the web project.
>> --
>> Regards,
>> Diego F.
>>
>>
>|||I'm starting to understand it. My first problem is that I can't see the
Report Manager. Where should I configure it?
--
Regards,
Diego F.
"Kaisa M. Lindahl" <kaisaml@.hotmail.com> escribió en el mensaje
news:uS55OarEGHA.3820@.TK2MSFTNGP12.phx.gbl...
> You don't have to deploy the report from your dev box. Just copy the RDL
> file to somewhere where you can add it to your Report Manager site, and
> add it to Report Manager by clicking the Upload file button.
> You might have to create data sources manually, just click on New Data
> Source button. Connect the report to the datasource and test it.
> Kaisa M. Lindahl
> "Diego F." <diegofrNO@.terra.es> wrote in message
> news:%23I0rHJhEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>>I tried creating a report in a report project, with my stored procedures.
>>But then, I have problems with deployment; it's unable to connect with the
>>server. I created a site in the server, but if I put
>>http://server:port/reportserver/reports in the report project properties,
>>and the conexion isn't possible.
>> --
>> Regards,
>> Diego F.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> escribió en el mensaje
>> news:uvfMW$gEGHA.2072@.TK2MSFTNGP10.phx.gbl...
>> VS 2005 has report controls for both win and web forms. You can use them
>> in local mode where you give it a report and the dataset. However it is
>> definitely more work to use them in local mode. If you already have
>> stored procedure then create a report that uses the stored procedures.
>> Test and make sure you like it. Then if possible (VB.Net pro is the
>> cheapest version that has the controls I believe) get the new controls
>> for your app. With the new controls it is very easy to embed in your
>> application, set the parameters and away you go.
>> Otherwise, look at URL integration to call the report from your app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web
>> application.
>> The way I'd like it to work is to click a button and launch a page with
>> the report. I have stored procedures that the reports would use and I'd
>> like to manually fill a dataset and assign it to the report.
>> Is that possible?
>> All examples I see create a report project, a datasource, and the
>> report.
>> If I do that, first I have to use a dataset for each report, and I
>> can't use that reports in the web project.
>> --
>> Regards,
>> Diego F.
>>
>>
>>
>|||Assuming it has been installed correctly on a web server, you should be able
to access Report manager at
http://yourwebserver/reports
Also, check for http://yourwebserver/reportserver/
If these websites are unavailable, you need to check what actually got
installed on the server.
Kaisa M. Lindahl
"Diego F." <diegofrNO@.terra.es> wrote in message
news:eTsTb6PFGHA.2444@.TK2MSFTNGP11.phx.gbl...
> I'm starting to understand it. My first problem is that I can't see the
> Report Manager. Where should I configure it?
> --
> Regards,
> Diego F.
>
> "Kaisa M. Lindahl" <kaisaml@.hotmail.com> escribió en el mensaje
> news:uS55OarEGHA.3820@.TK2MSFTNGP12.phx.gbl...
>> You don't have to deploy the report from your dev box. Just copy the RDL
>> file to somewhere where you can add it to your Report Manager site, and
>> add it to Report Manager by clicking the Upload file button.
>> You might have to create data sources manually, just click on New Data
>> Source button. Connect the report to the datasource and test it.
>> Kaisa M. Lindahl
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:%23I0rHJhEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>>I tried creating a report in a report project, with my stored procedures.
>>But then, I have problems with deployment; it's unable to connect with
>>the server. I created a site in the server, but if I put
>>http://server:port/reportserver/reports in the report project properties,
>>and the conexion isn't possible.
>> --
>> Regards,
>> Diego F.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> escribió en el mensaje
>> news:uvfMW$gEGHA.2072@.TK2MSFTNGP10.phx.gbl...
>> VS 2005 has report controls for both win and web forms. You can use
>> them in local mode where you give it a report and the dataset. However
>> it is definitely more work to use them in local mode. If you already
>> have stored procedure then create a report that uses the stored
>> procedures. Test and make sure you like it. Then if possible (VB.Net
>> pro is the cheapest version that has the controls I believe) get the
>> new controls for your app. With the new controls it is very easy to
>> embed in your application, set the parameters and away you go.
>> Otherwise, look at URL integration to call the report from your app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web
>> application.
>> The way I'd like it to work is to click a button and launch a page
>> with the report. I have stored procedures that the reports would use
>> and I'd like to manually fill a dataset and assign it to the report.
>> Is that possible?
>> All examples I see create a report project, a datasource, and the
>> report.
>> If I do that, first I have to use a dataset for each report, and I
>> can't use that reports in the web project.
>> --
>> Regards,
>> Diego F.
>>
>>
>>
>>
>|||The problem is that if I write that URL, what I see is the list of
directories in both cases. Shouldn't I see an application?
--
Regards,
Diego F.
"Kaisa M. Lindahl" <kaisaml@.hotmail.com> escribió en el mensaje
news:O5VnV9QFGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Assuming it has been installed correctly on a web server, you should be
> able to access Report manager at
> http://yourwebserver/reports
> Also, check for http://yourwebserver/reportserver/
> If these websites are unavailable, you need to check what actually got
> installed on the server.
> Kaisa M. Lindahl
>
> "Diego F." <diegofrNO@.terra.es> wrote in message
> news:eTsTb6PFGHA.2444@.TK2MSFTNGP11.phx.gbl...
>> I'm starting to understand it. My first problem is that I can't see the
>> Report Manager. Where should I configure it?
>> --
>> Regards,
>> Diego F.
>>
>> "Kaisa M. Lindahl" <kaisaml@.hotmail.com> escribió en el mensaje
>> news:uS55OarEGHA.3820@.TK2MSFTNGP12.phx.gbl...
>> You don't have to deploy the report from your dev box. Just copy the RDL
>> file to somewhere where you can add it to your Report Manager site, and
>> add it to Report Manager by clicking the Upload file button.
>> You might have to create data sources manually, just click on New Data
>> Source button. Connect the report to the datasource and test it.
>> Kaisa M. Lindahl
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:%23I0rHJhEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>>I tried creating a report in a report project, with my stored
>>procedures. But then, I have problems with deployment; it's unable to
>>connect with the server. I created a site in the server, but if I put
>>http://server:port/reportserver/reports in the report project
>>properties, and the conexion isn't possible.
>> --
>> Regards,
>> Diego F.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> escribió en el mensaje
>> news:uvfMW$gEGHA.2072@.TK2MSFTNGP10.phx.gbl...
>> VS 2005 has report controls for both win and web forms. You can use
>> them in local mode where you give it a report and the dataset. However
>> it is definitely more work to use them in local mode. If you already
>> have stored procedure then create a report that uses the stored
>> procedures. Test and make sure you like it. Then if possible (VB.Net
>> pro is the cheapest version that has the controls I believe) get the
>> new controls for your app. With the new controls it is very easy to
>> embed in your application, set the parameters and away you go.
>> Otherwise, look at URL integration to call the report from your app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web
>> application.
>> The way I'd like it to work is to click a button and launch a page
>> with the report. I have stored procedures that the reports would use
>> and I'd like to manually fill a dataset and assign it to the report.
>> Is that possible?
>> All examples I see create a report project, a datasource, and the
>> report.
>> If I do that, first I have to use a dataset for each report, and I
>> can't use that reports in the web project.
>> --
>> Regards,
>> Diego F.
>>
>>
>>
>>
>>
>|||No, the Report Manager is an application, but you won't see it as a sort of
program. Report Manager displays reports with descriptions and some details
in a nice user interface, the ReportServer displays some details in plain
text.
If you do get to see the directories, try uploading a report by pressing the
Upload file button in http://yourserver/reports/
Kaisa M. Lindahl
"Diego F." <diegofrNO@.terra.es> wrote in message
news:%23lUPWAcFGHA.3900@.TK2MSFTNGP10.phx.gbl...
> The problem is that if I write that URL, what I see is the list of
> directories in both cases. Shouldn't I see an application?
> --
> Regards,
> Diego F.
>
> "Kaisa M. Lindahl" <kaisaml@.hotmail.com> escribió en el mensaje
> news:O5VnV9QFGHA.1124@.TK2MSFTNGP10.phx.gbl...
>> Assuming it has been installed correctly on a web server, you should be
>> able to access Report manager at
>> http://yourwebserver/reports
>> Also, check for http://yourwebserver/reportserver/
>> If these websites are unavailable, you need to check what actually got
>> installed on the server.
>> Kaisa M. Lindahl
>>
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:eTsTb6PFGHA.2444@.TK2MSFTNGP11.phx.gbl...
>> I'm starting to understand it. My first problem is that I can't see the
>> Report Manager. Where should I configure it?
>> --
>> Regards,
>> Diego F.
>>
>> "Kaisa M. Lindahl" <kaisaml@.hotmail.com> escribió en el mensaje
>> news:uS55OarEGHA.3820@.TK2MSFTNGP12.phx.gbl...
>> You don't have to deploy the report from your dev box. Just copy the
>> RDL file to somewhere where you can add it to your Report Manager site,
>> and add it to Report Manager by clicking the Upload file button.
>> You might have to create data sources manually, just click on New Data
>> Source button. Connect the report to the datasource and test it.
>> Kaisa M. Lindahl
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:%23I0rHJhEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>>I tried creating a report in a report project, with my stored
>>procedures. But then, I have problems with deployment; it's unable to
>>connect with the server. I created a site in the server, but if I put
>>http://server:port/reportserver/reports in the report project
>>properties, and the conexion isn't possible.
>> --
>> Regards,
>> Diego F.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> escribió en el mensaje
>> news:uvfMW$gEGHA.2072@.TK2MSFTNGP10.phx.gbl...
>> VS 2005 has report controls for both win and web forms. You can use
>> them in local mode where you give it a report and the dataset.
>> However it is definitely more work to use them in local mode. If you
>> already have stored procedure then create a report that uses the
>> stored procedures. Test and make sure you like it. Then if possible
>> (VB.Net pro is the cheapest version that has the controls I believe)
>> get the new controls for your app. With the new controls it is very
>> easy to embed in your application, set the parameters and away you
>> go.
>> Otherwise, look at URL integration to call the report from your app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Diego F." <diegofrNO@.terra.es> wrote in message
>> news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
>>> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web
>>> application.
>>>
>>> The way I'd like it to work is to click a button and launch a page
>>> with the report. I have stored procedures that the reports would use
>>> and I'd like to manually fill a dataset and assign it to the report.
>>>
>>> Is that possible?
>>>
>>> All examples I see create a report project, a datasource, and the
>>> report.
>>>
>>> If I do that, first I have to use a dataset for each report, and I
>>> can't use that reports in the web project.
>>>
>>> --
>>> Regards,
>>>
>>> Diego F.
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||I thought that I would interject here a little.
We are using SQL Server 2000 / Reporting Services 2000 both on 1.1
framework. Our web server and web development platform is 2.0 framwork with
the web dev being done on vs 2005.
By far the easiest setup we've had so far is to setup the reports on report
server, publish a url. Then populate a table with two fields; report
discritpion and url field.
From that we have setup a navigation component from the web server and
linked it to the url table.
What this does is break the dev of reports and the web interface apart so
that they can be managed more effectively. As soon as the SQL dev produces a
new report or a change he populates the table with the new info and it is
immediately on the web site for consumers to view.
Ken...
"Kaisa M. Lindahl" wrote:
> No, the Report Manager is an application, but you won't see it as a sort of
> program. Report Manager displays reports with descriptions and some details
> in a nice user interface, the ReportServer displays some details in plain
> text.
> If you do get to see the directories, try uploading a report by pressing the
> Upload file button in http://yourserver/reports/
> Kaisa M. Lindahl
> "Diego F." <diegofrNO@.terra.es> wrote in message
> news:%23lUPWAcFGHA.3900@.TK2MSFTNGP10.phx.gbl...
> > The problem is that if I write that URL, what I see is the list of
> > directories in both cases. Shouldn't I see an application?
> >
> > --
> > Regards,
> >
> > Diego F.
> >
> >
> > "Kaisa M. Lindahl" <kaisaml@.hotmail.com> escribió en el mensaje
> > news:O5VnV9QFGHA.1124@.TK2MSFTNGP10.phx.gbl...
> >> Assuming it has been installed correctly on a web server, you should be
> >> able to access Report manager at
> >>
> >> http://yourwebserver/reports
> >>
> >> Also, check for http://yourwebserver/reportserver/
> >>
> >> If these websites are unavailable, you need to check what actually got
> >> installed on the server.
> >>
> >> Kaisa M. Lindahl
> >>
> >>
> >> "Diego F." <diegofrNO@.terra.es> wrote in message
> >> news:eTsTb6PFGHA.2444@.TK2MSFTNGP11.phx.gbl...
> >> I'm starting to understand it. My first problem is that I can't see the
> >> Report Manager. Where should I configure it?
> >>
> >> --
> >> Regards,
> >>
> >> Diego F.
> >>
> >>
> >> "Kaisa M. Lindahl" <kaisaml@.hotmail.com> escribió en el mensaje
> >> news:uS55OarEGHA.3820@.TK2MSFTNGP12.phx.gbl...
> >> You don't have to deploy the report from your dev box. Just copy the
> >> RDL file to somewhere where you can add it to your Report Manager site,
> >> and add it to Report Manager by clicking the Upload file button.
> >> You might have to create data sources manually, just click on New Data
> >> Source button. Connect the report to the datasource and test it.
> >>
> >> Kaisa M. Lindahl
> >>
> >> "Diego F." <diegofrNO@.terra.es> wrote in message
> >> news:%23I0rHJhEGHA.1736@.TK2MSFTNGP14.phx.gbl...
> >>I tried creating a report in a report project, with my stored
> >>procedures. But then, I have problems with deployment; it's unable to
> >>connect with the server. I created a site in the server, but if I put
> >>http://server:port/reportserver/reports in the report project
> >>properties, and the conexion isn't possible.
> >>
> >> --
> >> Regards,
> >>
> >> Diego F.
> >>
> >>
> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> escribió en el mensaje
> >> news:uvfMW$gEGHA.2072@.TK2MSFTNGP10.phx.gbl...
> >> VS 2005 has report controls for both win and web forms. You can use
> >> them in local mode where you give it a report and the dataset.
> >> However it is definitely more work to use them in local mode. If you
> >> already have stored procedure then create a report that uses the
> >> stored procedures. Test and make sure you like it. Then if possible
> >> (VB.Net pro is the cheapest version that has the controls I believe)
> >> get the new controls for your app. With the new controls it is very
> >> easy to embed in your application, set the parameters and away you
> >> go.
> >>
> >> Otherwise, look at URL integration to call the report from your app.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >> "Diego F." <diegofrNO@.terra.es> wrote in message
> >> news:OPy%23rueEGHA.1736@.TK2MSFTNGP14.phx.gbl...
> >>> Hi. I need to integrate RS2005 in an existing ASP.NET 2.0 web
> >>> application.
> >>>
> >>> The way I'd like it to work is to click a button and launch a page
> >>> with the report. I have stored procedures that the reports would use
> >>> and I'd like to manually fill a dataset and assign it to the report.
> >>>
> >>> Is that possible?
> >>>
> >>> All examples I see create a report project, a datasource, and the
> >>> report.
> >>>
> >>> If I do that, first I have to use a dataset for each report, and I
> >>> can't use that reports in the web project.
> >>>
> >>> --
> >>> Regards,
> >>>
> >>> Diego F.
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>sql

is SSIS wonderful?

Hi guys, I'm using sql 2000 now but eventually will upgrade existing server to sql 2005. currently we only have OLTP dbs. I would like to set up data warehouse & OLAP functionality to drive reporting from the system, is SSIS the product I need? can you please give me the suggestions?

regards

SSIS will certainly help you get your data warehouse going. It is certainly light years ahead of DTS in SQL Server 2000 in terms of functionality and operatability.|||

I know SQL 2005 can do pivot() in the query, isn't enough for reporting? Do I really need to use SSIS ?

|||

NewWorld wrote:

I know SQL 2005 can do pivot() in the query, isn't enough for reporting? Do I really need to use SSIS ?

Reporting really has nothing to do with SSIS. Though you can perform upfront calculations in SSIS and load them into a table to be later used for reports.

Pivot? Pivot is only a small piece of SSIS.|||

I've been using SSIS for a couple of months now and have grown to like it. I'm using it for exactly what you mention -- importing data from (multiple) OLTP databases into a relational data warehouse.

The visual designer is very useful since you can easily see how the data is flowing while running the package. And data viewers are a terrific debugging tool since you can see the data at different points in the data pipeline (much easier than debugging raw SQL scripts).

As far as OLAP goes, you would use SQL Server 2005 Analysis Services to define the structure of your OLAP database, and then use SSIS to get your data from the relational warehouse into the OLAP database (that's usually the last step of my SSIS package -- process the cube).

For reporting, you could use SQL Server 2005 Reporting Services to report on the data in the relational warehouse and/or the OLAP cubes.

Hope this helps, and good luck.

-Larry

|||SSIS - whats that?

You would be much better off creating your own app... lol

Anyways - after using SSIS for 6 months - it is improvement over DTS; BUT MS 2nd hack at ETL tool isnt quite the big time yet --> Some/most Built-in tasks/tools are mediocre or missing (FTP,ZIP,Email etc) and Data Flow although good concept doesnt have a match for SQL based solution --> for example to Update data - you would drop dead using OLE Update Command.

Although - I might sound synical - this is not just based on my own experience banging head against wall trying to figure out SSIS; our consultant with 20 years of DB & programming experience has similar opinion - its his idea using SQL based ETLs which we decided to follow.

Wonderful - joke rite?
Improvement - YES
Easy to get started - YES
Satisfies all your requirements --> Maybe - Maybe Not - BUT be ready for all kinds of errors and mishaps in the journey.

As usual - SSIS forum is the best place to find help in case you get into trouble|||

TheViewMaster wrote:

Anyways - after using SSIS for 6 months - it is improvement over DTS; BUT MS 2nd hack at ETL tool isnt quite the big time yet --> Some/most Built-in tasks/tools are mediocre or missing (FTP,ZIP,Email etc) and Data Flow although good concept doesnt have a match for SQL based solution --> for example to Update data - you would drop dead using OLE Update Command.

I'm going to have to disagree with you here. The data flow (where the OLE DB Command transformation is located) is designed to operate on a row-by-row basis. In a perfect world, how would you propose to implement an "update" feature? Are you looking for more of a GUI-based batch update in the CONTROL flow (as opposed to the Execute SQL task)?

|||

Lawrence Parker wrote:

The visual designer is very useful since you can easily see how the data is flowing while running the package. And data viewers are a terrific debugging tool since you can see the data at different points in the data pipeline (much easier than debugging raw SQL scripts).

Sorry mate - Data Flow data view is no match to SQL solution with using TEMP table to Load data and then Views, SPs, queries to process it which you can use anytime to monitor data movement. Dataview is only design time feature and doesnt help you much if package breaks down in the middle of a job.

Also - SQL solution although a bit more code will make packages easier to upgrade

My personal opinion - SSIS is not quite ready for ETL yet - do Extraxt Load Transform - and you are much better off|||I like being disagreed with on technical stuff - by defending my ideas on importing others we all improve.

OLE DB Command - row by row is way too slow - in a perfect world you would have something like UPDATE mytable FROM ... translated to SSIS.

Also - i forgot in me previous post -
I found a nugget today in Microsoft SQL language -
DELETE FROM x FROM x x ...|||

TheViewMaster wrote:

I like being disagreed with on technical stuff - by defending my ideas on importing others we all improve.

OLE DB Command - row by row is way too slow - in a perfect world you would have something like UPDATE mytable FROM ... translated to SSIS.

Also - i forgot in me previous post -
I found a nugget today in SQL language -
DELETE FROM x FROM x x ...

Right, but you cannot perform an "UPDATE mytable FROM anotherTable" in the data flow. (It shouldn't be expected that you could) You can do that today, and it is the preferred method, in the control flow via an Execute SQL task. Even if they did perform an "UPDATE mytable FROM anotherTable" in the data flow, you certainly wouldn't want that executing for EVERY row, would you? The control flow is the place for that operation. So again, are you asking for a GUI-based task in the control flow to perform batch updates?

|||Perhaps I am asking for wrong thing - but in SQL Stored Procedure all that could be done in one task -
Update existing
Insert new
Delete old
which is the bases of most of our ETL imports to our DB tables

At the moment we are using Data Flow to insert text files to db temp tables (In my case I sneak in occasional Derived column) and then do SQL processing.
I do like control of application (SSIS) to do the work, however benefits of SQL solution have outwighed my initial preference:
SQL has better maintainability - changes can be made to SPs, VIEWS without having to go through of hassle to recompile & deploy package
SQL - simpler processing model - TXT - TEMP table - VIEW - SP IMPORT table - VIEW - SP- Production table

However - SSIS benefits:
less TEMP tables and SQL code
ability to add info in Data Flow - derived column
customized filter duplicates Data Flow transform & able to do "INITCAP" more efficiently than in SQL

50/50|||

TheViewMaster wrote:

Perhaps I am asking for wrong thing - but in SQL Stored Procedure all that could be done in one task -
Update existing
Insert new
Delete old
which is the bases of most of our ETL imports to our DB tables

You're going to get me to 1,000 posts yet tonight, aren't you?! What you are talking about can be done in SSIS, though not inside one data flow. You need to think of the control flow as the foundation for all data work. Using your example, and assuming that order, here's how you'd do it.

Execute SQL task to update existing (update myTable FROM anotherTable) -> Data Flow (to insert new records) -> Execute SQL task (delete old)

Pretty easy, and perhaps faster than your stored procedure... Who knows. The data flow is a highly optimized engine for transporting data from point A (which could be one to many sources -- try that in your stored proc) to point B (which could be one to many destinations). Unfortunately updates aren't really part of data transportation, and is really at the mercy of the database engine.

|||1000 posts here we go - oh wait it's only my 135th post

Anyways - it s more complicated than

update

existing (update myTable FROM anotherTable) -> Data Flow (to

insert new records) -> Execute SQL task (delete old)

You need to determine which are new (lookup) - then which are changed (split) [referencing Jaime's article about SSIS - find columns in table A which are not in table B] - the SQL update, SQL delete (and trust me on this one - in SSIS books and docs they dont mention it at all - trial and error my friend to find out best way)

Somehow I think that INSERT in Store Proc is not that much slower that data flow import (and I would be rather in the mercy of DB engine than in the SSIS engine as the probablity is SSIS will be upgraded sooner)
|||

TheViewMaster wrote:

SQL has better maintainability - changes can be made to SPs, VIEWS without having to go through of hassle to recompile & deploy package

Now I *really* disagree with this statement. Using package configurations, you can create a package such that you'll never have to touch it again. I frequently use configurations to store sql so that I can make changes without touching the package. I can change databases, filenames, SQL, connection strings, etc... all with package configurations and without ever having to touch the package.

|||

TheViewMaster wrote:

1000 posts here we go - oh wait it's only my 135th post

You need to determine which are new (lookup) - then which are changed (split) [referencing Jaime's article about SSIS - find columns in table A which are not in table B] - the SQL update, SQL delete (and trust me on this one - in SSIS books and docs they dont mention it at all - trial and error my friend to find out best way)

Somehow I think that INSERT in Store Proc is not that much slower that data flow import (and I would be rather in the mercy of DB engine than in the SSIS engine as the probablity is SSIS will be upgraded sooner)

You did it! In response to the SQL delete, there are a TON of resources out there - Transact-SQL. Most anything you can do in a database, you can do in SSIS in one way or another... If you understand Transact-SQL, you can make SSIS do some pretty wonderful things!

I'll have to take this up another time, as my night has ended...

Phil

is SSIS wonderful?

Hi guys, I'm using sql 2000 now but eventually will upgrade existing server to sql 2005. currently we only have OLTP dbs. I would like to set up data warehouse & OLAP functionality to drive reporting from the system, is SSIS the product I need? can you please give me the suggestions?

regards

SSIS will certainly help you get your data warehouse going. It is certainly light years ahead of DTS in SQL Server 2000 in terms of functionality and operatability.|||

I know SQL 2005 can do pivot() in the query, isn't enough for reporting? Do I really need to use SSIS ?

|||

NewWorld wrote:

I know SQL 2005 can do pivot() in the query, isn't enough for reporting? Do I really need to use SSIS ?

Reporting really has nothing to do with SSIS. Though you can perform upfront calculations in SSIS and load them into a table to be later used for reports.

Pivot? Pivot is only a small piece of SSIS.|||

I've been using SSIS for a couple of months now and have grown to like it. I'm using it for exactly what you mention -- importing data from (multiple) OLTP databases into a relational data warehouse.

The visual designer is very useful since you can easily see how the data is flowing while running the package. And data viewers are a terrific debugging tool since you can see the data at different points in the data pipeline (much easier than debugging raw SQL scripts).

As far as OLAP goes, you would use SQL Server 2005 Analysis Services to define the structure of your OLAP database, and then use SSIS to get your data from the relational warehouse into the OLAP database (that's usually the last step of my SSIS package -- process the cube).

For reporting, you could use SQL Server 2005 Reporting Services to report on the data in the relational warehouse and/or the OLAP cubes.

Hope this helps, and good luck.

-Larry

|||SSIS - whats that?

You would be much better off creating your own app... lol

Anyways - after using SSIS for 6 months - it is improvement over DTS; BUT MS 2nd hack at ETL tool isnt quite the big time yet --> Some/most Built-in tasks/tools are mediocre or missing (FTP,ZIP,Email etc) and Data Flow although good concept doesnt have a match for SQL based solution --> for example to Update data - you would drop dead using OLE Update Command.

Although - I might sound synical - this is not just based on my own experience banging head against wall trying to figure out SSIS; our consultant with 20 years of DB & programming experience has similar opinion - its his idea using SQL based ETLs which we decided to follow.

Wonderful - joke rite?
Improvement - YES
Easy to get started - YES
Satisfies all your requirements --> Maybe - Maybe Not - BUT be ready for all kinds of errors and mishaps in the journey.

As usual - SSIS forum is the best place to find help in case you get into trouble|||

TheViewMaster wrote:

Anyways - after using SSIS for 6 months - it is improvement over DTS; BUT MS 2nd hack at ETL tool isnt quite the big time yet --> Some/most Built-in tasks/tools are mediocre or missing (FTP,ZIP,Email etc) and Data Flow although good concept doesnt have a match for SQL based solution --> for example to Update data - you would drop dead using OLE Update Command.

I'm going to have to disagree with you here. The data flow (where the OLE DB Command transformation is located) is designed to operate on a row-by-row basis. In a perfect world, how would you propose to implement an "update" feature? Are you looking for more of a GUI-based batch update in the CONTROL flow (as opposed to the Execute SQL task)?

|||

Lawrence Parker wrote:

The visual designer is very useful since you can easily see how the data is flowing while running the package. And data viewers are a terrific debugging tool since you can see the data at different points in the data pipeline (much easier than debugging raw SQL scripts).

Sorry mate - Data Flow data view is no match to SQL solution with using TEMP table to Load data and then Views, SPs, queries to process it which you can use anytime to monitor data movement. Dataview is only design time feature and doesnt help you much if package breaks down in the middle of a job.

Also - SQL solution although a bit more code will make packages easier to upgrade

My personal opinion - SSIS is not quite ready for ETL yet - do Extraxt Load Transform - and you are much better off|||I like being disagreed with on technical stuff - by defending my ideas on importing others we all improve.

OLE DB Command - row by row is way too slow - in a perfect world you would have something like UPDATE mytable FROM ... translated to SSIS.

Also - i forgot in me previous post -
I found a nugget today in Microsoft SQL language -
DELETE FROM x FROM x x ...|||

TheViewMaster wrote:

I like being disagreed with on technical stuff - by defending my ideas on importing others we all improve.

OLE DB Command - row by row is way too slow - in a perfect world you would have something like UPDATE mytable FROM ... translated to SSIS.

Also - i forgot in me previous post -
I found a nugget today in SQL language -
DELETE FROM x FROM x x ...

Right, but you cannot perform an "UPDATE mytable FROM anotherTable" in the data flow. (It shouldn't be expected that you could) You can do that today, and it is the preferred method, in the control flow via an Execute SQL task. Even if they did perform an "UPDATE mytable FROM anotherTable" in the data flow, you certainly wouldn't want that executing for EVERY row, would you? The control flow is the place for that operation. So again, are you asking for a GUI-based task in the control flow to perform batch updates?

|||Perhaps I am asking for wrong thing - but in SQL Stored Procedure all that could be done in one task -
Update existing
Insert new
Delete old
which is the bases of most of our ETL imports to our DB tables

At the moment we are using Data Flow to insert text files to db temp tables (In my case I sneak in occasional Derived column) and then do SQL processing.
I do like control of application (SSIS) to do the work, however benefits of SQL solution have outwighed my initial preference:
SQL has better maintainability - changes can be made to SPs, VIEWS without having to go through of hassle to recompile & deploy package
SQL - simpler processing model - TXT - TEMP table - VIEW - SP IMPORT table - VIEW - SP- Production table

However - SSIS benefits:
less TEMP tables and SQL code
ability to add info in Data Flow - derived column
customized filter duplicates Data Flow transform & able to do "INITCAP" more efficiently than in SQL

50/50|||

TheViewMaster wrote:

Perhaps I am asking for wrong thing - but in SQL Stored Procedure all that could be done in one task -
Update existing
Insert new
Delete old
which is the bases of most of our ETL imports to our DB tables

You're going to get me to 1,000 posts yet tonight, aren't you?! What you are talking about can be done in SSIS, though not inside one data flow. You need to think of the control flow as the foundation for all data work. Using your example, and assuming that order, here's how you'd do it.

Execute SQL task to update existing (update myTable FROM anotherTable) -> Data Flow (to insert new records) -> Execute SQL task (delete old)

Pretty easy, and perhaps faster than your stored procedure... Who knows. The data flow is a highly optimized engine for transporting data from point A (which could be one to many sources -- try that in your stored proc) to point B (which could be one to many destinations). Unfortunately updates aren't really part of data transportation, and is really at the mercy of the database engine.

|||1000 posts here we go - oh wait it's only my 135th post

Anyways - it s more complicated than

update

existing (update myTable FROM anotherTable) -> Data Flow (to

insert new records) -> Execute SQL task (delete old)

You need to determine which are new (lookup) - then which are changed (split) [referencing Jaime's article about SSIS - find columns in table A which are not in table B] - the SQL update, SQL delete (and trust me on this one - in SSIS books and docs they dont mention it at all - trial and error my friend to find out best way)

Somehow I think that INSERT in Store Proc is not that much slower that data flow import (and I would be rather in the mercy of DB engine than in the SSIS engine as the probablity is SSIS will be upgraded sooner)
|||

TheViewMaster wrote:

SQL has better maintainability - changes can be made to SPs, VIEWS without having to go through of hassle to recompile & deploy package

Now I *really* disagree with this statement. Using package configurations, you can create a package such that you'll never have to touch it again. I frequently use configurations to store sql so that I can make changes without touching the package. I can change databases, filenames, SQL, connection strings, etc... all with package configurations and without ever having to touch the package.

|||

TheViewMaster wrote:

1000 posts here we go - oh wait it's only my 135th post

You need to determine which are new (lookup) - then which are changed (split) [referencing Jaime's article about SSIS - find columns in table A which are not in table B] - the SQL update, SQL delete (and trust me on this one - in SSIS books and docs they dont mention it at all - trial and error my friend to find out best way)

Somehow I think that INSERT in Store Proc is not that much slower that data flow import (and I would be rather in the mercy of DB engine than in the SSIS engine as the probablity is SSIS will be upgraded sooner)

You did it! In response to the SQL delete, there are a TON of resources out there - Transact-SQL. Most anything you can do in a database, you can do in SSIS in one way or another... If you understand Transact-SQL, you can make SSIS do some pretty wonderful things!

I'll have to take this up another time, as my night has ended...

Phil

Is SQL Server Service Manager still existing on SQL Express Edition?

Hi there. I am new to the SQL Express. I just finished installing the SQL Express 2005 with Advanced Services on a Windows XP SP2 computer. The first thing I noticed was the service manager (used to be on the taskbar) was being removed on the Express Edition. How do I get this feature back if it's even possible? I know you can find out the server status from the Configuration Manager but it's handy if the status is showned on the taskbar after logging in.

Any help will be greatly appreciated. Thank you.

KC

There is no Service Manager in any SKU of SQL Server 2005. There are some folks out there that have written their own however.

Is SQL Server CE really the solution?

Hi,

So far, with other programming platforms, I used to have the facility, embedded within application .exe, to:

1- Interface with already existing "multi-user" database (ex: Oracle, Access, etc.)

2- Create/access "local"/"Single-User" files for processing purposes. (try to minimize network trafic...)

So far, I've read a lot about SQL Server products (SQL Server, Sql Server Express, SQL Server CE), at least all articles I could find, and would like to have your opinion on what would be the best approach?

1- What SQL version to use for "multi-user" databases?

2- What SQL version to use for "single-user" databases/files?

3- Can SQL Express allow me to achieve both "multi-user" and "single-user" approaches within same app? If not, what would you rather suggest?

Thanks in advance,

Stphane

I include a long discussion of the architectural best practices in both of my new books that include the SQL Server Compact Edition as well as the other SQL Server SKUs.

SQL Server Compact Edition is clearly not a multi-used database--unless you consider using it as a replication subscriber-based DBMS. While this is certainly a way to share data between multiple users, it's not a "multiuser" database in the traditional sense. It's best use is as a single-user data repository--even in applications that connect to a shared database.

SQL Server Express and similar SKUs can be used as a single-user database but it might (just might) be overkill for some situations. Yes, SQL Server Express edition can be used in an application that serves one or many users. As I describe in my books (in great detail), if you intend to take this approach, both applications need to be built as "multiuser" to reduce development and support costs.

See www.hitchhikerguides.net for more information.

hth

|||

Hi,

First, many thanks for replying. I really appreciate. I was aware that SQL CE was not a "multi-users" database. As a reminder, the approach I'm looking for is to have:

1- tables found at a specific network location which are shared by several users at the same time. (where I thought using SQL Express...)

2- tables, owned by single/specific user, which could be localized either on network (especially when centralized backups are an issue) as well as locally. These tables are especially used for queries and calculations required by the user so there is no need to have them "shareable". (where I "first" thought using SQL CE...)

Considering this scenario, after reading all articles I could find on subject, I really scratched my head wondering if using SQL CE in this context would effectively complicate things for nothing, that I could rather simply use SQL Express for both multi-user tables as well as single-user tables at the same time. You seem to say yes.

Now, when you add "...but it might (just might) be overkill for some situations", I'm not too familiar with this "overkill" expression. Can you elaborate a little more about this point?

Accordingly, for my "single user" access needs. With Clarion (ref. SoftVelocity), I used to have in this case directories, one for each user, where I could find any single table needed for processing. In fact, each filename could be specified from within application including appropriate directory path. Now with SQL Express, how can I integrate this same scenario? Will/can I create many occurences of same "single-user" database, one per user, but each one localized at a different physical place? Would certainly like to have your opinion on this...

A last point. Many times, over past years, I had to support people over the phone. I would certainly appreciate to still be able to install any new version of application "off-site" by instructing users over the phone, after sending them everything they need over the Net, method I oftenly used so far with other programming platforms. But... I'm still wondering how I can manage this way any SQL table layout modifications... Let me explain by a concrete example.

Again with Clarion, platform I've used now for many years, I could integrate in my application a "filer" utility wich could compare version of files/tables directly on site and "re-structure" them accordingly if file/table layout was not up to date.

Now, with SQL Express/SQL CE, what is the process involved when my "new" application is now using any table's version which layout is now "newer/different" from the one within actual database thus requiring any re-structuring process? Any tools I must acquire and combine with my application or must this re-structuring process absolutely be done manually on site (like I had no choice to do for any Oracle tables)? Your opinion?

Thanks again,

Stphane

|||

1- tables found at a specific network location which are shared by several users at the same time. (where I thought using SQL Express...)

Yes, SQL Express makes a lot of sense here but you might want to upgrade to Workgroup instead for reasons I'm about to explain.|||

Hi again,

Really appreciate your time. I read carefully your reply and would like to bring a few more things:

"In this case keeping user-specific tables stored in SQLCe might make sense if the application is run without a network connection at all at some time(s)."

Must I understand that I can't have an app using both SQL Express, for accessing "network" tables, and SQL CE, for accessing "local" tables, at the same time?

"Since you're depending on a shared database connection to SQL Express anyway, I would probably keep the user-specific data in the central SQL Express DB with a UserID as a secondary key"

I agree with this kind of structure. My only concerns are if I have, as an example, over a hundred of users running simultaneously reports then generating a lot of data (scenario I've already seen in the past on a tuesday afternoon after administration and production woke up...), won't I face a performance issue taking into account that this kind of data management generates a lot of insert/update/delete statements on same tables, a lot of network traffic in a short period of time? This kind of situation made me decide to go for localized resources which improved a lot the time response for all users. Your opinion?

"Yes, you could cache this on the client with SQLCe to improve startup performance"

I lost you on this one. I'm not sure to understand what you suggest to cache at startup?

"Another approach would be to let the Workgroup Edition publish some or all of this data..."

I took a few minutes and got on Microsoft's website to get some more infos on SQL Server 2005 Workgroup Edition. Seems in fact to be the appropriate tool. Unfortunately, if I'm targetting small/medium businesses as well, I'm quite sure that some customers will tell me to find something less expensive... (Please don't laugh. It's unfortunately true as I had to face this situation many times...) Any other reliable but cheaper approach?

BTW, thanks for taking time to explain the term "overkill". This is not an expression we use around here ;)

"When using a replication architecture, the schema is also propagated to the clients"

Any articles I could read on this replication process? I've never found/read anything on the subject so far... Are your books giving a detailed explanation on this subject? This issue is very important for me as I have to do it most of the times when people are asking for new features.

A last point, your books. BTW, I'm developping using VC++2005 (C++/CLI). I must admit that I'm quite worrying about not being able to find more reliable examples in C++ when I search MSDN or any other related resources, books. I can always convert from C# examples which are not that different but really have a hard time to find my way out with VB examples. In the books you mentionned, what is the language used for the examples?

Having discussed with many persons on this last issue so far, I can't keep asking myself why there is still so few resources available for C++... So much for C# and VB... People, even from Microsoft, told me many times that C++ was here to stay. But... why leaving us, especially when learning, with so few?

Thanks again for your help.

Stphane

|||

Must I understand that I can't have an app using both SQL Express, for accessing "network" tables, and SQL CE, for accessing "local" tables, at the same time?

Sure you can. It's a perfectly viable alternative. I discuss this strategy in the books. I think using SQLCe to store client-specific data or ever-morphing business rules in a local data cache (like SQLCe) makes a lot of sense. This way the application can come up (without having to connect to the server), process data and close down without having to connect at all. Using the SQLCe engine to buffer data that's eventually replicated up to the server also makes sense in some situations. That's what the SQL Mobile/SQLCe engine was designed to do.|||

Hi again,

Where are you that you have never heard of "overkill"? Cleveland?

I'm simply from nearly Montral, in Qubec Canada. Even if I work with English people on a daily basis, it is an expression I didn't hear quite often let's say.

"It's not the language that you use to ask the question that affects the answer--it's the question itself."

You can't hit the target better than that! How true it is!

I will definitely look forward reading your books/ebooks. Thanks again for your support. Again really appreciated.

Case closed for me!

Stphane

|||I (think) I'm speaking in Montreal in May. DevTeach? Look me up then and we can see how well you were able to implement your design.|||

Hi again,

Many thanks for this invitation. Very nice of you. I really hope I will be able to attend DevTeach.

Maybe a little question concerning install of CE. The version I have installed on my machine was done from files downloaded on Dec 15th 2006, which I think was the RC1 version. I noticed while reading this friday issue of "Microsoft Download Notifications" that there seemed to be new versions of CE available for download. I followed links supplied:

SQL Server 2005 Compact Edition:

http://www.microsoft.com/downloads/details.aspx?familyid=85E0C3CE-3FA1-453A-8CE9-AF6CA20946C3&mg_id=10096&displaylang=en

SQL Server 2005 Compact Edition Tools for VS2005 SP1

http://www.microsoft.com/downloads/details.aspx?familyid=877C0ADC-0347-4A47-B842-58FB71D159AC&mg_id=10096&displaylang=en

SQL Server 2005 Compact Edition Books Online

http://www.microsoft.com/downloads/details.aspx?familyid=E6BC81E8-175B-46EA-86A0-C9DACAA84C85&displaylang=en

and downloaded corresponding files but didn't install anything yet. I would have some questions:

1- Is the version obtained from those links the final version of CE?

2- As mentionned, considering that RC1 downloaded on Dec 15th is the version actually installed on my machine, should I uninstall everything before install these new files downloaded today.

3- Considering finally that VS2005 has been upgraded to SP1 on same machine, am I right thinking that I must also install "SQL Server 2005 Compact Edition Tools for VS2005 SP1" or is this already include in "SQL Server 2005 Compact Edition" version I downloaded?

Thanks again for your help, really appreciated.

Stphane

|||

1) The "official" announcment won't come until (at least) Monday. It should detail what's been exposed. I ended up uninstalling VS (completely) and reinstalling VS, SP1 and then the new SDK. I don't think the BOL has changed since the last drop, but I expect there will be further updates. In my opinion (and that of some others), it's pretty thin. That's why I wrote the EBook...

2) I did.

3) BHOM (Beats the Heck Out of Me)... ;) dunno. When I went into VS, after installing the new bits and did see the data providers had been renamed but the SQL Server Management Studio bits don't seem to have caught up. They still refer to the provider as "SQL Mobile".

perhaps we'll hear more next week.

|||

Hi again,

Didn't think you would be online today ;-). Glad to hear from you! As a conclusion to what you wrote, I really think that it would be smarter to wait for upcoming events.

"The "official" announcment won't come until (at least) Monday"

Is there any special website which would be the best source for any news or big titles coming from Microsoft especially for what may concern VS2005? I must admit that for CE, as an example, I browsed throught several websites in order to make my mind about what was really going on. Still no infos on that final version except the bits and bytes I can catch here and there on the Net...

I could understand that you had to reinstall VS. Is this a required step when uninstalling CE?

Must I understand that when upgrading from CE RC1 to CE final, I would probably have to face this reinstall? Yak!!!

BTW, should we receive any announcements or notice from Microsoft when SQL CE would be really at its final version and fully ready for download?

Thanks again,

Stphane

|||"Must I understand that when upgrading from CE RC1 to CE final, I would probably have to face this reinstall? Yak!!!"

I just uninstalled RC1 then installed final - no problem
|||

Hi Brian,

I understand that you had to uninstall RC1. After uninstall was completed, did you encounter any problem with VS2005 like William seems to highlight forcing you to reinstall anything?

(recall of William's reply: "I ended up uninstalling VS (completely) and reinstalling VS, SP1")

I ask you this question because I've myself seen this kind of scenario so many times in the past with many softwares unfortunately...

I presume you are using VS 2005 SP1. What install sequence would you recommend? Is the following one OK?

1. Uninstall SQL Server 2005 CE RC1 and any corresponding BOL installed.

2. Restart computer

3. Install SQL Server 2005 Compact Edition:

http://www.microsoft.com/downloads/details.aspx?familyid=85E0C3CE-3FA1-453A-8CE9-AF6CA20946C3&mg_id=10096&displaylang=en

4. Install SQL Server 2005 Compact Edition Tools for VS2005 SP1

http://www.microsoft.com/downloads/details.aspx?familyid=877C0ADC-0347-4A47-B842-58FB71D159AC&mg_id=10096&displaylang=en

Note: as I already mentionned in earlier post of this thread, is this step required if I'm using VS2005 SP1 or is this install already included in package downloaded from link specified in step 3.

5. Install SQL Server CE BOL

http://www.microsoft.com/downloads/details.aspx?familyid=E6BC81E8-175B-46EA-86A0-C9DACAA84C85&displaylang=en

Thanks for sharing,

Stphane

|||

Hi Stephane:

Your order of installation is incorrect.

The correct order of installation is in the Overview section on the SQL Server 2005 Compact Edition Tools for VS2005 SP1 page at

http://www.microsoft.com/downloads/details.aspx?familyid=877C0ADC-0347-4A47-B842-58FB71D159AC&mg_id=10096&displaylang=en

Robert Wishlaw

|||

Hi Robert,

Many thanks for follow-up and highlighting my mistakes. I followed link you supplied and concluded for what I could read, that install sequence should rather be the following:

1. Uninstall SQL Server 2005 CE RC1 and any corresponding BOL installed.

2. Restart computer

3. Install SQL Server 2005 Compact Edition Tools for VS2005 SP1

4. Install SQL Server 2005 Compact Edition:

5. Install SQL Server CE BOL

Is it OK now?

Also any established facts about the possibility of corrupting VS 2005 SP1 when uninstalling SQL 2005 CE?

Many thanks again for your help,

Stphane