compare child records - t-sql

I have four records, each containing a date.
LineNo ShipDate RefLine
--
1 1/30/05 <null>
2 1/1/05 1
3 1/15/05 1
I want to compare the date in line 1 to 2, then 2 to 3
Basically, the lines belong to the same order. What is going on is
when we want to change a ship date for an order line, we make a copy of
the original line (line 1 in this case), close the copied line out
(line 2 or 3) and reference the original line in it using a
user-defined field (labeled RefLine). The user then goes back to the
original line and changes the ship date. We are trying to track how
many times an orderline is pushed out, and calculate the days between.
The reason we cant just make a new line and set the date there has to
do with links in the original that can't be easily changed. basically
I want my query to look like:
LineNo ShipDate RefLine DaysMoved
---
1 1/30/05 <null> 15
2 1/1/05 1 <null> (this was org ship date)
3 1/15/05 1 15
---
Total 30
I can get the group total just by getting the difference between the
current and min dates, but in my report if I sum the over all using
this method I get 60 days because there are two detail lines.
Anyone help is appreciated...I figured it out. Here is the query I used:
SELECT
co.CUSTOMER_ID
, co.ORDER_DATE
, c.NAME AS 'CUSTOMER_NAME'
, cl.CUST_ORDER_ID AS 'ORDER_ID'
, cl.LINE_NO
, cl.ORDER_QTY
, cl.PART_ID
, m.LINE_NO AS 'MOVE_LINE_NO'
, m.DESIRED_SHIP_DATE
, m.REASON_CODE
, m.REASON_CODE_DESCRIPTION
, (SELECT TOP 1 DESIRED_SHIP_DATE FROM RV_MOVED_SHIP_DATES WHERE
order_id = cl.CUST_ORDER_ID AND
line_no > m.line_no AND
COPIED_FROM_LN = cl.LINE_NO AND
m.DESIRED_SHIP_DATE <
DESIRED_SHIP_DATE) AS 'NEXT_SHIP_DATE'
, cl.DESIRED_SHIP_DATE AS 'CURRENT_DATE'
, m.COPIED_FROM_LN
FROM
dbo.CUSTOMER_ORDER co
INNER JOIN
dbo.CUST_ORDER_LINE cl ON co.ID = cl.CUST_ORDER_ID
INNER JOIN
dbo.CUSTOMER c ON co.CUSTOMER_ID = c.ID
INNER JOIN
dbo.RV_MOVED_SHIP_DATES m ON cl.LINE_NO =
m.COPIED_FROM_LN AND
cl.CUST_ORDER_ID = m.ORDER_ID
WHERE
co.ORDER_DATE BETWEEN @.START_DATE AND @.END_DATE
ORDER BY
co.CUSTOMER_ID, cl.CUST_ORDER_ID, cl.LINE_NO, m.LINE_NO
Stephen wrote:
> I have four records, each containing a date.
> LineNo ShipDate RefLine
> --
> 1 1/30/05 <null>
> 2 1/1/05 1
> 3 1/15/05 1
> I want to compare the date in line 1 to 2, then 2 to 3
> Basically, the lines belong to the same order. What is going on is
> when we want to change a ship date for an order line, we make a copy of
> the original line (line 1 in this case), close the copied line out
> (line 2 or 3) and reference the original line in it using a
> user-defined field (labeled RefLine). The user then goes back to the
> original line and changes the ship date. We are trying to track how
> many times an orderline is pushed out, and calculate the days between.
> The reason we cant just make a new line and set the date there has to
> do with links in the original that can't be easily changed. basically
> I want my query to look like:
> LineNo ShipDate RefLine DaysMoved
> ---
> 1 1/30/05 <null> 15
> 2 1/1/05 1 <null> (this was org ship date)
> 3 1/15/05 1 15
> ---
> Total 30
> I can get the group total just by getting the difference between the
> current and min dates, but in my report if I sum the over all using
> this method I get 60 days because there are two detail lines.
> Anyone help is appreciated...

command line uninstall of sql express 2005

Another developer is writing the install/uninstall for our app and we're not
sure about the best way to uninstall the database component when the app is
uninstalled. Basically our app installs sql express 2005 ( + other .net stuff
) during install using the command line options and that works great. When it
comes to uninstall we have only one option at the moment - have the user go
to the control panel and manually uninstall the db. Is there an automated way
to remove the db from a machine or a way to issue a batchfile command w/
params? The user doesn't need to maintain this special db instance so want to
remove it automatically.
thanks,
Paul.
hi Paul,
paul wrote:
> Another developer is writing the install/uninstall for our app and
> we're not sure about the best way to uninstall the database component
> when the app is uninstalled. Basically our app installs sql express
> 2005 ( + other .net stuff ) during install using the command line
> options and that works great. When it comes to uninstall we have only
> one option at the moment - have the user go to the control panel and
> manually uninstall the db. Is there an automated way to remove the db
> from a machine or a way to issue a batchfile command w/ params? The
> user doesn't need to maintain this special db instance so want to
> remove it automatically.
> thanks,
> Paul.
http://msdn2.microsoft.com/en-us/lib...installscripts
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply

command line tools to make flat backups

Does anyone know if there is a way to run a command at the DOS prompt
to make a complete flat file (.bak) backup of a database? I know you
can do this using the enterprise manager by right clicking on the
db..., but I am curious to find out if I can add a command into my
batch scripts as part of my code migration procedures?
Thanks!
-Mike
You could use osql e.g.
osql -Q "BACKUP DATABASE pubs TO DISK = 'e:\backups\pubs.bak'" -E
Ray Mond
|||Yes, Ray, Perfecto!! That's what I was looking for. Thanks for the
help...
Happy Holidays!!

Command line tools missing

I have read about the dtexec utility, but I can not find this on my installation. Is it a seperate install or do I need to reinstall?

Bob

How I found it was by clicking on Start-->Run then entering in dtexecui.exe|||

Bob Everland wrote:

I have read about the dtexec utility, but I can not find this on my installation. Is it a seperate install or do I need to reinstall?

Bob

You'll need to install SQL Server Integration Services. Installing Workstation components is not enough.

-Jamie

Command line to take one cluster Group offline

We have an issue in our environment that requires me to bounce a cluster
group and associated services ever other day and Im getting tired of it (out
of control developers).
I would like to create a script that I can schedule to do this and would
like to know if there is a command line that will take just one cluster
group offline and then bring it back online. I have under groups in my
cluster admin: Cluster information, DataMirror, SQL Backup, SQL Data and SQL
Logs. I need to bounce the DataMirror one.
Thanks!!
Derrick
I figured it out after tinkering.. it is:
for my example
cluster /cluster:sqlcluster group datamirror /offline
thx..
derrick
"Turbo [GEEK]" <riveradl@.hotmail.com> wrote in message
news:u7PIk4I4FHA.3292@.tk2msftngp13.phx.gbl...
> We have an issue in our environment that requires me to bounce a cluster
> group and associated services ever other day and Im getting tired of it
> (out of control developers).
> I would like to create a script that I can schedule to do this and would
> like to know if there is a command line that will take just one cluster
> group offline and then bring it back online. I have under groups in my
> cluster admin: Cluster information, DataMirror, SQL Backup, SQL Data and
> SQL Logs. I need to bounce the DataMirror one.
> Thanks!!
> Derrick
>

Command line to pass parameters in SQL

Hi,
Do you know if any command I can use to pass parameters into reports,
generate PDF report format and drop it into a shared folder? Thanks.
ChuckYou can pass parameters ,and create PDF from a URL report request, but I do
not think you can specify a save directory
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Chuck" <Chuck@.discussions.microsoft.com> wrote in message
news:297FC292-95E4-408D-9E93-78C698A98AFC@.microsoft.com...
> Hi,
> Do you know if any command I can use to pass parameters into reports,
> generate PDF report format and drop it into a shared folder? Thanks.
>
> Chuck

Command line to find RAID Level

I have about 20 servers and want to compile a report to
find out RAID level without using the OS
Does anyone know how we can d that from command line so
that we can wrap that in SQL
thanks
This is typically a hardware setting associated with the Raid Card in your
server. You should check with your hardware vendor to see if they have a
tool for this.
"Ap" <anonymous@.discussions.microsoft.com> wrote in message
news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>I have about 20 servers and want to compile a report to
> find out RAID level without using the OS
> Does anyone know how we can d that from command line so
> that we can wrap that in SQL
> thanks
|||But if we are doing software raid from windows 2003 then
can we know wha tis the type by using any commands?

>--Original Message--
>This is typically a hardware setting associated with the
Raid Card in your
>server. You should check with your hardware vendor to
see if they have a
>tool for this.
>
>"Ap" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>
>.
>
|||Do the following yield anything:
WMIC DISKDRIVE
WMIC LOGICALDISK
WMIC IDECONTROLLER
WMIC SCSICONTROLLER
http://www.aspfaq.com/
(Reverse address to reply.)
"Ap" <anonymous@.discussions.microsoft.com> wrote in message
news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
> I have about 20 servers and want to compile a report to
> find out RAID level without using the OS
> Does anyone know how we can d that from command line so
> that we can wrap that in SQL
> thanks
|||It does but no the RAID level that says 1,5
thnaks for the effort
>--Original Message--
>Do the following yield anything:
>WMIC DISKDRIVE
>WMIC LOGICALDISK
>WMIC IDECONTROLLER
>WMIC SCSICONTROLLER
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Ap" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>
>.
>

Command line to find RAID Level

I have about 20 servers and want to compile a report to
find out RAID level without using the OS
Does anyone know how we can d that from command line so
that we can wrap that in SQL
thanksThis is typically a hardware setting associated with the Raid Card in your
server. You should check with your hardware vendor to see if they have a
tool for this.
"Ap" <anonymous@.discussions.microsoft.com> wrote in message
news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>I have about 20 servers and want to compile a report to
> find out RAID level without using the OS
> Does anyone know how we can d that from command line so
> that we can wrap that in SQL
> thanks|||But if we are doing software raid from windows 2003 then
can we know wha tis the type by using any commands?
>--Original Message--
>This is typically a hardware setting associated with the
Raid Card in your
>server. You should check with your hardware vendor to
see if they have a
>tool for this.
>
>"Ap" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>>I have about 20 servers and want to compile a report to
>> find out RAID level without using the OS
>> Does anyone know how we can d that from command line so
>> that we can wrap that in SQL
>> thanks
>
>.
>|||Do the following yield anything:
WMIC DISKDRIVE
WMIC LOGICALDISK
WMIC IDECONTROLLER
WMIC SCSICONTROLLER
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ap" <anonymous@.discussions.microsoft.com> wrote in message
news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
> I have about 20 servers and want to compile a report to
> find out RAID level without using the OS
> Does anyone know how we can d that from command line so
> that we can wrap that in SQL
> thanks|||It does but no the RAID level that says 1,5
thnaks for the effort
>--Original Message--
>Do the following yield anything:
>WMIC DISKDRIVE
>WMIC LOGICALDISK
>WMIC IDECONTROLLER
>WMIC SCSICONTROLLER
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Ap" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>> I have about 20 servers and want to compile a report to
>> find out RAID level without using the OS
>> Does anyone know how we can d that from command line so
>> that we can wrap that in SQL
>> thanks
>
>.
>

Command line to find RAID Level

I have about 20 servers and want to compile a report to
find out RAID level without using the OS
Does anyone know how we can d that from command line so
that we can wrap that in SQL
thanksThis is typically a hardware setting associated with the Raid Card in your
server. You should check with your hardware vendor to see if they have a
tool for this.
"Ap" <anonymous@.discussions.microsoft.com> wrote in message
news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>I have about 20 servers and want to compile a report to
> find out RAID level without using the OS
> Does anyone know how we can d that from command line so
> that we can wrap that in SQL
> thanks|||But if we are doing software raid from windows 2003 then
can we know wha tis the type by using any commands?

>--Original Message--
>This is typically a hardware setting associated with the
Raid Card in your
>server. You should check with your hardware vendor to
see if they have a
>tool for this.
>
>"Ap" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>
>.
>|||Do the following yield anything:
WMIC DISKDRIVE
WMIC LOGICALDISK
WMIC IDECONTROLLER
WMIC SCSICONTROLLER
http://www.aspfaq.com/
(Reverse address to reply.)
"Ap" <anonymous@.discussions.microsoft.com> wrote in message
news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
> I have about 20 servers and want to compile a report to
> find out RAID level without using the OS
> Does anyone know how we can d that from command line so
> that we can wrap that in SQL
> thanks|||It does but no the RAID level that says 1,5
thnaks for the effort
>--Original Message--
>Do the following yield anything:
>WMIC DISKDRIVE
>WMIC LOGICALDISK
>WMIC IDECONTROLLER
>WMIC SCSICONTROLLER
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Ap" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0baf01c4f449$91f551a0$a401280a@.phx.gbl...
>
>.
>

Command Line SQL Server Shutdown??

I need to write a script to run at a specific time to shutdown a
SQL Server. I also need to start the SQL Server back up.
Does anyone know the command line that could be used in a BAT script
to shutdown and then restart a SQL Server v.7
Please reply via email and post
Thanks in Advance,
JohnJohn,
You can use NET STOP and NET START, as in
net stop MSSQLServer
net start MSSQLServer
Please note that if sqlserveragent is dependent, then stop that service
first before stopping SQLServer service.These commands are documented in
BooksOnLine.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"John" <jkimb@.kimberlyconsulting.com> wrote in message
news:pan.2004.05.07.21.19.25.367752@.kimberlyconsulting.com...
> I need to write a script to run at a specific time to shutdown a
> SQL Server. I also need to start the SQL Server back up.
> Does anyone know the command line that could be used in a BAT script
> to shutdown and then restart a SQL Server v.7
> Please reply via email and post
> Thanks in Advance,
> John
>|||"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uEvi3qHNEHA.2064@.TK2MSFTNGP12.phx.gbl...
> John,
> You can use NET STOP and NET START, as in
> net stop MSSQLServer
> net start MSSQLServer
> Please note that if sqlserveragent is dependent, then stop that service
> first before stopping SQLServer service.These commands are documented in
> BooksOnLine.
In that case net stop mssqlserver /y also stops dependent services

Command Line SQL Server Shutdown??

I need to write a script to run at a specific time to shutdown a
SQL Server. I also need to start the SQL Server back up.
Does anyone know the command line that could be used in a BAT script
to shutdown and then restart a SQL Server v.7
Please reply via email and post
Thanks in Advance,
John
John,
You can use NET STOP and NET START, as in
net stop MSSQLServer
net start MSSQLServer
Please note that if sqlserveragent is dependent, then stop that service
first before stopping SQLServer service.These commands are documented in
BooksOnLine.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"John" <jkimb@.kimberlyconsulting.com> wrote in message
news:pan.2004.05.07.21.19.25.367752@.kimberlyconsul ting.com...
> I need to write a script to run at a specific time to shutdown a
> SQL Server. I also need to start the SQL Server back up.
> Does anyone know the command line that could be used in a BAT script
> to shutdown and then restart a SQL Server v.7
> Please reply via email and post
> Thanks in Advance,
> John
>
|||"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uEvi3qHNEHA.2064@.TK2MSFTNGP12.phx.gbl...
> John,
> You can use NET STOP and NET START, as in
> net stop MSSQLServer
> net start MSSQLServer
> Please note that if sqlserveragent is dependent, then stop that service
> first before stopping SQLServer service.These commands are documented in
> BooksOnLine.
In that case net stop mssqlserver /y also stops dependent services

Command line qeury of service

I have been looking at SC.exe from the resource kit to query sql server
services from command line. Anyone have any recommendations other than this
to do so.
I was looking to query all my sql servers to check services and output to a
file.
Russ,
How about VBScript and WMI? Or VBScript and SQL-DMO?
HTH
Jerry
"RussN" <RussN@.discussions.microsoft.com> wrote in message
news:EEA1A919-672C-441F-8F4D-9838F67650FE@.microsoft.com...
>I have been looking at SC.exe from the resource kit to query sql server
> services from command line. Anyone have any recommendations other than
> this
> to do so.
> I was looking to query all my sql servers to check services and output to
> a
> file.

Command line qeury of service

I have been looking at SC.exe from the resource kit to query sql server
services from command line. Anyone have any recommendations other than this
to do so.
I was looking to query all my sql servers to check services and output to a
file.Russ,
How about VBScript and WMI? Or VBScript and SQL-DMO?
HTH
Jerry
"RussN" <RussN@.discussions.microsoft.com> wrote in message
news:EEA1A919-672C-441F-8F4D-9838F67650FE@.microsoft.com...
>I have been looking at SC.exe from the resource kit to query sql server
> services from command line. Anyone have any recommendations other than
> this
> to do so.
> I was looking to query all my sql servers to check services and output to
> a
> file.

Command line qeury of service

I have been looking at SC.exe from the resource kit to query sql server
services from command line. Anyone have any recommendations other than this
to do so.
I was looking to query all my sql servers to check services and output to a
file.Russ,
How about VBScript and WMI? Or VBScript and SQL-DMO?
HTH
Jerry
"RussN" <RussN@.discussions.microsoft.com> wrote in message
news:EEA1A919-672C-441F-8F4D-9838F67650FE@.microsoft.com...
>I have been looking at SC.exe from the resource kit to query sql server
> services from command line. Anyone have any recommendations other than
> this
> to do so.
> I was looking to query all my sql servers to check services and output to
> a
> file.

command line prompt to open sql server enterprise manager

Is there a command line prompt that will invoke SQL Server Enterprise
Manager, like 'isqlw' for Query Analyser?
I know that there used to be one for 6.5 to perform this.
Many thanks in advanceC:\WINDOWS\system32\mmc.exe /s "C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC"
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"billu" <billu@.discussions.microsoft.com> wrote in message
news:E8719A48-FB22-4ED4-934C-5A2AB9D30636@.microsoft.com...
> Is there a command line prompt that will invoke SQL Server Enterprise
> Manager, like 'isqlw' for Query Analyser?
> I know that there used to be one for 6.5 to perform this.
> Many thanks in advance

Command line printing to specific printers, and specific trays

Hi All,

Could you guys please help me with printing reports invoked thru command line/ URL access to print automatically to specific printers and specific trays and also is it possible to set the specific printer and tray as parameters.

Any suggestions is appreciated

Thanks A lot in advance

e,g :

http://localhost/reportserver?/testreports/employee sales&UserID='ABC'&LName=Lastname='victor'&rs:Command=Render

There are no url parameters to make the report automatically print. You can print using the ActiveX control that ships with RS 2005 or you could look into using the printer delivery sample for printing your reports.

Command Line Parameters to msiexec

I am trying to pass command line parameters to msiexec for installing
msde2000.
Line is :
"c:\windows\system32\msiexec.exe" /settings "D:\develop\servis\setup.ini" /i
"e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /L*v
"D:\develop\servis\MSDE_setup.log"
It does not accept /settings "D:\develop\servis\setup.ini" part.
Any idea?
Hi,
The /Settings is the parameter of MSDE's setup and not msiexec.
From the syntax that you have sent, it seems as you are providing /settings
as the syntax for msiexec instead of the msde's setup.
Try to run the MSDE setup using the following syntax
"e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
"D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
Below is the msde's parameter list with its description.
================================================== ==========================
==========================================
Syntax
setup [/?]
[
[ /i package_file
[ /settings ini_file ]
| [ [ ALLOWXDBCHAINING=1 ]
[ BLANKSAPWD=1 ]
[ CALLBACK=Dllname!CallbackFunctionName ]
[ COLLATION="collation_name" ]
[ DATADIR="data_folder_path" ]
[ DISABLENETWORKPROTOCOLS=n ]
[ INSTANCENAME="instance_name" ]
[ SAPWD="sa_password" ]
[ SECURITYMODE=SQL ]
[ TARGETDIR="executable_folder_path" ]
[ UPGRADE=1 ]
[ UPGRADEUSER=admin_login ]
[ UPGRADEPWD=admin_password ]
]
]
[ /L*v [filename] ]
[ /upgradesp { SQLRUN
| <MSIPath>SQLRunnn.msi }
]
[ /qn | /qb ]
[ /x package_name ]
]
Arguments
/?
Displays a syntax summary of the setup options.
Important Because setup displays more options than it accepts, use only
the options documented in this topic.
/i package_file
Specifies the name of the Windows Installer installation package file (an
.msi file) to be used to install an instance of the Microsoft SQL Server
2000 Desktop Engine (MSDE 2000). The package file specified must be one of
the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
\MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe. If
/i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
folder on the SQL Server 2000 compact disc to the folder in which Setup.exe
is located.
For SP3 or later, the preferred approach is to specify the INSTANCENAME
parameter instead of the /i option. If all of the .msi package files are
present, then Setup will dynamically select which package file to use for
the installation. If neither /i nor INSTANCENAME are specified, Setup will
dynamically select the package file and install a default instance.
Caution It is possible to overwrite an instance by mistake. You must check
for instances that are already present, including instances installed by
other vendors' software.
/settings ini_file_name
Specifies the name of an .ini file containing settings for the Setup
parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified, these
parameters should be set in the .ini file, not on the command prompt. Place
the .ini file in the folder where Setup.exe is located.
ALLOWXDBCHAINING=1
In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
behavior of the Installer and enables cross database ownership chains for
the instance. For more information about cross database chaining, see Cross
DB Ownership Chaining. You should not use this parameter unless you are
running an application that requires cross database ownership chains.
BLANKSAPWD=1
Overrides the Installer's default behavior, which is to require that you
specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
assigns a null password to the sa login
Security Note Assigning a null, blank, simple, or well-known password to
the sa login can allow unauthorized people access to your data.
CALLBACK=Dllname!CallbackFunctionName
Specifies the name of the DLL containing the Desktop Engine Windows
Installer callback function, and the name of the callback function. For
more information, see Windows Installer Callback Functions for Desktop
Engine.
COLLATION="collation_name"
Specifies the SQL Server collation that will be used as the default
collation for this instance of the Desktop Engine. For information about
collation names, see Windows Collation Name and SQL Collation Name.
DATADIR="data_folder_path"
Specifies the folder where the SQL Server system databases are built.
Assuming that the system default for program files is C:\Program Files:
The default value for default instances is: C:\Program Files\Microsoft SQL
Server\MSSQL\Data\.
The default value for named instances is C:\Program Files\Microsoft SQL
Server\MSSQL$<instance_name>\Data\, where instance_name is the name
specified in the INSTANCENAME option.
The file path for this parameter must end with a backslash (\). When
installing a default instance, setup appends mssql\data to the end of the
path specified in DATADIR. When installing a named instance, setup appends
mssql$<instance_name>\data, where instance_name is the value specified in
the INSTANCENAME option.
Setup builds two other folders at the same location as the Data folder, a
Log folder for the database engine error logs, and an Install folder
containing installation scripts.
Note Settings that contain spaces should be enclosed with quotation marks.
DISABLENETWORKPROTOCOLS=n
In SQL Server 2000 SP3 or later, specifies how the Installer configures the
network protocol support for the instance of the Desktop Engine being
installed or upgraded. n is an integer number, and should be set to either
0 or 1.
These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
Value Specified for n Upgrading Existing Instance Installing New Instance
1 Instance is configured with all server Net-Libraries disabled. Instance
is configured with all server Net-Libraries disabled.
0 The existing server Net-Library configuration is retained. Instance is
configured with default server Net-Libraries and addresses enabled.
Parameter not specified, or is any value other than 0 or 1 The existing
server Net-Library configuration is retained. Instance is configured with
all server Net-Libraries disabled.
In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared to
SP3a:
When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
either not specified or set to a value other than 0 or 1, then the instance
is installed with the default Net-Libraries and addresses enabled. In SP3a,
the Net-Libraries are disabled.
Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
the instance will still use User Datagram Protocol (UDP) port 1434. In
SP3a, the instance will not use UDP port 1434 in that configuration. For
more information, see Controlling Net-Libraries and Communications
Addresses.
INSTANCENAME="instance_name"
Specifies the name for the instance. If no instance name is specified, the
instance is installed as a default instance.
SAPWD="sa_password"
Specifies the password to be assigned to the sa login when installing a new
instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
instance of MSDE 2000, so you should ensure the sa login has a strong
password before upgrading. You should always specify a strong sa password,
even when using Windows Authentication Mode. While the SAPWD parameter is
not written to the installation log file when running Setup.exe, it is if
you install using merge modules.
SECURITYMODE=SQL
Specifies that the instance be configured in Mixed Mode, where the instance
supports both SQL Server Authentication and Windows Authentication
connections.
In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
specified, the instance will be configured in Windows Authentication Mode.
The instance will only support Windows Authentication connections, and the
Windows local administrator's group will be added to the SQL Server
sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
instance in Mixed Mode.
Security Note When possible, use Windows Authentication.
In Microsoft Windows 98 or Windows ME, the instance is always configured to
use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
these operating systems, MSDE 2000 can only support SQL Server
Authentication connections.
TARGETDIR="executable_folder_path"
Specifies the folder where the Desktop Engine executable files are to be
installed. Assuming that your system default for program files is
C:\Program Files:
The default value for default instances is: C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\.
The default value for named instances is: C:\Program Files\Microsoft SQL
Server\MSSQL$<instance_name>\Binn\ for named instances, where instance_name
is the name specified in the INSTANCENAME option.
The file path for this parameter must end with a backslash (\). When
installing a default instance, setup appends mssql\binn to the end of the
path specified in TARGETDIR. When installing a named instance, setup
appends mssql$<instance_name>\binn.
Note Settings that contain spaces should be enclosed with quotation marks.
UPGRADE=1
Specifies that Desktop Engine Setup or Windows Installer is upgrading an
instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
same fashion as a default instance of MSDE 2000, and is always upgraded to
a default instance of MSDE 2000.
UPGRADEUSER=admin_login
Specifies the login to be used when you upgrade an instance of either MSDE
1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
member of the sysadmin fixed server role. This parameter is only used when
you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
UPGRADEPWD=admin_password
Specifies the password for the login specified in UPGRADEUSER when you
upgrade Desktop Engine using SQL Server Authentication.
/L*v [filename]
Specifies that a verbose log be created. If filename is specified, the log
is stored in the file specified.
/upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
Specifies that Setup will upgrade an existing instance of MSDE 2000. For
SP3 and later, this option replaces the /p option supported by earlier
versions of Setup. Do not use the /p option with SP3 or later. When
upgrading to SP3 or later, you are no longer required to specify the .msi
file used to install the existing instance of MSDE 2000.
Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
setup utility determines which .msi file to use. When you specify SQLRUN
without specifying an INSTANCENAME, Setup will upgrade the default instance
of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
upgrade the instance you specified using the INSTANCENAME parameter.
When you specify the name of an MSDE 2000 .msi installation package file,
Setup will upgrade whichever instance on the computer was originally
installed with a merge module of the same name. For example, if you specify
SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
originally installed using SqlRun01.msi. MSIPath is the path to the folder
holding the .msi file. MSIPath defaults to Setup\.
/qn
Specifies that Setup run with no user interface.
/qb
Specifies that Setup show only the basic user interface. Only dialog boxes
displaying progress information are displayed. Other dialog boxes, such as
the dialog box that asks users whether they want to restart at the end of
the setup process, are not displayed.
If neither /qn nor /qb is specified, Setup displays all user interface
dialog boxes.
/x package_name
Specifies the name of the Windows Installer installation package file (an
.msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
Engine. You must specify the name of the same installation package file
that was used to install the instance of the Desktop Engine. Place the .msi
file in the same folder as Setup.exe.
================================================== ==========================
==========================================
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
|||In windows 98 it says : invalid command or file name
In windows 2003 it says : invalid command line parameters.
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:lXiEhehZEHA.2804@.cpmsftngxa06.phx.gbl...
> Hi,
> The /Settings is the parameter of MSDE's setup and not msiexec.
> From the syntax that you have sent, it seems as you are providing
/settings
> as the syntax for msiexec instead of the msde's setup.
> Try to run the MSDE setup using the following syntax
>
> "e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
> "D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
>
> Below is the msde's parameter list with its description.
>
================================================== ==========================
> ==========================================
> Syntax
> setup [/?]
> [
> [ /i package_file
> [ /settings ini_file ]
> | [ [ ALLOWXDBCHAINING=1 ]
> [ BLANKSAPWD=1 ]
> [ CALLBACK=Dllname!CallbackFunctionName ]
> [ COLLATION="collation_name" ]
> [ DATADIR="data_folder_path" ]
> [ DISABLENETWORKPROTOCOLS=n ]
> [ INSTANCENAME="instance_name" ]
> [ SAPWD="sa_password" ]
> [ SECURITYMODE=SQL ]
> [ TARGETDIR="executable_folder_path" ]
> [ UPGRADE=1 ]
> [ UPGRADEUSER=admin_login ]
> [ UPGRADEPWD=admin_password ]
> ]
> ]
> [ /L*v [filename] ]
> [ /upgradesp { SQLRUN
> | <MSIPath>SQLRunnn.msi }
> ]
> [ /qn | /qb ]
> [ /x package_name ]
> ]
> Arguments
> /?
> Displays a syntax summary of the setup options.
>
> Important Because setup displays more options than it accepts, use only
> the options documented in this topic.
>
> /i package_file
> Specifies the name of the Windows Installer installation package file (an
> msi file) to be used to install an instance of the Microsoft SQL ServerT
> 2000 Desktop Engine (MSDE 2000). The package file specified must be one of
> the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
> \MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe.
If
> /i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
> folder on the SQL Server 2000 compact disc to the folder in which
Setup.exe
> is located.
> For SP3 or later, the preferred approach is to specify the INSTANCENAME
> parameter instead of the /i option. If all of the .msi package files are
> present, then Setup will dynamically select which package file to use for
> the installation. If neither /i nor INSTANCENAME are specified, Setup will
> dynamically select the package file and install a default instance.
>
> Caution It is possible to overwrite an instance by mistake. You must
check
> for instances that are already present, including instances installed by
> other vendors' software.
>
> /settings ini_file_name
> Specifies the name of an .ini file containing settings for the Setup
> parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
> INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified,
these
> parameters should be set in the .ini file, not on the command prompt.
Place
> the .ini file in the folder where Setup.exe is located.
> ALLOWXDBCHAINING=1
> In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
> behavior of the Installer and enables cross database ownership chains for
> the instance. For more information about cross database chaining, see
Cross
> DB Ownership Chaining. You should not use this parameter unless you are
> running an application that requires cross database ownership chains.
> BLANKSAPWD=1
> Overrides the Installer's default behavior, which is to require that you
> specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
> assigns a null password to the sa login
>
> Security Note Assigning a null, blank, simple, or well-known password to
> the sa login can allow unauthorized people access to your data.
>
> CALLBACK=Dllname!CallbackFunctionName
> Specifies the name of the DLL containing the Desktop Engine Windows
> Installer callback function, and the name of the callback function. For
> more information, see Windows Installer Callback Functions for Desktop
> Engine.
> COLLATION="collation_name"
> Specifies the SQL Server collation that will be used as the default
> collation for this instance of the Desktop Engine. For information about
> collation names, see Windows Collation Name and SQL Collation Name.
> DATADIR="data_folder_path"
> Specifies the folder where the SQL Server system databases are built.
> Assuming that the system default for program files is C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data\.
>
> The default value for named instances is C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Data\, where instance_name is the name
> specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\data to the end of the
> path specified in DATADIR. When installing a named instance, setup appends
> mssql$<instance_name>\data, where instance_name is the value specified in
> the INSTANCENAME option.
> Setup builds two other folders at the same location as the Data folder, a
> Log folder for the database engine error logs, and an Install folder
> containing installation scripts.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> DISABLENETWORKPROTOCOLS=n
> In SQL Server 2000 SP3 or later, specifies how the Installer configures
the
> network protocol support for the instance of the Desktop Engine being
> installed or upgraded. n is an integer number, and should be set to either
> 0 or 1.
> These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
> Value Specified for n Upgrading Existing Instance Installing New Instance
> 1 Instance is configured with all server Net-Libraries disabled. Instance
> is configured with all server Net-Libraries disabled.
> 0 The existing server Net-Library configuration is retained. Instance is
> configured with default server Net-Libraries and addresses enabled.
> Parameter not specified, or is any value other than 0 or 1 The existing
> server Net-Library configuration is retained. Instance is configured with
> all server Net-Libraries disabled.
>
> In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared
to
> SP3a:
> When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
> either not specified or set to a value other than 0 or 1, then the
instance
> is installed with the default Net-Libraries and addresses enabled. In
SP3a,
> the Net-Libraries are disabled.
>
> Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
> the instance will still use User Datagram Protocol (UDP) port 1434. In
> SP3a, the instance will not use UDP port 1434 in that configuration. For
> more information, see Controlling Net-Libraries and Communications
> Addresses.
> INSTANCENAME="instance_name"
> Specifies the name for the instance. If no instance name is specified, the
> instance is installed as a default instance.
> SAPWD="sa_password"
> Specifies the password to be assigned to the sa login when installing a
new
> instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
> instance of MSDE 2000, so you should ensure the sa login has a strong
> password before upgrading. You should always specify a strong sa password,
> even when using Windows Authentication Mode. While the SAPWD parameter is
> not written to the installation log file when running Setup.exe, it is if
> you install using merge modules.
> SECURITYMODE=SQL
> Specifies that the instance be configured in Mixed Mode, where the
instance
> supports both SQL Server Authentication and Windows Authentication
> connections.
> In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
> specified, the instance will be configured in Windows Authentication Mode.
> The instance will only support Windows Authentication connections, and the
> Windows local administrator's group will be added to the SQL Server
> sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
> instance in Mixed Mode.
>
> Security Note When possible, use Windows Authentication.
>
> In Microsoft Windows 98 or Windows ME, the instance is always configured
to
> use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
> these operating systems, MSDE 2000 can only support SQL Server
> Authentication connections.
> TARGETDIR="executable_folder_path"
> Specifies the folder where the Desktop Engine executable files are to be
> installed. Assuming that your system default for program files is
> C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\.
>
> The default value for named instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Binn\ for named instances, where
instance_name
> is the name specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\binn to the end of the
> path specified in TARGETDIR. When installing a named instance, setup
> appends mssql$<instance_name>\binn.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> UPGRADE=1
> Specifies that Desktop Engine Setup or Windows Installer is upgrading an
> instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
> Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
> same fashion as a default instance of MSDE 2000, and is always upgraded to
> a default instance of MSDE 2000.
> UPGRADEUSER=admin_login
> Specifies the login to be used when you upgrade an instance of either MSDE
> 1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
> member of the sysadmin fixed server role. This parameter is only used when
> you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
> UPGRADEPWD=admin_password
> Specifies the password for the login specified in UPGRADEUSER when you
> upgrade Desktop Engine using SQL Server Authentication.
> /L*v [filename]
> Specifies that a verbose log be created. If filename is specified, the log
> is stored in the file specified.
> /upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
> Specifies that Setup will upgrade an existing instance of MSDE 2000. For
> SP3 and later, this option replaces the /p option supported by earlier
> versions of Setup. Do not use the /p option with SP3 or later. When
> upgrading to SP3 or later, you are no longer required to specify the .msi
> file used to install the existing instance of MSDE 2000.
> Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
> setup utility determines which .msi file to use. When you specify SQLRUN
> without specifying an INSTANCENAME, Setup will upgrade the default
instance
> of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
> upgrade the instance you specified using the INSTANCENAME parameter.
> When you specify the name of an MSDE 2000 .msi installation package file,
> Setup will upgrade whichever instance on the computer was originally
> installed with a merge module of the same name. For example, if you
specify
> SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
> originally installed using SqlRun01.msi. MSIPath is the path to the folder
> holding the .msi file. MSIPath defaults to Setup\.
> /qn
> Specifies that Setup run with no user interface.
> /qb
> Specifies that Setup show only the basic user interface. Only dialog boxes
> displaying progress information are displayed. Other dialog boxes, such as
> the dialog box that asks users whether they want to restart at the end of
> the setup process, are not displayed.
> If neither /qn nor /qb is specified, Setup displays all user interface
> dialog boxes.
> /x package_name
> Specifies the name of the Windows Installer installation package file (an
> msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
> Engine. You must specify the name of the same installation package file
> that was used to install the instance of the Desktop Engine. Place the
..msi
> file in the same folder as Setup.exe.
>
>
================================================== ==========================
> ==========================================
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||"F:\mcd\msde2000\setup.exe" /settings "D:\develop\Servis\setup.ini" /i
"F:\mcd\msde2000\SETUP\SQLRUN01.MSI" /L*v "D:\develop\Servis\MSDE_setup.log"
/wait
But above line reallt works fine.
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:lXiEhehZEHA.2804@.cpmsftngxa06.phx.gbl...
> Hi,
> The /Settings is the parameter of MSDE's setup and not msiexec.
> From the syntax that you have sent, it seems as you are providing
/settings
> as the syntax for msiexec instead of the msde's setup.
> Try to run the MSDE setup using the following syntax
>
> "e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
> "D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
>
> Below is the msde's parameter list with its description.
>
================================================== ==========================
> ==========================================
> Syntax
> setup [/?]
> [
> [ /i package_file
> [ /settings ini_file ]
> | [ [ ALLOWXDBCHAINING=1 ]
> [ BLANKSAPWD=1 ]
> [ CALLBACK=Dllname!CallbackFunctionName ]
> [ COLLATION="collation_name" ]
> [ DATADIR="data_folder_path" ]
> [ DISABLENETWORKPROTOCOLS=n ]
> [ INSTANCENAME="instance_name" ]
> [ SAPWD="sa_password" ]
> [ SECURITYMODE=SQL ]
> [ TARGETDIR="executable_folder_path" ]
> [ UPGRADE=1 ]
> [ UPGRADEUSER=admin_login ]
> [ UPGRADEPWD=admin_password ]
> ]
> ]
> [ /L*v [filename] ]
> [ /upgradesp { SQLRUN
> | <MSIPath>SQLRunnn.msi }
> ]
> [ /qn | /qb ]
> [ /x package_name ]
> ]
> Arguments
> /?
> Displays a syntax summary of the setup options.
>
> Important Because setup displays more options than it accepts, use only
> the options documented in this topic.
>
> /i package_file
> Specifies the name of the Windows Installer installation package file (an
> msi file) to be used to install an instance of the Microsoft SQL ServerT
> 2000 Desktop Engine (MSDE 2000). The package file specified must be one of
> the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
> \MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe.
If
> /i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
> folder on the SQL Server 2000 compact disc to the folder in which
Setup.exe
> is located.
> For SP3 or later, the preferred approach is to specify the INSTANCENAME
> parameter instead of the /i option. If all of the .msi package files are
> present, then Setup will dynamically select which package file to use for
> the installation. If neither /i nor INSTANCENAME are specified, Setup will
> dynamically select the package file and install a default instance.
>
> Caution It is possible to overwrite an instance by mistake. You must
check
> for instances that are already present, including instances installed by
> other vendors' software.
>
> /settings ini_file_name
> Specifies the name of an .ini file containing settings for the Setup
> parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
> INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified,
these
> parameters should be set in the .ini file, not on the command prompt.
Place
> the .ini file in the folder where Setup.exe is located.
> ALLOWXDBCHAINING=1
> In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
> behavior of the Installer and enables cross database ownership chains for
> the instance. For more information about cross database chaining, see
Cross
> DB Ownership Chaining. You should not use this parameter unless you are
> running an application that requires cross database ownership chains.
> BLANKSAPWD=1
> Overrides the Installer's default behavior, which is to require that you
> specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
> assigns a null password to the sa login
>
> Security Note Assigning a null, blank, simple, or well-known password to
> the sa login can allow unauthorized people access to your data.
>
> CALLBACK=Dllname!CallbackFunctionName
> Specifies the name of the DLL containing the Desktop Engine Windows
> Installer callback function, and the name of the callback function. For
> more information, see Windows Installer Callback Functions for Desktop
> Engine.
> COLLATION="collation_name"
> Specifies the SQL Server collation that will be used as the default
> collation for this instance of the Desktop Engine. For information about
> collation names, see Windows Collation Name and SQL Collation Name.
> DATADIR="data_folder_path"
> Specifies the folder where the SQL Server system databases are built.
> Assuming that the system default for program files is C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data\.
>
> The default value for named instances is C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Data\, where instance_name is the name
> specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\data to the end of the
> path specified in DATADIR. When installing a named instance, setup appends
> mssql$<instance_name>\data, where instance_name is the value specified in
> the INSTANCENAME option.
> Setup builds two other folders at the same location as the Data folder, a
> Log folder for the database engine error logs, and an Install folder
> containing installation scripts.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> DISABLENETWORKPROTOCOLS=n
> In SQL Server 2000 SP3 or later, specifies how the Installer configures
the
> network protocol support for the instance of the Desktop Engine being
> installed or upgraded. n is an integer number, and should be set to either
> 0 or 1.
> These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
> Value Specified for n Upgrading Existing Instance Installing New Instance
> 1 Instance is configured with all server Net-Libraries disabled. Instance
> is configured with all server Net-Libraries disabled.
> 0 The existing server Net-Library configuration is retained. Instance is
> configured with default server Net-Libraries and addresses enabled.
> Parameter not specified, or is any value other than 0 or 1 The existing
> server Net-Library configuration is retained. Instance is configured with
> all server Net-Libraries disabled.
>
> In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared
to
> SP3a:
> When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
> either not specified or set to a value other than 0 or 1, then the
instance
> is installed with the default Net-Libraries and addresses enabled. In
SP3a,
> the Net-Libraries are disabled.
>
> Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
> the instance will still use User Datagram Protocol (UDP) port 1434. In
> SP3a, the instance will not use UDP port 1434 in that configuration. For
> more information, see Controlling Net-Libraries and Communications
> Addresses.
> INSTANCENAME="instance_name"
> Specifies the name for the instance. If no instance name is specified, the
> instance is installed as a default instance.
> SAPWD="sa_password"
> Specifies the password to be assigned to the sa login when installing a
new
> instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
> instance of MSDE 2000, so you should ensure the sa login has a strong
> password before upgrading. You should always specify a strong sa password,
> even when using Windows Authentication Mode. While the SAPWD parameter is
> not written to the installation log file when running Setup.exe, it is if
> you install using merge modules.
> SECURITYMODE=SQL
> Specifies that the instance be configured in Mixed Mode, where the
instance
> supports both SQL Server Authentication and Windows Authentication
> connections.
> In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
> specified, the instance will be configured in Windows Authentication Mode.
> The instance will only support Windows Authentication connections, and the
> Windows local administrator's group will be added to the SQL Server
> sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
> instance in Mixed Mode.
>
> Security Note When possible, use Windows Authentication.
>
> In Microsoft Windows 98 or Windows ME, the instance is always configured
to
> use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
> these operating systems, MSDE 2000 can only support SQL Server
> Authentication connections.
> TARGETDIR="executable_folder_path"
> Specifies the folder where the Desktop Engine executable files are to be
> installed. Assuming that your system default for program files is
> C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\.
>
> The default value for named instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Binn\ for named instances, where
instance_name
> is the name specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\binn to the end of the
> path specified in TARGETDIR. When installing a named instance, setup
> appends mssql$<instance_name>\binn.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> UPGRADE=1
> Specifies that Desktop Engine Setup or Windows Installer is upgrading an
> instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
> Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
> same fashion as a default instance of MSDE 2000, and is always upgraded to
> a default instance of MSDE 2000.
> UPGRADEUSER=admin_login
> Specifies the login to be used when you upgrade an instance of either MSDE
> 1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
> member of the sysadmin fixed server role. This parameter is only used when
> you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
> UPGRADEPWD=admin_password
> Specifies the password for the login specified in UPGRADEUSER when you
> upgrade Desktop Engine using SQL Server Authentication.
> /L*v [filename]
> Specifies that a verbose log be created. If filename is specified, the log
> is stored in the file specified.
> /upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
> Specifies that Setup will upgrade an existing instance of MSDE 2000. For
> SP3 and later, this option replaces the /p option supported by earlier
> versions of Setup. Do not use the /p option with SP3 or later. When
> upgrading to SP3 or later, you are no longer required to specify the .msi
> file used to install the existing instance of MSDE 2000.
> Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
> setup utility determines which .msi file to use. When you specify SQLRUN
> without specifying an INSTANCENAME, Setup will upgrade the default
instance
> of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
> upgrade the instance you specified using the INSTANCENAME parameter.
> When you specify the name of an MSDE 2000 .msi installation package file,

> Setup will upgrade whichever instance on the computer was originally
> installed with a merge module of the same name. For example, if you
specify
> SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
> originally installed using SqlRun01.msi. MSIPath is the path to the folder
> holding the .msi file. MSIPath defaults to Setup\.
> /qn
> Specifies that Setup run with no user interface.
> /qb
> Specifies that Setup show only the basic user interface. Only dialog boxes
> displaying progress information are displayed. Other dialog boxes, such as
> the dialog box that asks users whether they want to restart at the end of
> the setup process, are not displayed.
> If neither /qn nor /qb is specified, Setup displays all user interface
> dialog boxes.
> /x package_name
> Specifies the name of the Windows Installer installation package file (an
> msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
> Engine. You must specify the name of the same installation package file
> that was used to install the instance of the Desktop Engine. Place the
..msi
> file in the same folder as Setup.exe.
>
>
================================================== ==========================
> ==========================================
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||Hi,
"F:\mcd\msde2000\setup.exe" /settings "D:\develop\Servis\setup.ini" /i
"F:\mcd\msde2000\SETUP\SQLRUN01.MSI" /L*v "D:\develop\Servis\MSDE_setup.log"
/wait
These lines work, because you are providing parameters to the setup and not
to the MSIEXEC file.
MSIEXEC and setup.exe are two independent softwares.
The /Settings is a parameter of Setup.exe
For parameter information on MSIEXEC please visit,
http://msdn.microsoft.com/library/de...us/msi/setup/c
ommand_line_options.asp
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

command line parameters are invalid in SQL server Agent

Hi

Microsoft confirmed that the error message "The command line parameters are invalid" issue mentioned above is a bug and has been resolved in the next "drop" of SQL Server 2005.

has this error been fixed by microsoft. Cos i still get this error!!!!!!!!!

I am also trying to run the package from command line and when i click on execute the package it runs half way and hangs. What could be the problem?.

But when i run it from my Studio and stored package it works fine!!!

Thanks,

Jas

Perhaps the command line is incorrect. You do appear to have some keys that stick on your keyboard, which could lead to typing invalid commands.

Seriously, we need some more information to help you. What command line parameters are you trying to set?

Your second issue probably needs another thread. We would need to know what the package does - what tasks execute and what it is doing when it hangs.

Donald

|||

I have created a job to execute a SSIS package located in the SSIS Package Store. When starting the job I receive an error. The history log reports:

Message
Executed as user: semaster\vagnel. The command line parameters are invalid. The step failed.

I did not write this command line it is auto generated through wizard.

This is the command line:

/SQL "\ArchiveMain" /SERVER "SE413695\AASQL2005" /WARNASERROR /MAXCONCURRENT " -1 " /CHECKPOINTING OFF

Thanks,

Jasmine

command line parameters are invalid

I have a package that let me to import data from a excel book to a Sql server data base. When I try to run this package like a step into a SQL server Job it show me the next error.

"The command line parameters are invalid. The step failed."

the "command line" looks like this

/FILE "C:\Project\Package.dtsx" /CONNECTION ConexionExcel;"Provider=Microsoft.Jet.OLEDB.4.0;Da ta Source=;Extended Properties=""EXCEL 8.0;HDR=YES"";" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

and in my excel conexion is:

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=;Extended Properties="EXCEL 8.0;HDR=YES";

When i run the "Command Line" in the "Command window" the error is more expecific

"EXCEL 8.0;HDR=YES;" is not valid

So I chanded the "Command Line" in order to run it in de command window(look the double quote in the excel properties)

/FILE "C:\Project\Package.dtsx" /CONNECTION ConexionExcel;"Provider=Microsoft.Jet.OLEDB.4.0;Da ta Source=;Extended Properties="EXCEL 8.0;HDR=YES";" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

then the package RUN, but when i tried to do the same thing in the

sql wizzard, it just dont work and it lost the threat from de package and the errors says this time:

Couldn't find the package

Some one who knows the answer or has any idea to helpme please?

thanks

Use in the Import/Export wizard in SQL.

Adamus

|||According to current Books Online, the double quote is the correct method to escape the quotes inside the parameter. Are you running SP1? I believe they made some changes to the parsing of command lines in SP1, so perhaps that may help.|||

I have a windows 2003 server and the SP1 is only for windows vista, I have installed this version but, i don't know if it has some thing to do with that

|||

I have found the soluction,

I you have seen the command line, the excel connection doesn't have a Data Source because it change in a bucle, I modified connection string parameter in the package in oder to recive a variable with all the connection string, then when i programming my step in the job i don't need to especified the excel connection string.

Thanks Cesar for the aswer

Command line parameter passing

Command line parameter passing
Does anyone know if it is possible to pass a parameter to a script run
from the isql (Query Analyzer).
I have a large .SQL file that does a setup of a database and I would
like to pass it a parameter that is
A name of another database to create some views to.
If its not possible from the command line, Is it possible to set an
environment variable and check that
variable inside the .sql script.
Any help would be appreciated.You can use the OSQL command-line utility and pass a parameter as part of a
the query / command string (-q switch).
Lookup the OSQL syntax in Books Online.
David Portas
SQL Server MVP
--|||Thanks for the response.
I have been trying something like this.
isql -H%GSHost% -S%GSServer% -d%GSDB% -U%GSUser% -P%GSPassWord% -n -q
"declare @.Odb varchar(40);set @.Odb=' test ';print @.Odb" -i GsViews.sql
in the GSViews.sql I do
print @.Odb
So when I do this the first print (from the -q) works but the one in the
GSViews.sql (run by the -i) errors out stating that @.Odb does not exist.
No GSViews.sql is quite long and it needs to know what other database
name. Any idea?
David Portas wrote:

> You can use the OSQL command-line utility and pass a parameter as part of
a
> the query / command string (-q switch).
> Lookup the OSQL syntax in Books Online.
>