(ObjKommun IN (xxxx%, oooo%))

My question, is it valid to use "IN" as in "LIKE" conserning strings? (Using the "%" operator)
Thx in advance!Hello,

you cant you % in this way (for Oracle). Use SUBSTR(var, start, length)

Hope this helps ?

Greetz

Manfred Peter
(Alligator Company)
http://www.alligatorsql.de|||This is just a short copy of a SP im using in SQL server... now the problem appears if there will be to many parameters involved.. (HUGE query)

My main problem is how to reduce the length of the query..

So, instead of doing it like this..:

AND (((xxxx like 'yyyy%') OR (xxxx like 'zzzz%')))

I was thinking of doing like this..:

xxxx IN ('yyyy%', 'zzzz%')

But when im using the "IN" im not able to use the % (Cause sometimes strings are weird) and no result is shown, but when removing the % i get the satisfying result, not depending on Case sensitivity which is perfect, but still...

And im really really lousy to explain things, hope its ok anyways ;)|||No, IN cannot be used as a substitute for 'like', it will not work. You could try looking at applying a string function on the column side, e.g. WHERE substring( mycolumn, 0, 4) IN ( 'stri', '1234', 'etc.' )|||Okay, thx for the response.

Think I will use "IN" but forget about trying to make it work like "LIKE" :)

Most important is that the length of the query is shortened.

Best wishes from Sweden.|||Thats it :)

Greetings
Manfred Peter
(Alligator Company)
http://www.alligatorsql.com

"The feature(s) specified are not valid for this edition of SQL Server" error when ins

I've successfully installed SQL Server 2005 Standard Edition on an Enterprise edition of Windows Server 2003 x64. I'm now (and also tried & failed during the install of the database engine) attempting to install the "Management Tools" component on the same server. However, in all my attempts to do so, I receive the following error:

The feature(s) specified are not valid for this edition of SQL Server

The message box does not list the features that are not valid but since the only item I've selected to install is the "Management Tools" option under "Client Components" it obviously points to something with that.

Am I missing something or are the Management Tools not supported in my config - most notably SQL Server 2005 Standard edition running on Windows Server 2003 x64?

Thanks.

- Lance

Colorado State University

I was finally able to install the "Management Tools" with a pretty simple solution: Install using the installer files directly off of the physical DVD. My prior attempts had all been using a copy of the files on the DVD stored locally on the server. Incidently, I had used the same copied files to successfully install the DB engine and SSIS. Go figure.

"New request is not allowed to start because it should come with valid transaction descript

Hi all,
We are getting "New request is not allowed to start because it should come with valid transaction descriptor" when using transactions against SQL 2005. As I understand it, it's a bug that occurs after some statement has terminated against the database; see http://lab.msdn.microsoft.com/productfeedback/ViewWorkaround.aspx?FeedbackID=FDBK46530#1

Now, I wonder if there is a hotfix coming soon on this?

/Daniel

I have the same error description but within a different setup. Running SQL Server 2005 on Windows Server 2003 R2. Connecting to database use SNAC from VC6 application. Application is written still with old ODBC technology. I have switched back to the SQL Server driver in the odbc connection. Anyone have any ideas surrounding this problem, I also get a lot of query timeouts and have done the usual checks. Ensure no deadlocks occurs. Set query timeout value higher. Doing a google revealed that everyone getting this error has a managed code app using sqlclient, I geuss that this is the same classes MS used within the sql native client driver and therefore the hotfix will sort out this problem?

|||http://support.microsoft.com/kb/916002|||If you contact customer support directly they should be able to provide you with more information about how to resolve this issue.

"New request is not allowed to start because it should come with valid transaction descript

Hi all,
We are getting "New request is not allowed to start because it should come with valid transaction descriptor" when using transactions against SQL 2005. As I understand it, it's a bug that occurs after some statement has terminated against the database; see http://lab.msdn.microsoft.com/productfeedback/ViewWorkaround.aspx?FeedbackID=FDBK46530#1

Now, I wonder if there is a hotfix coming soon on this?

/Daniel

I have the same error description but within a different setup. Running SQL Server 2005 on Windows Server 2003 R2. Connecting to database use SNAC from VC6 application. Application is written still with old ODBC technology. I have switched back to the SQL Server driver in the odbc connection. Anyone have any ideas surrounding this problem, I also get a lot of query timeouts and have done the usual checks. Ensure no deadlocks occurs. Set query timeout value higher. Doing a google revealed that everyone getting this error has a managed code app using sqlclient, I geuss that this is the same classes MS used within the sql native client driver and therefore the hotfix will sort out this problem?

|||http://support.microsoft.com/kb/916002|||If you contact customer support directly they should be able to provide you with more information about how to resolve this issue.

"New request is not allowed to start because it should come with valid transaction descript

Hi all,
We are getting "New request is not allowed to start because it should come with valid transaction descriptor" when using transactions against SQL 2005. As I understand it, it's a bug that occurs after some statement has terminated against the database; see http://lab.msdn.microsoft.com/productfeedback/ViewWorkaround.aspx?FeedbackID=FDBK46530#1

Now, I wonder if there is a hotfix coming soon on this?

/Daniel

I have the same error description but within a different setup. Running SQL Server 2005 on Windows Server 2003 R2. Connecting to database use SNAC from VC6 application. Application is written still with old ODBC technology. I have switched back to the SQL Server driver in the odbc connection. Anyone have any ideas surrounding this problem, I also get a lot of query timeouts and have done the usual checks. Ensure no deadlocks occurs. Set query timeout value higher. Doing a google revealed that everyone getting this error has a managed code app using sqlclient, I geuss that this is the same classes MS used within the sql native client driver and therefore the hotfix will sort out this problem?

|||http://support.microsoft.com/kb/916002|||If you contact customer support directly they should be able to provide you with more information about how to resolve this issue.

%1 is not a valid WIN32 application

We've recently installed SQL SP4 on one of our servers and are experiencing
the following problem:
SQLSERVERAGENT fails to start after the service pack has been installed with
error:
%1 is not a valid WIN32 application
The system log reports pretty much the same error.
We had to resort to uninstalling SQL server completely. Reinstalling SQL
server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
problems.
Applying sp4 (and rebooting) results in the same error.
Please let me know if you are able to assist with this.Hi
Did you check out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812486
John
"Reuben Rinquest" wrote:
> We've recently installed SQL SP4 on one of our servers and are experiencing
> the following problem:
> SQLSERVERAGENT fails to start after the service pack has been installed with
> error:
> %1 is not a valid WIN32 application
> The system log reports pretty much the same error.
> We had to resort to uninstalling SQL server completely. Reinstalling SQL
> server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
> problems.
> Applying sp4 (and rebooting) results in the same error.
> Please let me know if you are able to assist with this.
>|||Thank you John, This solution worked
"John Bell" wrote:
> Hi
> Did you check out:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;812486
> John
> "Reuben Rinquest" wrote:
> > We've recently installed SQL SP4 on one of our servers and are experiencing
> > the following problem:
> >
> > SQLSERVERAGENT fails to start after the service pack has been installed with
> > error:
> > %1 is not a valid WIN32 application
> > The system log reports pretty much the same error.
> > We had to resort to uninstalling SQL server completely. Reinstalling SQL
> > server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
> > problems.
> >
> > Applying sp4 (and rebooting) results in the same error.
> >
> > Please let me know if you are able to assist with this.
> >
> >

%1 is not a valid WIN32 application

We've recently installed SQL SP4 on one of our servers and are experiencing
the following problem:
SQLSERVERAGENT fails to start after the service pack has been installed with
error:
%1 is not a valid WIN32 application
The system log reports pretty much the same error.
We had to resort to uninstalling SQL server completely. Reinstalling SQL
server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
problems.
Applying sp4 (and rebooting) results in the same error.
Please let me know if you are able to assist with this.
Hi
Did you check out:
http://support.microsoft.com/default...b;en-us;812486
John
"Reuben Rinquest" wrote:

> We've recently installed SQL SP4 on one of our servers and are experiencing
> the following problem:
> SQLSERVERAGENT fails to start after the service pack has been installed with
> error:
> %1 is not a valid WIN32 application
> The system log reports pretty much the same error.
> We had to resort to uninstalling SQL server completely. Reinstalling SQL
> server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
> problems.
> Applying sp4 (and rebooting) results in the same error.
> Please let me know if you are able to assist with this.
>
|||Thank you John, This solution worked
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Did you check out:
> http://support.microsoft.com/default...b;en-us;812486
> John
> "Reuben Rinquest" wrote:

%1 is not a valid WIN32 application

We've recently installed SQL SP4 on one of our servers and are experiencing
the following problem:
SQLSERVERAGENT fails to start after the service pack has been installed with
error:
%1 is not a valid WIN32 application
The system log reports pretty much the same error.
We had to resort to uninstalling SQL server completely. Reinstalling SQL
server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
problems.
Applying sp4 (and rebooting) results in the same error.
Please let me know if you are able to assist with this.Hi
Did you check out:
http://support.microsoft.com/defaul...kb;en-us;812486
John
"Reuben Rinquest" wrote:

> We've recently installed SQL SP4 on one of our servers and are experiencin
g
> the following problem:
> SQLSERVERAGENT fails to start after the service pack has been installed wi
th
> error:
> %1 is not a valid WIN32 application
> The system log reports pretty much the same error.
> We had to resort to uninstalling SQL server completely. Reinstalling SQL
> server (and applying sp3a) works fine and SQLSERVERAGENT starts without an
y
> problems.
> Applying sp4 (and rebooting) results in the same error.
> Please let me know if you are able to assist with this.
>|||Thank you John, This solution worked
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Did you check out:
> http://support.microsoft.com/defaul...kb;en-us;812486
> John
> "Reuben Rinquest" wrote:
>