Cognos to RS

Hi all!

I am taking a cognos report and created an identical one in RS. Can anyone tell me what this means and help figure out how to do it in RS?
cognos
TO_DATE(SUBSTR(DATE_TIME_STAMP,1,14),'YYYYMMDDHH24MISS')

RS (i am guessing)
CONVERT(SUBSTRING(DATE_TIME_STAMP,1,14),yyyyMMddhh?m?ss)

can anyone help?

Thanks in avance,
KerrieIs this a SQL function or a function in the report? If it is the latter, the function for SUBSTR is Mid() (http://whidbey.msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vbalr/html/8b6caa3e-973a-4f18-b0e4-93956a9dee9b.asp). You probably want to use the Format() function (http://whidbey.msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vbalr/html/c6f5bdda-a7c3-4f38-86cc-1cf47aa940b3.asp) in place of the TO_DATE.|||you could try :

http://www.sqlobserver.com

SQLobSERVER is a new independent forum specialising in BI/ETL including across the vendors (ie., Cognos)

Sorry about the blurb, but thought it might to be useful..

Cognos to RS

Hi all!

I am taking a cognos report and created an identical one in RS. Can anyone tell me what this means and help figure out how to do it in RS?
cognos
TO_DATE(SUBSTR(DATE_TIME_STAMP,1,14),'YYYYMMDDHH24MISS')

RS (i am guessing)
CONVERT(SUBSTRING(DATE_TIME_STAMP,1,14),yyyyMMddhh?m?ss)

can anyone help?

Thanks in avance,
KerrieIs this a SQL function or a function in the report? If it is the latter, the function for SUBSTR is Mid() (http://whidbey.msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vbalr/html/8b6caa3e-973a-4f18-b0e4-93956a9dee9b.asp). You probably want to use the Format() function (http://whidbey.msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vbalr/html/c6f5bdda-a7c3-4f38-86cc-1cf47aa940b3.asp) in place of the TO_DATE.|||you could try :

http://www.sqlobserver.com

SQLobSERVER is a new independent forum specialising in BI/ETL including across the vendors (ie., Cognos)

Sorry about the blurb, but thought it might to be useful..

Code page translations are not supported for the text data type. From: 1252 To: 950.

Code page translations are not supported for the text data type. From:
1252 To: 950.

I would like to know what this message means. I also installed the
language packs in advanced settings, Everything is set to English. My
windows XP computer is XP English. For some reason I cant get an update
to go thru using ADO. like Recordset.Update

Although other routines using .update work

Any ideas?Is it possible that If I installed MSDE when I had set under advanced
settings the nonunicode programs to Chinese that this would happen? I
have also noticed I can get around this by using the N' like select *
from some where something = N'something'

Anyway, how does one normally get around this issue, would an uninstall
of MSDE and then reinstall while XP is set to English fix this issue?|||That worked, uninstaled MSDE and reinstalled while XP was set to
english.
But I think the only setting change I made was under
control panel
regional settings
advanced language for nonunicode programs to Chinese(Taiwan).|||Hi

The collation was probably not explicitly set for the installation see
http://msdn.microsoft.com/library/d...istsql_84xl.asp
http://msdn.microsoft.com/library/d..._ca-co_2e95.asp

John

<sdowney717@.msn.com> wrote in message
news:1110744591.148218.180470@.z14g2000cwz.googlegr oups.com...
> That worked, uninstaled MSDE and reinstalled while XP was set to
> english.
> But I think the only setting change I made was under
> control panel
> regional settings
> advanced language for nonunicode programs to Chinese(Taiwan).|||Yes, it gives no options on the install, it must just use whatever is
set for the language. That does answer another question I was wondering
about, involving default collations. Is there an updated install for
MSDE, I only have the one off my Office XP CDROM. from 2000|||Hi

The latest release is downloadable from
http://www.microsoft.com/downloads/...&displaylang=en
this includes SP3a although you can apply SP3a to your existing system using
the appropriate download from
http://www.microsoft.com/sql/downloads/2000/sp3.asp

John

<sdowney717@.msn.com> wrote in message
news:1110749126.795817.193210@.f14g2000cwb.googlegr oups.com...
> Yes, it gives no options on the install, it must just use whatever is
> set for the language. That does answer another question I was wondering
> about, involving default collations. Is there an updated install for
> MSDE, I only have the one off my Office XP CDROM. from 2000|||sdowney717@.msn.com (sdowney717@.msn.com) writes:
> Is it possible that If I installed MSDE when I had set under advanced
> settings the nonunicode programs to Chinese that this would happen? I
> have also noticed I can get around this by using the N' like select *
> from some where something = N'something'

The N' means that the literal is nvarchar and thus Unicode, and thus not
subject to conversion between different 8-bit character sets.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

ClusterDistance value

Can somebody please define the result of the ClusterDistance() function for me. BOL and MSDN are vague about what the output means and I am getting some cases that have a value of zero and sometimes there are more than one per cluster.

Thanks in advance,

Dan Meyers

I believe the clusterdistance() is simply 1-clusterprobability(). Are you saying you are getting more that one "0" value of cluster distance for different clusters on a single case?|||No. I am getting more than one case per cluster that has a ClusterDistance() value of "0".|||That's ok - it's an issue if you get more than one cluster per case with a ClusterDistance() of 0. Imagine if you have two identical cases - it would make sense that they have the same ClusterDistance(), would it not?|||

It does make sense. I just wanted to make sure that I was understanding everything correctly and I was not sure because the documentation is a bit vague in its definition of the function.

Thanks Jamie.

Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
'
Thanks for any enlightening.
Regards,audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
>> Hi,
>> I've read that installing a SQL Server SP is cluster-aware.
>> I'm just not sure what this means.
>> Does this mean that when running the setup on the active node (given
>> 2 nodes), the setup will
>> - install files on the passive node (node2)
>> - failover to the other node (node2)
>> - install files on the first node (node1)
>> - failback to node1
>> or is this way off?
>> After installing the nodes probably needs a reboot. Running on node1;
>> - reboot node2
>> - when back up, failover to node2
>> - reboot node1
>> - when back up, failback to node1
>> '
>> Thanks for any enlightening.
>> Regards,
>|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.129.250.171.67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>> Cluster aware means acting appropriately in all cluster situations.
>> If you install a SP to an instance starting on the host node, it will
>> update all binaries on all accessable nodes AND run SQL update
>> scripts. It will advise you about rebooting both the local and remote
>> node(s) but will not force a reboot. If you run the SP from an node
>> that does not currently host the target instance, it will update local
>> binaries only. Again, it will advise but not force a reboot. This
>> is covered in the Service Pack README file. Hotfixes exhibit the same
>> behavior. In some circumstances, SPs will not do a binary-only local
>> update and you will have to run the service pack again on the entire
>> instance.
>> Geoff N. Hiten
>> Microsoft SQL Server MVP
>>
>> <audunj@.gmail.com> wrote in message
>> news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
>> Hi,
>> I've read that installing a SQL Server SP is cluster-aware.
>> I'm just not sure what this means.
>> Does this mean that when running the setup on the active node (given
>> 2 nodes), the setup will
>> - install files on the passive node (node2)
>> - failover to the other node (node2)
>> - install files on the first node (node1)
>> - failback to node1
>> or is this way off?
>> After installing the nodes probably needs a reboot. Running on node1;
>> - reboot node2
>> - when back up, failover to node2
>> - reboot node1
>> - when back up, failback to node1
>> '
>> Thanks for any enlightening.
>> Regards,
>>
>

Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
'
Thanks for any enlightening.
Regards,audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:

> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
>|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.12
9.250.171.67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>
>

Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
?
Thanks for any enlightening.
Regards,
audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> ?
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)
|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegr oups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> ?
> Thanks for any enlightening.
> Regards,
>
|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:

> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegr oups.com...
>
|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.129.250.171. 67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>