Can I use the rdls created in Visual Studio in Report builder

Hi,

I have created a report template in Visual Studio 2005.

To get a consistent look for all batch and ad-hoc reports, I want to provide this template( which has some labels/text fields/todays date in the report header etc) to the users using ad-hoc reporting.

But while opening the rdl file developed using VS 2005 in Report Builder I get an error:

Cannot Open this item

This report cannot be opened using Report Builder

One or more unexpected Report Definition Language (RDL) elements of the following type have been removed: DataSet
Microsoft.ReportingServices.ReportBuilder.ReportModel.Report: System.Web.Services.Protocols.SoapException: The operation you are attempting on item "/Data Sources/Adcenter" is not allowed for this item type. > Microsoft.ReportingServices.Diagnostics.Utilities.WrongItemTypeException: The operation you are attempting on item "/Data Sources/Adcenter" is not allowed for this item type.
at Microsoft.ReportingServices.Library.ModelCatalogItem.ModelStorage.GetModelItemIDAndItemSecurity(ModelCatalogItem model)
at Microsoft.ReportingServices.Library.ModelCatalogItem.ModelStorage.LoadModel(ModelCatalogItem model, Boolean getModelDefinition)
at Microsoft.ReportingServices.Library.ModelCatalogItem.LoadModel(CatalogItemContext modelContext, Nullable`1 requiredOperation, Boolean getModelDefinition)
at Microsoft.ReportingServices.Library.ModelCatalogItem.LoadUserModel(CatalogItemContext modelContext, Nullable`1 requiredOperation, String perspectiveID)
at Microsoft.ReportingServices.Library.GetUserModelAction.PerformActionNow()
at Microsoft.ReportingServices.Library.RSSoapAction.Execute()
at Microsoft.ReportingServices.WebServer.ReportingService2005.GetUserModel(String Model, String Perspective, Byte[]& Definition)
End of inner exception stack trace
at Microsoft.ReportingServices.WebServer.ReportingService2005.GetUserModel(String Model, String Perspective, Byte[]& Definition)

I also tried to work it around by saving a file developed using Report Builder and modifying it using VS 2005.But when I open the modified file in Report Builder ,it throws the error:

Cannot Open this item

This report cannot be opened using Report Builder

Value cannot be null.

Please help me in this.

Thanks in advance,

Heya --

No -- desiging a report in Report Builder which was created/modifed in VS2005 Report Designer is not supported...

Before 2005 released I remember trying to get it to work anyway, and if your Report Designer report was really, really simple, it sometimes did -- again., that was before the product RTM'd...

|||

Thanks Russel..

Could you suggest some way I can add images,today's date in a textbox (in the report header) etc in a Report Builder report.The insert option in the Report Builder provides only text boxes,unlike images etc in SQL BI Dev studio 2005.

I tried adding todays date as a calculated field in the report but I have to add it as a column in the table of my tabular report.

Thanks in advance..

|||

SP1 will allow you to insert images into reports in Report Builder (yay!) A community tech preview of SP1 was dropped earlier this week. See Brian's blog for more info:

http://blogs.msdn.com/bwelcker/

I've forgotten the current date function you use in R.B. (GetDate()? Now()?) but it should be as easy as adding this function as a forumla in a textbox.

|||

I just posted an example of how to do this on my blog:

http://blogs.msdn.com/bobmeyers/archive/2006/03/26/561147.aspx

|||

Hi,

I am truying to acheive the same. Please let me know if you found the solution.

Regards,

Prakash

Can I use the rdls created in Visual Studio in Report builder

Hi,

I have created a report template in Visual Studio 2005.

To get a consistent look for all batch and ad-hoc reports, I want to provide this template( which has some labels/text fields/todays date in the report header etc) to the users using ad-hoc reporting.

But while opening the rdl file developed using VS 2005 in Report Builder I get an error:

Cannot Open this item

This report cannot be opened using Report Builder

One or more unexpected Report Definition Language (RDL) elements of the following type have been removed: DataSet
Microsoft.ReportingServices.ReportBuilder.ReportModel.Report: System.Web.Services.Protocols.SoapException: The operation you are attempting on item "/Data Sources/Adcenter" is not allowed for this item type. > Microsoft.ReportingServices.Diagnostics.Utilities.WrongItemTypeException: The operation you are attempting on item "/Data Sources/Adcenter" is not allowed for this item type.
at Microsoft.ReportingServices.Library.ModelCatalogItem.ModelStorage.GetModelItemIDAndItemSecurity(ModelCatalogItem model)
at Microsoft.ReportingServices.Library.ModelCatalogItem.ModelStorage.LoadModel(ModelCatalogItem model, Boolean getModelDefinition)
at Microsoft.ReportingServices.Library.ModelCatalogItem.LoadModel(CatalogItemContext modelContext, Nullable`1 requiredOperation, Boolean getModelDefinition)
at Microsoft.ReportingServices.Library.ModelCatalogItem.LoadUserModel(CatalogItemContext modelContext, Nullable`1 requiredOperation, String perspectiveID)
at Microsoft.ReportingServices.Library.GetUserModelAction.PerformActionNow()
at Microsoft.ReportingServices.Library.RSSoapAction.Execute()
at Microsoft.ReportingServices.WebServer.ReportingService2005.GetUserModel(String Model, String Perspective, Byte[]& Definition)
End of inner exception stack trace
at Microsoft.ReportingServices.WebServer.ReportingService2005.GetUserModel(String Model, String Perspective, Byte[]& Definition)

I also tried to work it around by saving a file developed using Report Builder and modifying it using VS 2005.But when I open the modified file in Report Builder ,it throws the error:

Cannot Open this item

This report cannot be opened using Report Builder

Value cannot be null.

Please help me in this.

Thanks in advance,

Heya --

No -- desiging a report in Report Builder which was created/modifed in VS2005 Report Designer is not supported...

Before 2005 released I remember trying to get it to work anyway, and if your Report Designer report was really, really simple, it sometimes did -- again., that was before the product RTM'd...

|||

Thanks Russel..

Could you suggest some way I can add images,today's date in a textbox (in the report header) etc in a Report Builder report.The insert option in the Report Builder provides only text boxes,unlike images etc in SQL BI Dev studio 2005.

I tried adding todays date as a calculated field in the report but I have to add it as a column in the table of my tabular report.

Thanks in advance..

|||

SP1 will allow you to insert images into reports in Report Builder (yay!) A community tech preview of SP1 was dropped earlier this week. See Brian's blog for more info:

http://blogs.msdn.com/bwelcker/

I've forgotten the current date function you use in R.B. (GetDate()? Now()?) but it should be as easy as adding this function as a forumla in a textbox.

|||

I just posted an example of how to do this on my blog:

http://blogs.msdn.com/bobmeyers/archive/2006/03/26/561147.aspx

|||

Hi,

I am truying to acheive the same. Please let me know if you found the solution.

Regards,

Prakash

Can I use table data type in a trigger?

This little batch:
========================================
====
create trigger x on T after insert, update
as
declare @.z table (id int not null)
select
@.z = (select col from table)
go
========================================
====
seems to contain some invalid logic.
QA returns me that I have to declare @.z. But i do this.
Any help appreciated.
Regards.
fabri
Sei un italiano medio, di oltre trent'anni se:
Sai che il codice SYS64738 serviva per riavviare il Commodore 64 ed hai
cambiato almeno una mezza dozzina di joystick Quickshot I giocando a
Summer Games.
MKDS nick & friend Code:
Joker - 055895 043343I got it:

> create trigger x on T after insert, update
> as
> declare @.z table (id int not null)
> insert into @.z = select col from table
> go
fabri
Sei un italiano medio, di oltre trent'anni se:
Sai che il codice SYS64738 serviva per riavviare il Commodore 64 ed hai
cambiato almeno una mezza dozzina di joystick Quickshot I giocando a
Summer Games.
MKDS nick & friend Code:
Joker - 055895 043343

Can I switch recovery model from full to simple and back to full

Here is my scenerio: A developer wants to switch recovery modes from Full
to Simple and then back to Full after his nightly batch cycle for two
databases. Will I have to take two backups a Full at the start of the
nightly batch cycle and then another backup after switching to Simple, right?
Is this possible and will I be able to recover successfully? and what are
the pros and cons? Does anyone have a better idea?
Thanks,
Katherine
The recovery mode will be switched during the STARS/TMS Batch Cycle from
“Full” to “Simple” and then back to “Full” after the successful completion of
the batch processes. Changing the database mode will require that there are
two daily back-up so that in a disaster the transaction logs can be applied.
If you switch to simple and then back to full, then SQL Server would have truncated the log while in
simple. This mean that if you do log backups when back in full, you cannot use those log backups.
You first have to do a db backup (after going back to full) and then the log backups you do after
that will be usable. In essence, you have lost point in time restore possibility for the time from
the last log backup before switching to simple until the first log db backup after going back to
full.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Katherine" <Katherine@.discussions.microsoft.com> wrote in message
news:A342DF5F-8A78-4667-9A6F-28C6FCE9057C@.microsoft.com...
> Here is my scenerio: A developer wants to switch recovery modes from Full
> to Simple and then back to Full after his nightly batch cycle for two
> databases. Will I have to take two backups a Full at the start of the
> nightly batch cycle and then another backup after switching to Simple, right?
> Is this possible and will I be able to recover successfully? and what are
> the pros and cons? Does anyone have a better idea?
> Thanks,
> Katherine
> The recovery mode will be switched during the STARS/TMS Batch Cycle from
> “Full” to “Simple” and then back to “Full” after the successful completion of
> the batch processes. Changing the database mode will require that there are
> two daily back-up so that in a disaster the transaction logs can be applied.
|||The full database backup before the recovery model change is redundant. One
method to address recovery in your scenario is:
- backup log
- change recovery model to SIMPLE
- execute batch process
- change recovery model back to FULL
- backup database
This will allow you to recover to any point in time from the last full
backup until the change to SIMPLE recovery. Your potential data loss are
changes during the batch process (between the SIMPLE recovery model change
and the database backup).
Hope this helps.
Dan Guzman
SQL Server MVP
"Katherine" <Katherine@.discussions.microsoft.com> wrote in message
news:A342DF5F-8A78-4667-9A6F-28C6FCE9057C@.microsoft.com...
> Here is my scenerio: A developer wants to switch recovery modes from
> Full
> to Simple and then back to Full after his nightly batch cycle for two
> databases. Will I have to take two backups a Full at the start of the
> nightly batch cycle and then another backup after switching to Simple,
> right?
> Is this possible and will I be able to recover successfully? and what are
> the pros and cons? Does anyone have a better idea?
> Thanks,
> Katherine
> The recovery mode will be switched during the STARS/TMS Batch Cycle from
> "Full" to "Simple" and then back to "Full" after the successful completion
> of
> the batch processes. Changing the database mode will require that there
> are
> two daily back-up so that in a disaster the transaction logs can be
> applied.

Can I switch recovery model from full to simple and back to full

Here is my scenerio: A developer wants to switch recovery modes from Full
to Simple and then back to Full after his nightly batch cycle for two
databases. Will I have to take two backups a Full at the start of the
nightly batch cycle and then another backup after switching to Simple, right
?
Is this possible and will I be able to recover successfully? and what are
the pros and cons? Does anyone have a better idea?
Thanks,
Katherine
The recovery mode will be switched during the STARS/TMS Batch Cycle from
“Full” to “Simple” and then back to “Full” after the successful
completion of
the batch processes. Changing the database mode will require that there are
two daily back-up so that in a disaster the transaction logs can be applied.If you switch to simple and then back to full, then SQL Server would have tr
uncated the log while in
simple. This mean that if you do log backups when back in full, you cannot u
se those log backups.
You first have to do a db backup (after going back to full) and then the log
backups you do after
that will be usable. In essence, you have lost point in time restore possibi
lity for the time from
the last log backup before switching to simple until the first log db backup
after going back to
full.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Katherine" <Katherine@.discussions.microsoft.com> wrote in message
news:A342DF5F-8A78-4667-9A6F-28C6FCE9057C@.microsoft.com...[vbcol=seagreen]
> Here is my scenerio: A developer wants to switch recovery modes from Ful
l
> to Simple and then back to Full after his nightly batch cycle for two
> databases. Will I have to take two backups a Full at the start of the
> nightly batch cycle and then another backup after switching to Simple, rig
ht?
> Is this possible and will I be able to recover successfully? and what are
> the pros and cons? Does anyone have a better idea?
> Thanks,
> Katherine
> The recovery mode will be switched during the STARS/TMS Batch Cycle from
> “Full” to “Simple” and then back to “Full” after the successfu
l completion of
> the batch processes. Changing the database mode will require that there a
re
> two daily back-up so that in a disaster the transaction logs can be applied.[/vbco
l]|||The full database backup before the recovery model change is redundant. One
method to address recovery in your scenario is:
- backup log
- change recovery model to SIMPLE
- execute batch process
- change recovery model back to FULL
- backup database
This will allow you to recover to any point in time from the last full
backup until the change to SIMPLE recovery. Your potential data loss are
changes during the batch process (between the SIMPLE recovery model change
and the database backup).
Hope this helps.
Dan Guzman
SQL Server MVP
"Katherine" <Katherine@.discussions.microsoft.com> wrote in message
news:A342DF5F-8A78-4667-9A6F-28C6FCE9057C@.microsoft.com...
> Here is my scenerio: A developer wants to switch recovery modes from
> Full
> to Simple and then back to Full after his nightly batch cycle for two
> databases. Will I have to take two backups a Full at the start of the
> nightly batch cycle and then another backup after switching to Simple,
> right?
> Is this possible and will I be able to recover successfully? and what are
> the pros and cons? Does anyone have a better idea?
> Thanks,
> Katherine
> The recovery mode will be switched during the STARS/TMS Batch Cycle from
> "Full" to "Simple" and then back to "Full" after the successful completion
> of
> the batch processes. Changing the database mode will require that there
> are
> two daily back-up so that in a disaster the transaction logs can be
> applied.

Can I switch recovery model from full to simple and back to full

Here is my scenerio: A developer wants to switch recovery modes from Full
to Simple and then back to Full after his nightly batch cycle for two
databases. Will I have to take two backups a Full at the start of the
nightly batch cycle and then another backup after switching to Simple, right?
Is this possible and will I be able to recover successfully? and what are
the pros and cons? Does anyone have a better idea?
Thanks,
Katherine
The recovery mode will be switched during the STARS/TMS Batch Cycle from
â'Fullâ' to â'Simpleâ' and then back to â'Fullâ' after the successful completion of
the batch processes. Changing the database mode will require that there are
two daily back-up so that in a disaster the transaction logs can be applied.If you switch to simple and then back to full, then SQL Server would have truncated the log while in
simple. This mean that if you do log backups when back in full, you cannot use those log backups.
You first have to do a db backup (after going back to full) and then the log backups you do after
that will be usable. In essence, you have lost point in time restore possibility for the time from
the last log backup before switching to simple until the first log db backup after going back to
full.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Katherine" <Katherine@.discussions.microsoft.com> wrote in message
news:A342DF5F-8A78-4667-9A6F-28C6FCE9057C@.microsoft.com...
> Here is my scenerio: A developer wants to switch recovery modes from Full
> to Simple and then back to Full after his nightly batch cycle for two
> databases. Will I have to take two backups a Full at the start of the
> nightly batch cycle and then another backup after switching to Simple, right?
> Is this possible and will I be able to recover successfully? and what are
> the pros and cons? Does anyone have a better idea?
> Thanks,
> Katherine
> The recovery mode will be switched during the STARS/TMS Batch Cycle from
> â'Fullâ' to â'Simpleâ' and then back to â'Fullâ' after the successful completion of
> the batch processes. Changing the database mode will require that there are
> two daily back-up so that in a disaster the transaction logs can be applied.|||The full database backup before the recovery model change is redundant. One
method to address recovery in your scenario is:
- backup log
- change recovery model to SIMPLE
- execute batch process
- change recovery model back to FULL
- backup database
This will allow you to recover to any point in time from the last full
backup until the change to SIMPLE recovery. Your potential data loss are
changes during the batch process (between the SIMPLE recovery model change
and the database backup).
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Katherine" <Katherine@.discussions.microsoft.com> wrote in message
news:A342DF5F-8A78-4667-9A6F-28C6FCE9057C@.microsoft.com...
> Here is my scenerio: A developer wants to switch recovery modes from
> Full
> to Simple and then back to Full after his nightly batch cycle for two
> databases. Will I have to take two backups a Full at the start of the
> nightly batch cycle and then another backup after switching to Simple,
> right?
> Is this possible and will I be able to recover successfully? and what are
> the pros and cons? Does anyone have a better idea?
> Thanks,
> Katherine
> The recovery mode will be switched during the STARS/TMS Batch Cycle from
> "Full" to "Simple" and then back to "Full" after the successful completion
> of
> the batch processes. Changing the database mode will require that there
> are
> two daily back-up so that in a disaster the transaction logs can be
> applied.