Showing posts with label sql2005. Show all posts
Showing posts with label sql2005. Show all posts

Friday, March 30, 2012

parameter problem in sql2005 sp

in sql2005 store procedure is accepting the varchar value which is more than the parameter's varchar value size it is not giving any exception error but removes the remaining character from right side

Example :

Table

-

create table employee

(Empname Varchar(5), EmpNo Int)

Procedure

create procedure test (@.para1 Varchar(5))

as

SELECT * FROM employee WHRE empNAME=@.PARA1

Execution

--

exec test 'ABCDEFGH'

it consider only 'ABCDE' and ignores remaining character without giving any exception error.

Thanks,

It is the specification. Not only in 2005 earlier versions also use the same specification.

But in sql server 2005 you can overcome this issue using Varchar(max) it never truncate the value.

Declare @.A varchar(1), @.B varchar(Max);

Set @.A = '1234' --Truncated value

Set @.B = '1234' --Never Truncate the value

Select @.A, @.B

Note:

The character length is only validated on Insert & Update statement.

|||thanks fo reply

parameter problem in sql2005 sp

in sql2005 store procedure is accepting the varchar value which is more than the parameter's varchar value size it is not giving any exception error but removes the remaining character from right side

Example :

Table

-

create table employee

(Empname Varchar(5), EmpNo Int)

Procedure

create procedure test (@.para1 Varchar(5))

as

SELECT * FROM employee WHRE empNAME=@.PARA1

Execution

--

exec test 'ABCDEFGH'

it consider only 'ABCDE' and ignores remaining character without giving any exception error.

Thanks,

It is the specification. Not only in 2005 earlier versions also use the same specification.

But in sql server 2005 you can overcome this issue using Varchar(max) it never truncate the value.

Declare @.A varchar(1), @.B varchar(Max);

Set @.A = '1234' --Truncated value

Set @.B = '1234' --Never Truncate the value

Select @.A, @.B

Note:

The character length is only validated on Insert & Update statement.

|||thanks fo replysql

Wednesday, March 21, 2012

Parallel processing not supported in standard edition (use developer)

Hi,

I have a developer edition of SQL2005 upgraded to SP1 plus hotfixes on the dev box where I create my stuff.

Now, when I try to set a SSIS cube processing task to process in parallel, it tells me "Parallel processing is not supported in standard edition of analysis services."

Why?

I cannot edit the package on the enterprise edition used on production. I have to deploy as it is on dev.

Thanks,

Philippe

Hi,

The SQL Server build is 9.00.2153.00

I note that the problem exist only in the SSIS task. If I specify the parallel processing option when processing from management Studio, I do not get the error.

I bet it is a bug in SP1 or in the hotfix

Philippe

|||I have this exact same problem - I'm running Enterprise Edition, but in SSIS I get the error that "Parallel processing is not supported on STandard edition of Analysis Services". Can anyone confirm if this is a known issue and whether there is a workaround?

Parallel processing not supported in standard edition (use developer)

Hi,

I have a developer edition of SQL2005 upgraded to SP1 plus hotfixes on the dev box where I create my stuff.

Now, when I try to set a SSIS cube processing task to process in parallel, it tells me "Parallel processing is not supported in standard edition of analysis services."

Why?

I cannot edit the package on the enterprise edition used on production. I have to deploy as it is on dev.

Thanks,

Philippe

Hi,

The SQL Server build is 9.00.2153.00

I note that the problem exist only in the SSIS task. If I specify the parallel processing option when processing from management Studio, I do not get the error.

I bet it is a bug in SP1 or in the hotfix

Philippe

|||I have this exact same problem - I'm running Enterprise Edition, but in SSIS I get the error that "Parallel processing is not supported on STandard edition of Analysis Services". Can anyone confirm if this is a known issue and whether there is a workaround?