Pay Attention Please...

Dear Sir,
Actually i want to ask, how to install the SQL Server Desktop Edition
2000 Client Tools only from the Command Prompt ? i have gone through the
internet but all the responds were about SQL Server Desktop Edition
2005, and it does not work for SQL Server Desktop Edition 2000.
I just could find the below command to install the full package:
setup.exe sapwd=abc123 sequritymode=sql
disablenetworkprotocols=0
Could you please help me to get this done,
Appreciate your kind consideration,
Best Regards,
Feri.
*** Sent via Developersdex http://www.codecomments.com ***
First, I would put something less like a junk mail subject in the subject. I
suggest: "SQL Server Desktop 2000 Installation".
Next, I would post this on the right newsgroup. This group focuses on
Connecting to SQL Server. You have an installation issue so I suggest using
microsoft.public.sqlserver.msde...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Feri Sh" <far.sharifi@.gmail.com> wrote in message
news:uwMDZQM2HHA.1168@.TK2MSFTNGP02.phx.gbl...
> Dear Sir,
> Actually i want to ask, how to install the SQL Server Desktop Edition
> 2000 Client Tools only from the Command Prompt ? i have gone through the
> internet but all the responds were about SQL Server Desktop Edition
> 2005, and it does not work for SQL Server Desktop Edition 2000.
> I just could find the below command to install the full package:
> setup.exe sapwd=abc123 sequritymode=sql
> disablenetworkprotocols=0
> Could you please help me to get this done,
> Appreciate your kind consideration,
>
> Best Regards,
> Feri.
> *** Sent via Developersdex http://www.codecomments.com ***
sql

Pay Attention Please...

Dear Sir,
Actually i want to ask, how to install the SQL Server Desktop Edition
2000 Client Tools only from the Command Prompt ? i have gone through the
internet but all the responds were about SQL Server Desktop Edition
2005, and it does not work for SQL Server Desktop Edition 2000.
I just could find the below command to install the full package:
setup.exe sapwd=abc123 sequritymode=sql
disablenetworkprotocols=0
Could you please help me to get this done,
Appreciate your kind consideration,
Best Regards,
Feri.
*** Sent via Developersdex http://www.codecomments.com ***First, I would put something less like a junk mail subject in the subject. I
suggest: "SQL Server Desktop 2000 Installation".
Next, I would post this on the right newsgroup. This group focuses on
Connecting to SQL Server. You have an installation issue so I suggest using
microsoft.public.sqlserver.msde...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Feri Sh" <far.sharifi@.gmail.com> wrote in message
news:uwMDZQM2HHA.1168@.TK2MSFTNGP02.phx.gbl...
> Dear Sir,
> Actually i want to ask, how to install the SQL Server Desktop Edition
> 2000 Client Tools only from the Command Prompt ? i have gone through the
> internet but all the responds were about SQL Server Desktop Edition
> 2005, and it does not work for SQL Server Desktop Edition 2000.
> I just could find the below command to install the full package:
> setup.exe sapwd=abc123 sequritymode=sql
> disablenetworkprotocols=0
> Could you please help me to get this done,
> Appreciate your kind consideration,
>
> Best Regards,
> Feri.
> *** Sent via Developersdex http://www.codecomments.com ***

Password not Added after Installation

Hi,
I recently installed MSDE 2000, by giving the following to
setup parameters in the Command Prompt:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\> D:\MSDE2000\Setup.Exe SAPWD="apple" SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 /L*v C:\MSDELog.txt
C:\>
In log file, it did mentioned that the installation is
successfull at it's end of the file. However the SA
password is blank eventhough I gave the password
as "apple". Why did this happen. Is there anything wrong
in my setup parameter mentioned in the Command Prompt?
Help required on this matter, cos there are several
computers left to install MSDE 2000 and hoping to use the
above setup parameters.
Thanx in advance,
shahzard.
hi shahzard,
"Shahzard" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:574901c47465$e8574990$a301280a@.phx.gbl...
> Hi,
> I recently installed MSDE 2000, by giving the following to
> setup parameters in the Command Prompt:
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\> D:\MSDE2000\Setup.Exe SAPWD="apple" SECURITYMODE=SQL
> DISABLENETWORKPROTOCOLS=0 /L*v C:\MSDELog.txt
> C:\>
> In log file, it did mentioned that the installation is
> successfull at it's end of the file. However the SA
> password is blank eventhough I gave the password
> as "apple". Why did this happen. Is there anything wrong
> in my setup parameter mentioned in the Command Prompt?
> Help required on this matter, cos there are several
> computers left to install MSDE 2000 and hoping to use the
> above setup parameters.
the command line is ok, and i reproduced the problem on a Win2k box, where
SECURITYMODE=SQL has not been honored...
will investigate a little further... for workaround, run Regedit, locate
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\MSSQLServer
and set LoginMode key = 2
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Passing system variables to stored procedure

How do I pass system variables to a stored procedure? Is it possible to have an OLE DB transformation with the following sql command: exec InsertIntoLog @.MachineName, @.TaskName...? Do I have to use a Derived Transformation first to 'convert' variables into columns and then use exec InsertIntoLog ?, ? ...

Thanks for the help.

In the execute sql task refer to parameters with question marks. Then on the parameter mapping page of the execute sql task you can map the question marks to variables.

|||

Thanx...I need the same for the OLE DB transformation

|||

Do you mean OLE DB source? It's pretty much the same as the execute sql task.

Put question mark's where you want the variable then click the 'parameters' button and choose the variable that you want to use for it.

If your source provider (DB2) doesn't allow you to pass parameters you'll have to create a variable that builds the sql statement referencing another variable. Then change the 'data access mode' in the ole db source to 'sql command from variable'.

Good luck.

|||

I mean OLE DB Command Transformation...

|||

I think the answer to your original question you want is yes, use the Derived Column to make a variable into a column so that you can use it, and question marks are the placeholders.

|||

Audit transformation can also be used (I need to populate log table).

Passing system variables to stored procedure

How do I pass system variables to a stored procedure? Is it possible to have an OLE DB transformation with the following sql command: exec InsertIntoLog @.MachineName, @.TaskName...? Do I have to use a Derived Transformation first to 'convert' variables into columns and then use exec InsertIntoLog ?, ? ...

Thanks for the help.

In the execute sql task refer to parameters with question marks. Then on the parameter mapping page of the execute sql task you can map the question marks to variables.

|||

Thanx...I need the same for the OLE DB transformation

|||

Do you mean OLE DB source? It's pretty much the same as the execute sql task.

Put question mark's where you want the variable then click the 'parameters' button and choose the variable that you want to use for it.

If your source provider (DB2) doesn't allow you to pass parameters you'll have to create a variable that builds the sql statement referencing another variable. Then change the 'data access mode' in the ole db source to 'sql command from variable'.

Good luck.

|||

I mean OLE DB Command Transformation...

|||

I think the answer to your original question you want is yes, use the Derived Column to make a variable into a column so that you can use it, and question marks are the placeholders.

|||

Audit transformation can also be used (I need to populate log table).

Passing status back from Command line application to SQL Job

Hi,

I have created a job in SQL Server 2005 in which one of the step executes a .NET console application which is created in .NET to update some status to database before the next step. i need some help in sending some status back to sql job when i come accross any problem in the console application for ex when there is a exception i need to send some status to the job, so the job gets failed permanently. i tried few other methods of updating some temporary status database with this error information and have another intermediate step in the job to check for the status... it worked but i dont like doing it. please let me know if there is any other method to do this.

Thanks in advance

Hariharan

Are you doing anything with SSIS, or is this a SQL Server Agent question only?|||I'ts in SSIS as one of the step.|||

Hari Haran wrote:

I'ts in SSIS as one of the step.

Please provide more details then... As it reads, it sounds like it has nothing to do with SSIS.

Thanks,
Phil|||

To make the to step fail, just ensure the applicaton returns a suitable exit code. Take a closer look at the Job Step dialog and note of the "Process exit code of a successful cvommand:" option. Match this to you exist code as required. If this is the SSIS task after all, then look at the properties SuccessValue and FailTaskIfRetrnCodeIsNotSuccessValue.

You have set an exit code? If not see -

Environment.Exit Method (System)
(http://msdn2.microsoft.com/en-us/library/system.environment.exit.aspx)

Passing status back from Command line application to SQL Job

Hi,

I have created a job in SQL Server 2005 in which one of the step executes a .NET console application which is created in .NET to update some status to database before the next step. i need some help in sending some status back to sql job when i come accross any problem in the console application for ex when there is a exception i need to send some status to the job, so the job gets failed permanently. i tried few other methods of updating some temporary status database with this error information and have another intermediate step in the job to check for the status... it worked but i dont like doing it. please let me know if there is any other method to do this.

Thanks in advance

Hariharan

Are you doing anything with SSIS, or is this a SQL Server Agent question only?|||I'ts in SSIS as one of the step.|||

Hari Haran wrote:

I'ts in SSIS as one of the step.

Please provide more details then... As it reads, it sounds like it has nothing to do with SSIS.

Thanks,
Phil|||

To make the to step fail, just ensure the applicaton returns a suitable exit code. Take a closer look at the Job Step dialog and note of the "Process exit code of a successful cvommand:" option. Match this to you exist code as required. If this is the SSIS task after all, then look at the properties SuccessValue and FailTaskIfRetrnCodeIsNotSuccessValue.

You have set an exit code? If not see -

Environment.Exit Method (System)
(http://msdn2.microsoft.com/en-us/library/system.environment.exit.aspx)