Collation issue?

Hi,
I am having problems querying some czech letters (or maybe it is
inserting that fails?).
Here is the deal:
We have a web application that supports different languages. We have
stored the different messages to be displayed into a nvarchar column
with the SQL_Danish_Pref_CP1_CI_AS collation.
resource_ID
int
langID
int
data nvarchar(4000 )
Then I update the following row into the table:
update usr_data set data='DotaznXk je vyplněn!' where langid=5 and
resource_id=7
When querying the updated value I get
resource_ID langID data
7 5 DotaznXk je vyplnen!
See the missing upside-down ^ over the letter e in the last word.
I have also tested this on collation Latin1_General_CI_AS and
Czech_CI_AS with the same result.
I created a new table with a nvarchar column with the above collation
and inserted the same text, but the result was the same.
What am I missing here?
Thanks,
> Then I update the following row into the table:
> update usr_data set data='DotaznXk je vyplněn!' where langid=5 and
> resource_id=7
For a Unicode constant, prefix the literal with N:
UPDATE dbo.usr_data
SET data = N'DotaznXk je vyplněn!'
WHERE
langid = 5 AND
resource_id = 7
Note that Unicode allows all Unicode characters to be stored. The Unicode
collation affects only sorting and comparison.
Hope this helps.
Dan Guzman
SQL Server MVP
"gurbao" <audunj@.gmail.com> wrote in message
news:1181645527.452234.163220@.x35g2000prf.googlegr oups.com...
Hi,
I am having problems querying some czech letters (or maybe it is
inserting that fails?).
Here is the deal:
We have a web application that supports different languages. We have
stored the different messages to be displayed into a nvarchar column
with the SQL_Danish_Pref_CP1_CI_AS collation.
resource_ID
int
langID
int
data nvarchar(4000 )
Then I update the following row into the table:
update usr_data set data='DotaznXk je vyplněn!' where langid=5 and
resource_id=7
When querying the updated value I get
resource_ID langID data
7 5 DotaznXk je vyplnen!
See the missing upside-down ^ over the letter e in the last word.
I have also tested this on collation Latin1_General_CI_AS and
Czech_CI_AS with the same result.
I created a new table with a nvarchar column with the above collation
and inserted the same text, but the result was the same.
What am I missing here?
Thanks,
|||Thanks a lot!
That did the trick.
Only thing I wonder now, is how I could forget :-)
Regards,
On Jun 12, 1:02Xpm, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> For a Unicode constant, prefix the literal with N:
> UPDATE dbo.usr_data
> SET data = N'DotaznXk je vyplněn!'
> WHERE
> X X langid = 5 AND
> X X resource_id = 7
> Note that Unicode allows all Unicode characters to be stored. XThe Unicode
> collation affects only sorting and comparison.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gurbao" <aud...@.gmail.com> wrote in message
> news:1181645527.452234.163220@.x35g2000prf.googlegr oups.com...
> Hi,
> I am having problems querying some czech letters (or maybe it is
> inserting that fails?).
> Here is the deal:
> We have a web application that supports different languages. We have
> stored the different messages to be displayed into a nvarchar column
> with the SQL_Danish_Pref_CP1_CI_AS collation.
> resource_ID
> int
> langID
> int
> data X X X X X X nvarchar(4000 )
> Then I update the following row into the table:
> update usr_data set data='DotaznXk je vyplněn!' where langid=5 and
> resource_id=7
> When querying the updated value I get
> resource_ID langID X X Xdata
> X X X X X 7 X X X X X 5DotaznXk je vyplnen!
> See the missing upside-down ^ over the letter e in the last word.
> I have also tested this on collation Latin1_General_CI_AS and
> Czech_CI_AS with the same result.
> I created a new table with a nvarchar column with the above collation
> and inserted the same text, but the result was the same.
> What am I missing here?
> Thanks,
|||> Only thing I wonder now, is how I could forget :-)
I'm glad I was able to help. I think you'll remember the 'N' the next time
;-)
Dan Guzman
SQL Server MVP
"gurbao" <audunj@.gmail.com> wrote in message
news:1181646750.111306.272120@.z28g2000prd.googlegr oups.com...
Thanks a lot!
That did the trick.
Only thing I wonder now, is how I could forget :-)
Regards,
On Jun 12, 1:02 pm, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> For a Unicode constant, prefix the literal with N:
> UPDATE dbo.usr_data
> SET data = N'DotaznXk je vyplněn!'
> WHERE
> langid = 5 AND
> resource_id = 7
> Note that Unicode allows all Unicode characters to be stored. The Unicode
> collation affects only sorting and comparison.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gurbao" <aud...@.gmail.com> wrote in message
> news:1181645527.452234.163220@.x35g2000prf.googlegr oups.com...
> Hi,
> I am having problems querying some czech letters (or maybe it is
> inserting that fails?).
> Here is the deal:
> We have a web application that supports different languages. We have
> stored the different messages to be displayed into a nvarchar column
> with the SQL_Danish_Pref_CP1_CI_AS collation.
> resource_ID
> int
> langID
> int
> data nvarchar(4000 )
> Then I update the following row into the table:
> update usr_data set data='DotaznXk je vyplněn!' where langid=5 and
> resource_id=7
> When querying the updated value I get
> resource_ID langID data
> 7 5 DotaznXk je vyplnen!
> See the missing upside-down ^ over the letter e in the last word.
> I have also tested this on collation Latin1_General_CI_AS and
> Czech_CI_AS with the same result.
> I created a new table with a nvarchar column with the above collation
> and inserted the same text, but the result was the same.
> What am I missing here?
> Thanks,

Collation issue?

Hi,
I am having problems querying some czech letters (or maybe it is
inserting that fails?).
Here is the deal:
We have a web application that supports different languages. We have
stored the different messages to be displayed into a nvarchar column
with the SQL_Danish_Pref_CP1_CI_AS collation.
resource_ID
int
langID
int
data nvarchar(4000 )
Then I update the following row into the table:
update usr_data set data=3D'Dotazn=C3=ADk je vypln=C4=9Bn!' where langid=3D= 5 and
resource_id=3D7
When querying the updated value I get
resource_ID langID data
7 5 Dotazn=C3=ADk je vyplnen!
See the missing upside-down ^ over the letter e in the last word.
I have also tested this on collation Latin1_General_CI_AS and
Czech_CI_AS with the same result.
I created a new table with a nvarchar column with the above collation
and inserted the same text, but the result was the same.
What am I missing here?
Thanks,> Then I update the following row into the table:
> update usr_data set data='Dotazník je vyplnÄ?n!' where langid=5 and
> resource_id=7
For a Unicode constant, prefix the literal with N:
UPDATE dbo.usr_data
SET data = N'Dotazník je vyplnÄ?n!'
WHERE
langid = 5 AND
resource_id = 7
Note that Unicode allows all Unicode characters to be stored. The Unicode
collation affects only sorting and comparison.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"gurbao" <audunj@.gmail.com> wrote in message
news:1181645527.452234.163220@.x35g2000prf.googlegroups.com...
Hi,
I am having problems querying some czech letters (or maybe it is
inserting that fails?).
Here is the deal:
We have a web application that supports different languages. We have
stored the different messages to be displayed into a nvarchar column
with the SQL_Danish_Pref_CP1_CI_AS collation.
resource_ID
int
langID
int
data nvarchar(4000 )
Then I update the following row into the table:
update usr_data set data='Dotazník je vyplnÄ?n!' where langid=5 and
resource_id=7
When querying the updated value I get
resource_ID langID data
7 5 Dotazník je vyplnen!
See the missing upside-down ^ over the letter e in the last word.
I have also tested this on collation Latin1_General_CI_AS and
Czech_CI_AS with the same result.
I created a new table with a nvarchar column with the above collation
and inserted the same text, but the result was the same.
What am I missing here?
Thanks,|||Thanks a lot!
That did the trick.
Only thing I wonder now, is how I could forget :-)
Regards,
On Jun 12, 1:02=C2=A0pm, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> > Then I update the following row into the table:
> > update usr_data set data=3D'Dotazn=C3=ADk je vypln=C4=9Bn!' where langi=d=3D5 and
> > resource_id=3D7
> For a Unicode constant, prefix the literal with N:
> UPDATE dbo.usr_data
> SET data =3D N'Dotazn=C3=ADk je vypln=C4=9Bn!'
> WHERE
> =C2=A0 =C2=A0 langid =3D 5 AND
> =C2=A0 =C2=A0 resource_id =3D 7
> Note that Unicode allows all Unicode characters to be stored. =C2=A0The U=nicode
> collation affects only sorting and comparison.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gurbao" <aud...@.gmail.com> wrote in message
> news:1181645527.452234.163220@.x35g2000prf.googlegroups.com...
> Hi,
> I am having problems querying some czech letters (or maybe it is
> inserting that fails?).
> Here is the deal:
> We have a web application that supports different languages. We have
> stored the different messages to be displayed into a nvarchar column
> with the SQL_Danish_Pref_CP1_CI_AS collation.
> resource_ID
> int
> langID
> int
> data =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 nvarchar(4000 )
> Then I update the following row into the table:
> update usr_data set data=3D'Dotazn=C3=ADk je vypln=C4=9Bn!' where langid==3D5 and
> resource_id=3D7
> When querying the updated value I get
> resource_ID langID =C2=A0 =C2=A0 =C2=A0data
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 7 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 5= Dotazn=C3=ADk je vyplnen!
> See the missing upside-down ^ over the letter e in the last word.
> I have also tested this on collation Latin1_General_CI_AS and
> Czech_CI_AS with the same result.
> I created a new table with a nvarchar column with the above collation
> and inserted the same text, but the result was the same.
> What am I missing here?
> Thanks,|||> Only thing I wonder now, is how I could forget :-)
I'm glad I was able to help. I think you'll remember the 'N' the next time
;-)
--
Dan Guzman
SQL Server MVP
"gurbao" <audunj@.gmail.com> wrote in message
news:1181646750.111306.272120@.z28g2000prd.googlegroups.com...
Thanks a lot!
That did the trick.
Only thing I wonder now, is how I could forget :-)
Regards,
On Jun 12, 1:02 pm, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> > Then I update the following row into the table:
> > update usr_data set data='Dotazník je vyplnÄ?n!' where langid=5 and
> > resource_id=7
> For a Unicode constant, prefix the literal with N:
> UPDATE dbo.usr_data
> SET data = N'Dotazník je vyplnÄ?n!'
> WHERE
> langid = 5 AND
> resource_id = 7
> Note that Unicode allows all Unicode characters to be stored. The Unicode
> collation affects only sorting and comparison.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gurbao" <aud...@.gmail.com> wrote in message
> news:1181645527.452234.163220@.x35g2000prf.googlegroups.com...
> Hi,
> I am having problems querying some czech letters (or maybe it is
> inserting that fails?).
> Here is the deal:
> We have a web application that supports different languages. We have
> stored the different messages to be displayed into a nvarchar column
> with the SQL_Danish_Pref_CP1_CI_AS collation.
> resource_ID
> int
> langID
> int
> data nvarchar(4000 )
> Then I update the following row into the table:
> update usr_data set data='Dotazník je vyplnÄ?n!' where langid=5 and
> resource_id=7
> When querying the updated value I get
> resource_ID langID data
> 7 5 Dotazník je vyplnen!
> See the missing upside-down ^ over the letter e in the last word.
> I have also tested this on collation Latin1_General_CI_AS and
> Czech_CI_AS with the same result.
> I created a new table with a nvarchar column with the above collation
> and inserted the same text, but the result was the same.
> What am I missing here?
> Thanks,

Collation issue?

Hi,
I am having problems querying some czech letters (or maybe it is
inserting that fails?).
Here is the deal:
We have a web application that supports different languages. We have
stored the different messages to be displayed into a nvarchar column
with the SQL_Danish_Pref_CP1_CI_AS collation.
resource_ID
int
langID
int
data nvarchar(4000 )
Then I update the following row into the table:
update usr_data set data=3D'Dotazn=C3=ADk je vypln=C4=9Bn!' where langid=3D=
5 and
resource_id=3D7
When querying the updated value I get
resource_ID langID data
7 5 Dotazn=C3=ADk je vyplnen!
See the missing upside-down ^ over the letter e in the last word.
I have also tested this on collation Latin1_General_CI_AS and
Czech_CI_AS with the same result.
I created a new table with a nvarchar column with the above collation
and inserted the same text, but the result was the same.
What am I missing here?
Thanks,> Then I update the following row into the table:
> update usr_data set data='Dotazn_k je vyplněn!' where langid=5 and
> resource_id=7
For a Unicode constant, prefix the literal with N:
UPDATE dbo.usr_data
SET data = N'Dotazn_k je vyplněn!'
WHERE
langid = 5 AND
resource_id = 7
Note that Unicode allows all Unicode characters to be stored. The Unicode
collation affects only sorting and comparison.
Hope this helps.
Dan Guzman
SQL Server MVP
"gurbao" <audunj@.gmail.com> wrote in message
news:1181645527.452234.163220@.x35g2000prf.googlegroups.com...
Hi,
I am having problems querying some czech letters (or maybe it is
inserting that fails?).
Here is the deal:
We have a web application that supports different languages. We have
stored the different messages to be displayed into a nvarchar column
with the SQL_Danish_Pref_CP1_CI_AS collation.
resource_ID
int
langID
int
data nvarchar(4000 )
Then I update the following row into the table:
update usr_data set data='Dotazn_k je vyplněn!' where langid=5 and
resource_id=7
When querying the updated value I get
resource_ID langID data
7 5 Dotazn_k je vyplnen!
See the missing upside-down ^ over the letter e in the last word.
I have also tested this on collation Latin1_General_CI_AS and
Czech_CI_AS with the same result.
I created a new table with a nvarchar column with the above collation
and inserted the same text, but the result was the same.
What am I missing here?
Thanks,|||Thanks a lot!
That did the trick.
Only thing I wonder now, is how I could forget :-)
Regards,
On Jun 12, 1:02=C2=A0pm, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
d=3D5 and[vbcol=seagreen]
> For a Unicode constant, prefix the literal with N:
> UPDATE dbo.usr_data
> SET data =3D N'Dotazn=C3=ADk je vypln=C4=9Bn!'
> WHERE
> =C2=A0 =C2=A0 langid =3D 5 AND
> =C2=A0 =C2=A0 resource_id =3D 7
> Note that Unicode allows all Unicode characters to be stored. =C2=A0The U=
nicode
> collation affects only sorting and comparison.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gurbao" <aud...@.gmail.com> wrote in message
> news:1181645527.452234.163220@.x35g2000prf.googlegroups.com...
> Hi,
> I am having problems querying some czech letters (or maybe it is
> inserting that fails?).
> Here is the deal:
> We have a web application that supports different languages. We have
> stored the different messages to be displayed into a nvarchar column
> with the SQL_Danish_Pref_CP1_CI_AS collation.
> resource_ID
> int
> langID
> int
> data =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 nvarchar(4000 )
> Then I update the following row into the table:
> update usr_data set data=3D'Dotazn=C3=ADk je vypln=C4=9Bn!' where langid=
=3D5 and
> resource_id=3D7
> When querying the updated value I get
> resource_ID langID =C2=A0 =C2=A0 =C2=A0data
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 7 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 5=
Dotazn=C3=ADk je vyplnen!
> See the missing upside-down ^ over the letter e in the last word.
> I have also tested this on collation Latin1_General_CI_AS and
> Czech_CI_AS with the same result.
> I created a new table with a nvarchar column with the above collation
> and inserted the same text, but the result was the same.
> What am I missing here?
> Thanks,|||> Only thing I wonder now, is how I could forget :-)
I'm glad I was able to help. I think you'll remember the 'N' the next time
;-)
Dan Guzman
SQL Server MVP
"gurbao" <audunj@.gmail.com> wrote in message
news:1181646750.111306.272120@.z28g2000prd.googlegroups.com...
Thanks a lot!
That did the trick.
Only thing I wonder now, is how I could forget :-)
Regards,
On Jun 12, 1:02 pm, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> For a Unicode constant, prefix the literal with N:
> UPDATE dbo.usr_data
> SET data = N'Dotazn_k je vyplněn!'
> WHERE
> langid = 5 AND
> resource_id = 7
> Note that Unicode allows all Unicode characters to be stored. The Unicode
> collation affects only sorting and comparison.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gurbao" <aud...@.gmail.com> wrote in message
> news:1181645527.452234.163220@.x35g2000prf.googlegroups.com...
> Hi,
> I am having problems querying some czech letters (or maybe it is
> inserting that fails?).
> Here is the deal:
> We have a web application that supports different languages. We have
> stored the different messages to be displayed into a nvarchar column
> with the SQL_Danish_Pref_CP1_CI_AS collation.
> resource_ID
> int
> langID
> int
> data nvarchar(4000 )
> Then I update the following row into the table:
> update usr_data set data='Dotazn_k je vyplněn!' where langid=5 and
> resource_id=7
> When querying the updated value I get
> resource_ID langID data
> 7 5 Dotazn_k je vyplnen!
> See the missing upside-down ^ over the letter e in the last word.
> I have also tested this on collation Latin1_General_CI_AS and
> Czech_CI_AS with the same result.
> I created a new table with a nvarchar column with the above collation
> and inserted the same text, but the result was the same.
> What am I missing here?
> Thanks,

CogInStr function fails with MSAS 2005

Hi,

Following MDX query works with MSAS 2000 but fails with MSAS 2005:

SELECT
{ FILTER([Product].AllMembers, CogInStr([Product].CurrentMember.Name,"*", 0) > 0) }
ON AXIS(0)
FROM [Sales]

Following error is thrown:

[ 1] Microsoft OLE DB Provider for Analysis S: Query (2, 32) The '[CogInStr]' function does not exist.

Any pointers on what needs to be done in order to support this query in MSAS 2005 would be appreciated.

Thanks and Regards,
Santosh

CogInStr - was not the built in funtion in AS2000, and it is not a built in function in AS2005 either. I suspect in your deployment somebody implemented custom UDF function with such name. You will need to implement it as a stored procedure in AS2005.

|||

Thanks for your response.
Yes, in AS2000 it was implemented as a UDF as shown below:

command = USE LIBRARY "CogUdf.CogRExp"
command = SELECT
{ FILTER([Product].AllMembers, CogInStr([Product].CurrentMember.Name,"*", 0) > 0) }
ON AXIS(0)
FROM [Sales]

Can you please give me some pointers (possible code snippets) on how I can convert this to a stored procedure in AS2005.

Thanks in advance,
Santosh.

|||Also, can't i use it in the same manner as it was in AS2000. i.e, through library function which i can execute using the USE LIBRARY call?|||

Please read BOL on the subject of stored procedures. Once they are deployed to the server, there is no need to do USE LIBRARY command anymore. For the extensive library of custom sprocs, you can check the following CodePlex project: http://www.codeplex.com/ASStoredProcedures

HTH,

Mosha (http://www.mosha.com/msolap)

|||The samples given in codeplex.com have been written in C#. Can stored procedures be implemented using OLE db for olap interfaces?|||You are not asking the right question. Take a look at the implementation of CogInStr - it doesn't use OLEDB for OLAP. You can easily replicate its functionality on C# or VB.NET or any other CLR language.|||

Sorry for the confusion.

I was trying to use the ASSP project with my MSAS 2005. I registered ASSP.dll under server assembly as a COM DLL type of assembly.

Later when I tried to run the following MDX query against the Adventure Works DW sample database, I am getting following error:

Query (1, 30) The '[ASSP].[FindCurrentMemberVerbose]' function does not exist.

Is there a link which demonstrate the use of these stored procedures with MSAS2005 and how to register it under Server/Database assemblies?

Thanks and Regards,
Santosh.

|||

I was able to use the Stored Procedure finally with MSAS 2005.

Thanks,
Santosh.

CMDExec not working in sql agent job.

We have both our sql server and agent running under an
account of sqlservice. I run a winrar job in the agent as
a CMDExec step and it fails everytime. If I terminal
service into the box under the sqlservice account I can
create new files on both the source and destination file
systems. I can also run the job as a batch script from the
command line.
I'm baffeled, if I can run the job as the same account
the agent is running under and specify the job as that
same user. What is stopping this job from running?
"c:\Program Files\WinRAR\rar" a -ep1 "\\Ixcorpnas01
\public1\bmurtha\telnform
[DATE].rar" "G:\MSSQL\BACKUP\telnform.BAK"
I get this error:
Executed as user: IXCORPSQL01\SqlService. The process
could not be created for step 2 of job
0x0C7C1F1321CA844D884F666429C26A67 (reason: The system
cannot find the file specified). The step failed.
But runs fine on the command line when logged in as
sqlservice.
Please help,
BryanHi Bryan
Is the service you are using a Domain account or a local account? The error
you get says it's executed as user 'IXCOPRSQL01\...' which to me sounds like
a local account rather than a domain account. If you are running it as a
local user, you might have problems getting to your '\\Ixcoprnas01\....'
share.
Regards
Steen
Bryan Murtha wrote:
> We have both our sql server and agent running under an
> account of sqlservice. I run a winrar job in the agent as
> a CMDExec step and it fails everytime. If I terminal
> service into the box under the sqlservice account I can
> create new files on both the source and destination file
> systems. I can also run the job as a batch script from the
> command line.
> I'm baffeled, if I can run the job as the same account
> the agent is running under and specify the job as that
> same user. What is stopping this job from running?
> "c:\Program Files\WinRAR\rar" a -ep1 "\\Ixcorpnas01
> \public1\bmurtha\telnform
> [DATE].rar" "G:\MSSQL\BACKUP\telnform.BAK"
> I get this error:
> Executed as user: IXCORPSQL01\SqlService. The process
> could not be created for step 2 of job
> 0x0C7C1F1321CA844D884F666429C26A67 (reason: The system
> cannot find the file specified). The step failed.
> But runs fine on the command line when logged in as
> sqlservice.
> Please help,
> Bryan|||Hi Steve,
Oddly enough I didn't figure out what was happening
until I took that line and executed in Query Analyizer
with xp_cmdshell. It wound up it was path to RAR that was
blowing up. It had nothing to to with the NAS or the
backup path. I just stuck RAR in system32 and changed this:
"c:\Program Files\WinRAR\rar" to rar and it was all good.
Regards,
Bryan
>--Original Message--
>Hi Bryan
>Is the service you are using a Domain account or a local
account? The error
>you get says it's executed as user 'IXCOPRSQL01\...'
which to me sounds like
>a local account rather than a domain account. If you are
running it as a
>local user, you might have problems getting to
your '\\Ixcoprnas01\....'
>share.
>Regards
>Steen
>
>Bryan Murtha wrote:
>> We have both our sql server and agent running under an
>> account of sqlservice. I run a winrar job in the agent
as
>> a CMDExec step and it fails everytime. If I terminal
>> service into the box under the sqlservice account I can
>> create new files on both the source and destination file
>> systems. I can also run the job as a batch script from
the
>> command line.
>> I'm baffeled, if I can run the job as the same account
>> the agent is running under and specify the job as that
>> same user. What is stopping this job from running?
>> "c:\Program Files\WinRAR\rar" a -ep1 "\\Ixcorpnas01
>> \public1\bmurtha\telnform
>> [DATE].rar" "G:\MSSQL\BACKUP\telnform.BAK"
>> I get this error:
>> Executed as user: IXCORPSQL01\SqlService. The process
>> could not be created for step 2 of job
>> 0x0C7C1F1321CA844D884F666429C26A67 (reason: The system
>> cannot find the file specified). The step failed.
>> But runs fine on the command line when logged in as
>> sqlservice.
>> Please help,
>> Bryan
>
>.
>

CMDExec not working in sql agent job.

We have both our sql server and agent running under an
account of sqlservice. I run a winrar job in the agent as
a CMDExec step and it fails everytime. If I terminal
service into the box under the sqlservice account I can
create new files on both the source and destination file
systems. I can also run the job as a batch script from the
command line.
I'm baffeled, if I can run the job as the same account
the agent is running under and specify the job as that
same user. What is stopping this job from running?
"c:\Program Files\WinRAR\rar" a -ep1 "\\Ixcorpnas01
\public1\bmurtha\telnform
[DATE].rar" "G:\MSSQL\BACKUP\telnform.BAK"
I get this error:
Executed as user: IXCORPSQL01\SqlService. The process
could not be created for step 2 of job
0x0C7C1F1321CA844D884F666429C26A67 (reason: The system
cannot find the file specified). The step failed.
But runs fine on the command line when logged in as
sqlservice.
Please help,
BryanHi Bryan
Is the service you are using a Domain account or a local account? The error
you get says it's executed as user 'IXCOPRSQL01\...' which to me sounds like
a local account rather than a domain account. If you are running it as a
local user, you might have problems getting to your '\\Ixcoprnas01\....'
share.
Regards
Steen
Bryan Murtha wrote:
> We have both our sql server and agent running under an
> account of sqlservice. I run a winrar job in the agent as
> a CMDExec step and it fails everytime. If I terminal
> service into the box under the sqlservice account I can
> create new files on both the source and destination file
> systems. I can also run the job as a batch script from the
> command line.
> I'm baffeled, if I can run the job as the same account
> the agent is running under and specify the job as that
> same user. What is stopping this job from running?
> "c:\Program Files\WinRAR\rar" a -ep1 "\\Ixcorpnas01
> \public1\bmurtha\telnform
> [DATE].rar" "G:\MSSQL\BACKUP\telnform.BAK"
> I get this error:
> Executed as user: IXCORPSQL01\SqlService. The process
> could not be created for step 2 of job
> 0x0C7C1F1321CA844D884F666429C26A67 (reason: The system
> cannot find the file specified). The step failed.
> But runs fine on the command line when logged in as
> sqlservice.
> Please help,
> Bryan|||Hi Steve,
Oddly enough I didn't figure out what was happening
until I took that line and executed in Query Analyizer
with xp_cmdshell. It wound up it was path to RAR that was
blowing up. It had nothing to to with the NAS or the
backup path. I just stuck RAR in system32 and changed this:
"c:\Program Files\WinRAR\rar" to rar and it was all good.
Regards,
Bryan
>--Original Message--
>Hi Bryan
>Is the service you are using a Domain account or a local
account? The error
>you get says it's executed as user 'IXCOPRSQL01\...'
which to me sounds like
>a local account rather than a domain account. If you are
running it as a
>local user, you might have problems getting to
your '\\Ixcoprnas01\....'
>share.
>Regards
>Steen
>
>Bryan Murtha wrote:
as[vbcol=seagreen]
the[vbcol=seagreen]
>
>.
>

CMDExec not working in sql agent job.

We have both our sql server and agent running under an
account of sqlservice. I run a winrar job in the agent as
a CMDExec step and it fails everytime. If I terminal
service into the box under the sqlservice account I can
create new files on both the source and destination file
systems. I can also run the job as a batch script from the
command line.
I'm baffeled, if I can run the job as the same account
the agent is running under and specify the job as that
same user. What is stopping this job from running?
"c:\Program Files\WinRAR\rar" a -ep1 "\\Ixcorpnas01
\public1\bmurtha\telnform
[DATE].rar" "G:\MSSQL\BACKUP\telnform.BAK"
I get this error:
Executed as user: IXCORPSQL01\SqlService. The process
could not be created for step 2 of job
0x0C7C1F1321CA844D884F666429C26A67 (reason: The system
cannot find the file specified). The step failed.
But runs fine on the command line when logged in as
sqlservice.
Please help,
Bryan
Hi Bryan
Is the service you are using a Domain account or a local account? The error
you get says it's executed as user 'IXCOPRSQL01\...' which to me sounds like
a local account rather than a domain account. If you are running it as a
local user, you might have problems getting to your '\\Ixcoprnas01\....'
share.
Regards
Steen
Bryan Murtha wrote:
> We have both our sql server and agent running under an
> account of sqlservice. I run a winrar job in the agent as
> a CMDExec step and it fails everytime. If I terminal
> service into the box under the sqlservice account I can
> create new files on both the source and destination file
> systems. I can also run the job as a batch script from the
> command line.
> I'm baffeled, if I can run the job as the same account
> the agent is running under and specify the job as that
> same user. What is stopping this job from running?
> "c:\Program Files\WinRAR\rar" a -ep1 "\\Ixcorpnas01
> \public1\bmurtha\telnform
> [DATE].rar" "G:\MSSQL\BACKUP\telnform.BAK"
> I get this error:
> Executed as user: IXCORPSQL01\SqlService. The process
> could not be created for step 2 of job
> 0x0C7C1F1321CA844D884F666429C26A67 (reason: The system
> cannot find the file specified). The step failed.
> But runs fine on the command line when logged in as
> sqlservice.
> Please help,
> Bryan
|||Hi Steve,
Oddly enough I didn't figure out what was happening
until I took that line and executed in Query Analyizer
with xp_cmdshell. It wound up it was path to RAR that was
blowing up. It had nothing to to with the NAS or the
backup path. I just stuck RAR in system32 and changed this:
"c:\Program Files\WinRAR\rar" to rar and it was all good.
Regards,
Bryan
>--Original Message--
>Hi Bryan
>Is the service you are using a Domain account or a local
account? The error
>you get says it's executed as user 'IXCOPRSQL01\...'
which to me sounds like
>a local account rather than a domain account. If you are
running it as a
>local user, you might have problems getting to
your '\\Ixcoprnas01\....'[vbcol=seagreen]
>share.
>Regards
>Steen
>
>Bryan Murtha wrote:
as[vbcol=seagreen]
the
>
>.
>

Clustering and Transactions

Hi,
When the primary server fails and the secondary starts to take over the job,
what will happen to the transactions opened on the primary node prior to
failure?
Thanks,
Leila
They all get rolled back and every connection is severed. Your client code
should re-try.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Leila" <leilas@.hotpop.com> wrote in message
news:OXWJoSdwEHA.3336@.TK2MSFTNGP11.phx.gbl...
Hi,
When the primary server fails and the secondary starts to take over the job,
what will happen to the transactions opened on the primary node prior to
failure?
Thanks,
Leila
|||"Leila" <leilas@.hotpop.com> wrote in message
news:OXWJoSdwEHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> When the primary server fails and the secondary starts to take over the
job,
> what will happen to the transactions opened on the primary node prior to
> failure?
You need to treat it just like one server was shut down and the other
started up.
Transactions are rolled back (or in a few cases forward) as appropriate.

> Thanks,
> Leila
>

Clustered SQL7 upgrade to SQL2000 fails to find default server

We are trying to upgrade to SQL2000 in a failover cluster
environment but the upgrade process is failing to identify
the default server and is instead creating a new named
instance of SQL2000 alongside SQL7 (the 'default' checkbox
on the upgrade wizard is greyed out and unchecked). The
production database is 125Gb so I don't want to use the
copy database wizard if possible. Can anyone suggest how
to get round this? Is it a registry setting?
TIA
JohnI am not sure what process you are taking to do this but here is the proper
sequence:
1. Uncluster SQL Server 7.0 cluster
2. Upgrade SQL Server 7.0 to a SQL Server 2000 default instance (putting
binaries on a local drive)
3. Upgrade the default instance of SQL Server 2000 ti a clustered intance
of SQL Server.
This is documetned in Books on Line:
Upgrading to a SQL SErver 2000 Failover Cluster
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Rand,
this is exactly the process we are trying to follow, but
the 2nd step fails because the upgrade process can't find
the default SQL7 server to upgrade in place and instead
creates a new instance of SQL2000. We have tried this over
and over again, even to the point of completely removing
and reinstalling SQL7. I've had no trouble before with
upgrading a standalone server so it's probably something
to do with the clustering. Any suggestions would be
greatly appreciated...

>--Original Message--
>I am not sure what process you are taking to do this but
here is the proper
>sequence:
>1. Uncluster SQL Server 7.0 cluster
>2. Upgrade SQL Server 7.0 to a SQL Server 2000 default
instance (putting
>binaries on a local drive)
>3. Upgrade the default instance of SQL Server 2000 ti a
clustered intance
>of SQL Server.
>This is documetned in Books on Line:
>Upgrading to a SQL SErver 2000 Failover Cluster
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>