reportservertempdb

We are working on creating a copy of our SQL server machine for disaster
recovery purposes. ReportServerTempDB is purely a temp database, correct?
Meaning, the data in it does not need to be replicated from our production
server to our disaster recovery server, correct?
Could someone just verify this for me.
Thanks.Yes, you don't need to replicated your ReportServerTempDB
According to BOL "Backup and Restore Operations for a Reporting Services
Installation"
The only reason to backup the reportservertempdb is to avoid having to
recreate it if there is a hardware failure.
Med bouchenafa
"Jeff" <Jeff@.discussions.microsoft.com> a écrit dans le message de news:
C440E7E5-D027-4C98-9A8B-EA0C8C2B245B@.microsoft.com...
> We are working on creating a copy of our SQL server machine for disaster
> recovery purposes. ReportServerTempDB is purely a temp database, correct?
> Meaning, the data in it does not need to be replicated from our production
> server to our disaster recovery server, correct?
> Could someone just verify this for me.
> Thanks.|||Depends... are you talking disaster recovery... in which you would
re-establish services from a repository of stored data? ...or... are you
looking for fault tollerance where a more real-time fail over takes place
imediately after the falure due to disaster?
"Jeff" wrote:
> We are working on creating a copy of our SQL server machine for disaster
> recovery purposes. ReportServerTempDB is purely a temp database, correct?
> Meaning, the data in it does not need to be replicated from our production
> server to our disaster recovery server, correct?
> Could someone just verify this for me.
> Thanks.|||Ken,
We're looking a the former. We have an offsite repository of data, which we
would use to re-establish services in the event of a fire or something like
that. This isn't for real time failover.
"Ken Carter" wrote:
> Depends... are you talking disaster recovery... in which you would
> re-establish services from a repository of stored data? ...or... are you
> looking for fault tollerance where a more real-time fail over takes place
> imediately after the falure due to disaster?
> "Jeff" wrote:
> > We are working on creating a copy of our SQL server machine for disaster
> > recovery purposes. ReportServerTempDB is purely a temp database, correct?
> > Meaning, the data in it does not need to be replicated from our production
> > server to our disaster recovery server, correct?
> >
> > Could someone just verify this for me.
> >
> > Thanks.

ReportingWeekToMonthPattern possible values

Hi, I'm working with a server Time dimension which one of it's many purposes is to provide sales analysis by Reporting week. I'm using the property ReportingWeekToMonthPattern to divide the months in weeks but none of the default values is good to me {4-4-5 | 4-5-4 | 544}. According to the business rules, the pattern is not that regular and instead, I need this exact pattern that includes the 12 months of the year:

4-4-5-4-4-5-4-5-4-4-5-4

That is, the first half of the year with a 4-4-5 pattern, and the second half with a 4-5-4 pattern. Is this possible to set in the dimension?

Thanks in advance,

RAH

I don't think you can do this using a server time dimension. You would probably need to create a dimension table and build your time dimension off it. That way you can do pretty much anything you like.

Reporting Stored Procedure on SQL Server 2000

I want to adapt a Stored Procedure like the following for reporting purposes.
select
frmInstId,
frmName,
frmDueDate,
country,
description,
frmLastStatus
flgStat1,
flgStat2,
flgStat3,
flgStat4,
flgStat5
FROM
tblFrmDef,
tblFrmInst,
tblFrmHist,
tblObjects
WHERE
tblFrmDef.frmDefId = tblFrmInst.frmDefId and
tblFrmInst.objId = tblObjects.objId and
tblFrmInst.frmInstId = tblFrmHist.frmInstId and
tblFrmInst.flgActive=1
The problem is that the report can potentially take numerous permutations of
numerous parameters, including:
-tblFrmInst.frmDueDate (range possible)
-tblObjects.user
-tblFrmInst.flgActive (1 or 0)
-tblDef.frmName,
-tblFrmHist.frmLastStatus,
-flgStat1,
-flgStat2,
-flgStat3,
-flgStat4
-flgStat5
Short of building a heavily nested if...then...else statement to build the
correct select statement, are there any better ideas?Dynamic Search Conditions in T-SQL
http://www.sommarskog.se/dyn-search.html
AMB
"Patrick" wrote:
> I want to adapt a Stored Procedure like the following for reporting purposes.
> select
> frmInstId,
> frmName,
> frmDueDate,
> country,
> description,
> frmLastStatus
> flgStat1,
> flgStat2,
> flgStat3,
> flgStat4,
> flgStat5
> FROM
> tblFrmDef,
> tblFrmInst,
> tblFrmHist,
> tblObjects
> WHERE
> tblFrmDef.frmDefId = tblFrmInst.frmDefId and
> tblFrmInst.objId = tblObjects.objId and
> tblFrmInst.frmInstId = tblFrmHist.frmInstId and
> tblFrmInst.flgActive=1
>
> The problem is that the report can potentially take numerous permutations of
> numerous parameters, including:
> -tblFrmInst.frmDueDate (range possible)
> -tblObjects.user
> -tblFrmInst.flgActive (1 or 0)
> -tblDef.frmName,
> -tblFrmHist.frmLastStatus,
> -flgStat1,
> -flgStat2,
> -flgStat3,
> -flgStat4
> -flgStat5
> Short of building a heavily nested if...then...else statement to build the
> correct select statement, are there any better ideas?|||Also, some of our parameters take in list
and I want to do filter like WHERE tblObjects.user in
('jblogg','helloWorld','smith')
how could I do that? I try to make the parameter a varchar(1000) parameter,
but SQL2000 doesn't seem to treat my comma seperated list as a list, but
rather treating it as a single string/value!?
"Alejandro Mesa" wrote:
> Dynamic Search Conditions in T-SQL
> http://www.sommarskog.se/dyn-search.html
>
> AMB
> "Patrick" wrote:
> > I want to adapt a Stored Procedure like the following for reporting purposes.
> > select
> > frmInstId,
> > frmName,
> > frmDueDate,
> > country,
> > description,
> > frmLastStatus
> > flgStat1,
> > flgStat2,
> > flgStat3,
> > flgStat4,
> > flgStat5
> > FROM
> > tblFrmDef,
> > tblFrmInst,
> > tblFrmHist,
> > tblObjects
> > WHERE
> > tblFrmDef.frmDefId = tblFrmInst.frmDefId and
> > tblFrmInst.objId = tblObjects.objId and
> > tblFrmInst.frmInstId = tblFrmHist.frmInstId and
> > tblFrmInst.flgActive=1
> >
> >
> > The problem is that the report can potentially take numerous permutations of
> > numerous parameters, including:
> > -tblFrmInst.frmDueDate (range possible)
> > -tblObjects.user
> > -tblFrmInst.flgActive (1 or 0)
> > -tblDef.frmName,
> > -tblFrmHist.frmLastStatus,
> > -flgStat1,
> > -flgStat2,
> > -flgStat3,
> > -flgStat4
> > -flgStat5
> >
> > Short of building a heavily nested if...then...else statement to build the
> > correct select statement, are there any better ideas?|||Hello Alejandro,
You shall use two single quotation for a string in dynamical query. For
example, you could run this in QA to test
exec ('select * from employees where fname=''test''')
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Thread-Topic: Reporting Stored Procedure on SQL Server 2000
| thread-index: AcWcy8MVucGjmJIKT72QFaaxe01p2g==| X-WBNR-Posting-Host: 198.240.128.75
| From: "=?Utf-8?B?UGF0cmljaw==?=" <questions@.newsgroup.nospam>
| References: <5A2BD817-28A5-433D-9556-3E82983B39DD@.microsoft.com>
<915A2183-FE52-4005-A8A9-4CBF10BC8586@.microsoft.com>
| Subject: RE: Reporting Stored Procedure on SQL Server 2000
| Date: Tue, 9 Aug 2005 03:19:01 -0700
| Lines: 58
| Message-ID: <0C9CE207-7DD9-4EB3-9B8C-0091DFE447CF@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:66307
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Also, some of our parameters take in list
| and I want to do filter like WHERE tblObjects.user in
| ('jblogg','helloWorld','smith')
|
| how could I do that? I try to make the parameter a varchar(1000)
parameter,
| but SQL2000 doesn't seem to treat my comma seperated list as a list, but
| rather treating it as a single string/value!?
|
| "Alejandro Mesa" wrote:
|
| > Dynamic Search Conditions in T-SQL
| > http://www.sommarskog.se/dyn-search.html
| >
| >
| > AMB
| >
| > "Patrick" wrote:
| >
| > > I want to adapt a Stored Procedure like the following for reporting
purposes.
| > > select
| > > frmInstId,
| > > frmName,
| > > frmDueDate,
| > > country,
| > > description,
| > > frmLastStatus
| > > flgStat1,
| > > flgStat2,
| > > flgStat3,
| > > flgStat4,
| > > flgStat5
| > > FROM
| > > tblFrmDef,
| > > tblFrmInst,
| > > tblFrmHist,
| > > tblObjects
| > > WHERE
| > > tblFrmDef.frmDefId = tblFrmInst.frmDefId and
| > > tblFrmInst.objId = tblObjects.objId and
| > > tblFrmInst.frmInstId = tblFrmHist.frmInstId and
| > > tblFrmInst.flgActive=1
| > >
| > >
| > > The problem is that the report can potentially take numerous
permutations of
| > > numerous parameters, including:
| > > -tblFrmInst.frmDueDate (range possible)
| > > -tblObjects.user
| > > -tblFrmInst.flgActive (1 or 0)
| > > -tblDef.frmName,
| > > -tblFrmHist.frmLastStatus,
| > > -flgStat1,
| > > -flgStat2,
| > > -flgStat3,
| > > -flgStat4
| > > -flgStat5
| > >
| > > Short of building a heavily nested if...then...else statement to
build the
| > > correct select statement, are there any better ideas?
|