Creating RS Folders

We are setting up a Reporting Server and are categorizing our reports by
departments and applications within the departments. I have a long list of
these categorizations which are in the follwing format:
Dept1 App1 Rept1
Dept1 App2 Rept1
Dept2 App1 Rept1
Dept2 App3 Rept1
Dept3 App2 Rept1
...
My two questions are:
1) What is the fastest way for me to create all the folders to reflect the
categorizations as listed above (can this be done faster than just doing it
manually)
2) Once the folder structures have been set up. Can I somehow save this or
script it out for future server builds?Look into using rs.exe to create the folders. You can also use any .Net
language to make SOAP calls to create the folder structure, creating an .exe
that will create them on any RS machine you want.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:32995ABD-3B01-4F4B-8854-6B0108ADC401@.microsoft.com...
> We are setting up a Reporting Server and are categorizing our reports by
> departments and applications within the departments. I have a long list of
> these categorizations which are in the follwing format:
> Dept1 App1 Rept1
> Dept1 App2 Rept1
> Dept2 App1 Rept1
> Dept2 App3 Rept1
> Dept3 App2 Rept1
> ...
> My two questions are:
> 1) What is the fastest way for me to create all the folders to reflect the
> categorizations as listed above (can this be done faster than just doing
> it
> manually)
> 2) Once the folder structures have been set up. Can I somehow save this or
> script it out for future server builds?|||Daniel,
In using the SOAP calls, with forms authentication set up, it appears we'll
need to make sure the forms auth cookie gets through. (I can't get rs.exe
to work, and I presume it's because that cookie isn't there.)
From what I've heard, this means the .NET app we create needs to be a web
service or web app to have visibility into the web security context. Is
that correct?
Thanks,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:ONReSH18EHA.3124@.TK2MSFTNGP11.phx.gbl...
> Look into using rs.exe to create the folders. You can also use any .Net
> language to make SOAP calls to create the folder structure, creating an
> .exe that will create them on any RS machine you want.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "DBA72" <DBA72@.discussions.microsoft.com> wrote in message
> news:32995ABD-3B01-4F4B-8854-6B0108ADC401@.microsoft.com...
>> We are setting up a Reporting Server and are categorizing our reports by
>> departments and applications within the departments. I have a long list
>> of
>> these categorizations which are in the follwing format:
>> Dept1 App1 Rept1
>> Dept1 App2 Rept1
>> Dept2 App1 Rept1
>> Dept2 App3 Rept1
>> Dept3 App2 Rept1
>> ...
>> My two questions are:
>> 1) What is the fastest way for me to create all the folders to reflect
>> the
>> categorizations as listed above (can this be done faster than just doing
>> it
>> manually)
>> 2) Once the folder structures have been set up. Can I somehow save this
>> or
>> script it out for future server builds?
>|||Daniel (or any other MSFT person or person with experience) ... Do we need
to create a web service or web app to *script* reporting services *with
forms auth running*?
I appreciate any replies, thanks,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Jeff A. Stucker" <jeff@.mobilize.net> wrote in message
news:uJwZkKR9EHA.1300@.TK2MSFTNGP14.phx.gbl...
> Daniel,
> In using the SOAP calls, with forms authentication set up, it appears
> we'll need to make sure the forms auth cookie gets through. (I can't get
> rs.exe to work, and I presume it's because that cookie isn't there.)
> From what I've heard, this means the .NET app we create needs to be a web
> service or web app to have visibility into the web security context. Is
> that correct?
> Thanks,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:ONReSH18EHA.3124@.TK2MSFTNGP11.phx.gbl...
>> Look into using rs.exe to create the folders. You can also use any .Net
>> language to make SOAP calls to create the folder structure, creating an
>> .exe that will create them on any RS machine you want.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "DBA72" <DBA72@.discussions.microsoft.com> wrote in message
>> news:32995ABD-3B01-4F4B-8854-6B0108ADC401@.microsoft.com...
>> We are setting up a Reporting Server and are categorizing our reports by
>> departments and applications within the departments. I have a long list
>> of
>> these categorizations which are in the follwing format:
>> Dept1 App1 Rept1
>> Dept1 App2 Rept1
>> Dept2 App1 Rept1
>> Dept2 App3 Rept1
>> Dept3 App2 Rept1
>> ...
>> My two questions are:
>> 1) What is the fastest way for me to create all the folders to reflect
>> the
>> categorizations as listed above (can this be done faster than just doing
>> it
>> manually)
>> 2) Once the folder structures have been set up. Can I somehow save this
>> or
>> script it out for future server builds?
>>
>

creating procedures

I have seen developers create procedures by declaring the variables and
others declaring the variables and setting them to null like below.
Is one way better that another?
CREATE PROCEDURE [dbo].[testsp_InsertIssuerDetails]
@.issuerId int output,
@.companyId int = NULL,
@.issuerName varchar(60) = NULL,
@.dateAdded datetime = NULL,
@.dateModified datetime = NULL,
@.statusDate datetime = NULL,
@.modifiedBy smallint = NULL ....
thanks
MeenalWhen declaring parameters of a procedure the declaration can include a
default value for each parameter. This is what your example shows. This way
the parameters become optional.
On the other hand, the declaration of a variable cannot include a default
value.
ML
http://milambda.blogspot.com/|||If a parameter to a stored procedure has a default assigned, the
parameter is optional when called. If no default is defined, the
parameter is required, and if not provided it will fail:
exec sp_helpindex
Server: Msg 201, Level 16, State 4, Procedure sp_helpindex, Line 0
Procedure 'sp_helpindex' expects parameter '@.objname', which was not
supplied.
Roy Harvey
Beacon Falls, CT
On Tue, 27 Jun 2006 00:48:47 -0400, "meenal"
<meenal_dhody@.hotmail.com> wrote:

>I have seen developers create procedures by declaring the variables and
>others declaring the variables and setting them to null like below.
>Is one way better that another?
>CREATE PROCEDURE [dbo].[testsp_InsertIssuerDetails]
> @.issuerId int output,
> @.companyId int = NULL,
> @.issuerName varchar(60) = NULL,
> @.dateAdded datetime = NULL,
> @.dateModified datetime = NULL,
> @.statusDate datetime = NULL,
> @.modifiedBy smallint = NULL ....
>thanks
>Meenal
>|||IF they are defined in the CREATE statement, what 'looks' like variables are
really known as 'Parameters'. Variables are defined in the stored procedure
body with the DECLARE statement.
It's often easy to confuse Parameters and Variables.
When Parameters are provided values when they are defined, two things are no
w possible. First, it is not necessary to provide a value for that Parameter
when the stored procedure is executed. Second, it may be that a particular
value 'should' be used it the stored procedure if no value of offered.
In Query Analyzer, try the following example:
CREATE PROCEDURE dbo.MyTest
( @.CheckValue int = 0
, @.DateInput datetime = NULL
)
AS
IF @.DateInput IS NULL
SET @.DateInput = getdate()
IF @.CheckValue = 0
PRINT 'Choice Number 0 Selected on ' + cast( @.DateInput AS varchar(11) )
ELSE IF @.CheckValue = 1
PRINT 'Choice Number 1 Selected on ' + cast( @.DateInput AS varchar(11) )
ELSE
PRINT 'Choice Number ' + cast( @.CheckValue AS varchar(5) ) + ' Selected on '
+ cast( @.DateInput AS varchar(11) )
GO
EXECUTE dbo.MyTest
EXECUTE dbo.MyTest @.CheckValue = 1
EXECUTE dbo.MyTest @.CheckValue = 25, @.DateInput = 'jan 1 2005'
--(Note: it is a good practice to use name=value pairs when calling stored p
rocedures and passing parameters.
--It makes your intention very clear, and protects against future changes to
the stored procedure.)
-- Clean up when finished
--DROP PROCEDURE MyTest
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"meenal" <meenal_dhody@.hotmail.com> wrote in message news:uathBVamGHA.2112@.TK2MSFTNGP04.phx
.gbl...
>I have seen developers create procedures by declaring the variables and
> others declaring the variables and setting them to null like below.
>
> Is one way better that another?
>
> CREATE PROCEDURE [dbo].[testsp_InsertIssuerDetails]
> @.issuerId int output,
> @.companyId int = NULL,
> @.issuerName varchar(60) = NULL,
> @.dateAdded datetime = NULL,
> @.dateModified datetime = NULL,
> @.statusDate datetime = NULL,
> @.modifiedBy smallint = NULL ....
>
> thanks
>
> Meenal
>
>