Package Runs From Command Prompt, But Wouldn't From The Agent

Sep 20, 2007

A strange thing is happening to us: we create a bat file that executes an SSIS package with multiple connection managers and tasks.

When calling the bat file from command prompt €“ the package runs just fine!

When calling the same bat file from SQL Server Agent (that runs under the same NT account as SSIS, and all other SQL services, and belongs to local Adminstrators), the package fails half way through with connection failed issue.

Plus it gives us something like this: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER

Has anyone ever experienced this issue, do you have any possible solutions?

Thank you!
Anastasia

View 4 Replies


ADVERTISEMENT

SSIS Package That Runs Fine Through Command Prompt, XML Error When Run Through SQL Server Agent Job CmdExec

Aug 17, 2006

I have an SSIS package that runs fine through command pormpt although when I try to run it from a SQL Servr Agent Job CmdExec step it bombs out.  Please help this has me stumped...the SSIS package uses an XML connection string so certain key settings such as connection strings and email info can be changed easily.  Currently this is all on the same machine.  I have not moved it beyond where I am developing.

 

On the command line I am using the following command...

dtexec /F "S:connectionscontacts.dtsConfig" /DE "password"

 

Below is the output log...

 

Microsoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Started:  6:59:40 PM
Progress: 2006-08-16 18:59:41.29
   Source: Data Flow Task
   Validating: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.29
   Source: Data Flow Task
   Validating: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.71
   Source: Data Flow Task
   Validating: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.73
   Source: Data Flow Task
   Validating: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.77
   Source: Data Flow Task
   Validating: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.77
   Source: Data Flow Task
   Validating: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.77
   Source: Data Flow Task
   Validating: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.77
   Source: Data Flow Task
   Validating: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.79
   Source: Data Flow Task
   Prepare for Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.79
   Source: Data Flow Task
   Prepare for Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.79
   Source: Data Flow Task
   Prepare for Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.79
   Source: Data Flow Task
   Prepare for Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.81
   Source: Data Flow Task
   Pre-Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.84
   Source: Data Flow Task
   Pre-Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.90
   Source: Data Flow Task
   Pre-Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.90
   Source: Data Flow Task
   Pre-Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.92
   Source: Data Flow Task
   Post Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.92
   Source: Data Flow Task
   Post Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.92
   Source: Data Flow Task
   Post Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.92
   Source: Data Flow Task
   Post Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.92
   Source: Data Flow Task
   Cleanup: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.93
   Source: Data Flow Task
   Cleanup: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.93
   Source: Data Flow Task
   Cleanup: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.93
   Source: Data Flow Task
   Cleanup: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.95
   Source: Send Mail Task
   The SendMail task is initiated.: 0% complete
End Progress
Progress: 2006-08-16 18:59:42.09
   Source: Send Mail Task
   The SendMail task is completed.: 100% complete
End Progress
DTExec: The package execution returned DTSER_SUCCESS (0).
Started:  6:59:40 PM
Finished: 6:59:42 PM
Elapsed:  1.984 seconds

 

 

When I try to use the same command within SQL Server Agent Job using a CmdExec step I get the following error...

 

Description: The package is attempting to configure from the XML file "S:connectionscontacts.dtsConfig".  End Info  Warning: 2006-08-16 18:40:03.15     Code: 0x80012012     Source: contactsPackage Description: The configuration file name "S:connectionscontacts.dtsConfig" is not valid. Check the configuration file name.  End Warning  Warning: 2006-08-16 18:40:03.15     Code: 0x80012059     Source: contactsPackage Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed.  End Warning  Info: 2006-08-16 18:40:03.20  ...  Process Exit Code 1.  The step failed.

 

Thanks in advance for any help!!!

View 2 Replies View Related

Sql Srvr 6.5 Only Runs From Command Prompt

Oct 11, 1999

We have a development server that will only run SQL Server from a DOS command prompt. Each time I reboot the server the services don't autostart, and I am unable to start them manually using Service Manager. Does anyone know what I can do to fix this problem?
Thanks

View 1 Replies View Related

Using The Command Prompt Via SQL Server Agent

Jun 4, 2007

I need to verify a csv file exists before I call a stored procedure to complete a bulk insert. The first step in the SP will be to verify the file exists (that particular "Job" step did not fail). I have only one step in the job that I have set the type as "Operating System (CmdExec)" and the Command is "Dir C:NAFCDMDataShipmentsCooperShipments.csv". When I execute the job manually to verify the proper operation I receive the error listed below. I know the path and file name are correct as I originally typed in the UNC, when it failed I copied it from the Address bar. I attempted to move the file to the root location without success. I attempted to use another file. I have attempted to rename the file. The DBAs will not allow me to use the SP_cmdshell stored procedure (that was my first thought).

I added 'Everyone' with Full Access to the root folder and propagated these permissions to all containing folders. This again did not allow the job to run. I changed the statment to "REN C:NAFCDMShipmentsShipment.csv Shipment1.csv". I continue to get the same error. Can someone Please point me in a direction to fix this problem?



"The process could not be created for step 1 of job 0x71D51027F920A140A2913234DB7FF509

(reason: The system cannot find the file specified). The step failed.

The job failed. The Job was invoked by User sa. The last step to run was step 1 (Verify the File's Existance)."

View 1 Replies View Related

Unable To Run Command Prompt SQL Utility From SQL Agent

Mar 20, 2003

I am unable to execute DTS packages,ISQLs when scheduled from SQL Server Agent . It dispalys a Dr.Watson Access Voilation message on the box .The result of the job is "failed as the step did not return any result ".

1)The utilities run fine when run from clients from other computers .


2)They fail again when run thru the command prompt of the box .

3)They suceed when run via the xp_cmdshell .

Can anybody help me out ?

Thanks,
Venkat

View 7 Replies View Related

SQL Server Agent Accessing The Command Prompt

Jun 4, 2007

I need to verify a csv file exists before I call a stored procedure to complete a bulk insert. The first step in the SP will be to verify the file exists (that particular "Job" step did not fail). I have only one step in the job that I have set the type as "Operating System (CmdExec)" and the Command is "Dir C:NAFCDMDataShipmentsCooperShipments.csv". When I execute the job manually to verify the proper operation I receive the error listed below. I know the path and file name are correct as I originally typed in the UNC, when it failed I copied it from the Address bar. I attempted to move the file to the root location without success. I attempted to use another file. I have attempted to rename the file. The DBAs will not allow me to use the SP_cmdshell stored procedure (that was my first thought).

I added 'Everyone' with Full Access to the root folder and propagated these permissions to all containing folders. This again did not allow the job to run. I changed the statment to "REN C:NAFCDMShipmentsShipment.csv Shipment1.csv". I continue to get the same error. Can someone Please point me in a direction to fix this problem?



"The process could not be created for step 1 of job 0x71D51027F920A140A2913234DB7FF509

(reason: The system cannot find the file specified). The step failed.

The job failed. The Job was invoked by User sa. The last step to run was step 1 (Verify the File's Existance)."

View 3 Replies View Related

Calling SSIS Package Through Command Prompt

Feb 24, 2008

All, I am developing the data mart refresh task in SSIS. I wanted to call the package in command prompt. I need help. Can any one give any tips on it. Thanks and appricate in advance.

Regards
Govind

View 2 Replies View Related

Integration Services :: Execute SSIS Package From Command Prompt

May 28, 2015

How to execute ssis package from command prompt and also pass configuration file to it and set logging to ssis log provider for sql server. Writing all those options with cmd.

View 3 Replies View Related

SSIS Package Runs OK Manually But Not From SQL Server Agent...Permissions?

Dec 19, 2007

I have a problem where I have an SSIS package (SQL Server 2005) that won't run properly from SQL Server Agent, but it runs fine when kicked off manually from Integration Services -> Run Package or when run in debug from Visual Studio.

The first step in the package checks for the existance of a file via a script task. The script looks like this...





Code Block
Public Sub Main()

Dim TaskResult As Integer
Dim ImportFile As String = CStr(Dts.Variables("BaseDirectory").Value) + CStr(Dts.Variables("ImportDirectory").Value) + CStr(Dts.Variables("ImportFile").Value)

If Dir(ImportFile) = "" Then
Dts.TaskResult = Dts.Results.Failure
Else
Dts.TaskResult = Dts.Results.Success
End If

Return

End Sub






This script runs fine and the file is seen as expected when I run the package manually. But as a step in a SQL Server Agent job, it doesn't see the file.

The SQL Server Agent service is set to start up / log on as a Local System Account. I've also tried setting up a credential / proxy (using an account that I know can see and even move / rename the file) to run the job as but that didn't seem to help.

The package is being run from SQL Server (stored in MSDB) and is set to rely on SQL Server for sensitive information, so I don't think that's an issue; other packages are set up like this in terms of sensitive data and run fine.

Any ideas why my script can't "see" the file I'm looking at when it's kicked off by SQL Server agent? I've looked and looked...I can't seem to figure this out. I would really appreciate any help you might be able to offer up.

View 12 Replies View Related

Package Runs In BIDS, Manually In Mgmt. Studio, But Not Via Agent. Why???

Aug 2, 2007

All:
As the subject suggests I am encountering an error while running a package through an agent. Unfortunately the error does not provide much information for me to diagnose the problem, and hence the post.

I have pasted the error below and appreciate help from anyone.

Thank you,



Message
Executed as user: EPSILONSYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:16:31 AM Error: 2007-08-02 10:16:32.25 Code: 0xC002F304 Source: File System Task File System Task Description: An error occurred with the following error message: "Could not find a part of the path 'P:FinanceItems Sold Below CostItems Sold Below Cost_2007-08-01.csv'.". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:16:31 AM Finished: 10:16:32 AM Elapsed: 1.047 seconds. The package execution failed. The step failed.

View 9 Replies View Related

BCP Utility & Command Prompt

Dec 7, 2000

Can anyone tell me how to enable bcp utility. Because anytime I try to run BCP I get the following error messages: (BCP not enable). Also how can I get to SQL Server command prompt? I look forward to hearing from anyone.

View 2 Replies View Related

Running A DTS Job From Command Prompt

Oct 17, 2000

Sorry for the new thread.
How to run a DTS job from command prompt? Any help is appreciated!
Thanks.

View 1 Replies View Related

Start Job From The Command Prompt?

Feb 23, 2006

I have a Microsoft SQL server that is setup, and inside it is a job. Inside the job is a bunch of lines of transact sql statements.

I would like to be able to start the job from the command prompt. Moreover, I do not want to have to create new files or modify anything that is existing. I just want to be able to have it set up so that a new user who installs the server and all of the job on their machine fresh, can just punch in the command to run the job.

I know I can copy the transact sql statements from the job, and run them through the command prompt, but that would be a poor way to do it, because if the statements in the job were ever modified, with this task being automated, the command prompt statements would be out of date.

So I just need a way to start the existing job from the command prompt. Is this possible? Maybe with OSQL?

View 4 Replies View Related

Sql Install From Command Prompt

Jun 18, 2008

Please let me know how to install sql server by using command prompt.

View 4 Replies View Related

BCP Problem Using Command Prompt

Mar 26, 2008

I am have trouble configuring developer edition when trying to run a Bulk Copy through Command Prompt. I have configured remote connections within the surface area configuration and have created a firewall exception

I enter and run

bcp FileImportDB..Exam in "c:FileImportPracticeExamImportFile.txt" -T -c

then i get the following error message

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:UsersDineen>bcp FileImportDB.Exam in "c:FileImportPracticeExamImportFile.t
xt" -T -c
SQLState = 08001, NativeError = 2
Error = [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].
SQLState = HYT00, NativeError = 0
Error = [Microsoft][SQL Native Client]Login timeout expired
SQLState = 08001, NativeError = 2
Error = [Microsoft][SQL Native Client]An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this failure may
be caused by the fact that under the default settings SQL Server does not allow remote connections.

I am running developer edition on vista and Service pack 2, iam connecting to my instance with no problem.

Can someone please help

Kind regards

Rob

View 6 Replies View Related

Running SQL Scripts From Command Prompt

Jul 25, 2006

I have a requirment, when a user logs in to the pc, I want to run some SQL scripts which is been saved as a stored procedure on another pc. Could this be possible. I know in oracle you could do it using SQLLDR. Is there any way to do it in SQL?
Please advice. Any help is greatly appreciated.

View 3 Replies View Related

Backing Up Database From Command Prompt

Sep 13, 2000

Is there a way by which we can execute the backing up of database from the command prompt......

Suppose i need to do the below task. I can write a stored procedure and schedule it. But the situation demands to run from the command prompt. Is there a way out.


-- Create the backup device for the full MyNwind backup.

USE master

EXEC sp_addumpdevice 'disk', 'MyNwind_2', 'c:mssql7ackupMyNwind_2.dat'

-- Back up the full MyNwind database.

BACKUP DATABASE MyNwind TO MyNwind_2


-Rajesh

View 2 Replies View Related

Running Sp From The Command Prompt (of Another Server)

Jan 23, 2001

I have created linked servers and successfully run the following stored procedure.

exec [db-2001server].sales..sp_test

Can anyone give me the exact syntax for running the same from command promt(without using the query analyzer).I am new to isql/osql.So,please help me with the syntax.
Thanks!!

View 1 Replies View Related

How To Import Database In Command Prompt?

Jan 7, 2001

How to import database in command prompt?

View 1 Replies View Related

Problem In Using Sqlmaint In Command Prompt

Feb 13, 2004

Hi,

I try to backup DB (DatabaseA) in ServerA using sqlmaint utility in command prompt.

The sqlmaint.exe does reside in ..MssqlBinn Folder.

Below is the command i used (MS-DOS):
..Binn>sqlmaint -S ServerA -U "sa" -P "########" -D DatabaseA
-BkUpDB C:Temp -HtmlRpt BackupRpt.html

When I execute the command, it only shows a list of the commands as if I execute -? command. There's NO any other messages that indicate the backup command is being executed.

When I check in the C:Temp folder, there's no BackupRpt.html file.

Anyone got any idea?

Thanks.

View 5 Replies View Related

Command Prompt Output Capture?

Jun 25, 2014

How can i get the output (like 1 rows(s) inserted)in a file from an input file through sql command prompt.

View 1 Replies View Related

Execute Sql Commands Through Command Prompt

Nov 15, 2007

Hi,

I wanted to know if there is a way to execute sql commands on the operating system's command line. If it is possible, then how do we do it ? For example to execute a SELECT * from Table statement what are we supposed to do ?

Thanks
S

View 2 Replies View Related

Help! SQLEXPRESS Command Prompt Installation!

Aug 8, 2007



i have a problem installing SQLEXPRESS via command prompt... the installation is successful but the 'sa' account could not login to the server.. here's the command in my batch file.





Code SnippetStart /wait <exe> /qb INSTANCENAME=MYINSTANCE ADDLOCAL=ALL *AUTOSTART=1 RSCONFIGURATION=DEFAULT SECURITYMODE=SQL SAPWD=sapwd SQLCOLLATION=Latin1_General_BIN requiresmsiengine=1




and one more thing, i need to run the report server automatically.. thanks!

View 2 Replies View Related

MSDE Installation Stops In Command Prompt

Aug 14, 2005

Hi,I am trying to install MSDE from a CD. At the beginning I cunpack all files at C:sql2ksp3. Then in in Command promptI enter          C:sql2ksp3MSDE> Setup SAPWD=Hello SecurityMode=SQL The problem is that nothing happens after that. When I press enter another line appears             C:sql2ksp3MSDE>but that's about it.The installation does not continue. Does anybody know how to "push" it a bit so it will continue?Thanks

View 1 Replies View Related

Triggering SSRS Report From Command Prompt

Dec 17, 2007



Hi,

We have requirement where we need to run the SSRS report from Command Prompt. We are using Control + M, which is a scheduler runs only from DOS prompt.

Can anyone help us to know the procedure of doing this.


Thanks
Karthik

View 1 Replies View Related

Installing SQL Express And Attaching A Mdf Db From The Command Prompt

Mar 21, 2007

Hi,

I need to install a customed SQL server express instance on the client's computer by using the Command prompt installation. I've already defined the security settings and everything i need but i was wondering if is possible to attach a mdf database during the installation. Perhaps there is a paramenter i can include in the in the ini file.

Thank you

View 6 Replies View Related

Login To SQL Server Express Using Command Prompt

Jun 30, 2006

How can I login to SQL Server Express instance(localhostSqlExpress) using command prompt so that I can query database. Is there any alternative GUI tool for SQL Server Express Manager? (I think Microsoft has discontinued SQL Server Express Manager). I prefer using Command Prompt. I am using WindowsXP Professional.

View 8 Replies View Related

Job Agent - Runs Without Errors, But Against Test DB

Mar 26, 2008

I've got a very simple package that truncates some rows from a table. The packages utilizes configurations as described in a post I made on this forum yesterday http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3062343&SiteID=1.

When the package is deployed and installed on the prod server, it runs successfully from the Execute Package Utility, utilizing the configurations as expected, removing the rows from the target table.

When the package is run from the SQL Agent on prod, it completes successfully without errors, but the rows in the prod table remain. On the "Data Source" tab in the job, the correct connection string shows pointing at the prod database (picked up from a config file on the prod server).

Curiously, the job appears to run the truncate against the test db table - I tested this by putting rows in the target tables on both test and prod. When the package is run from SQL Agent, the test rows are removed. When run from the Execute Package Utility on prod, the prod rows are removed. Huh?

Again, the Data Source tab in the Job on prod shows the prod db connection string and the package removes the rows correctly from the prod table when run from the Execute Package Utility on prod.

Does anyone have any thoughts on this behavior when using the Job Agent to execute a package?

Thanks!

Jamie Pick

View 12 Replies View Related

Several Different Errors When Creating And Running SSIS Package. Package Runs Successfuly Sometimes.

May 2, 2008

Hi All,



I am in the process of moving from a 32-bit SQL Server 2005 Enterprise (9.0.3054) to a 64-bit SQL Server 2005 Enterprise (9.0.3054 with 4 CPUs and 8GB of memory on Win 2003 SP2) and the process has been very frustrating to say the least. I am having a problem with packages that I created on my 64-bit SQL Server. I am importing a few tables from the 32-SQL Server into the 64-bit SQL Server using the Task --> Import to create the package.



Sometimes when I am creating a package I get the following error in a message box:



SQL Server Import and Export Wizard

The SSIS Runtime object could not be created. Verify that DTS.dll is available and registered. The wizard cannot continue and it will terminate.

Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Windows.Forms)





Other times when I run a package that has run successfully before I get the following error:



Faulting application dtexecui.exe, version 9.0.3042.0, stamp 45cd726d, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x025d23f0.





Other times I get this error message:



.NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error (79FFEE24) (80131506)





And still other times



The package appears to hang when running. By this I mean that the Package Execution Progress shows progress up to a point then it just stops. (The package takes about 17 seconds to run normally) CPU usage is at 1% and the package cannot be stopped.





I have deleted and re-created the package several times and I have also re-installed the service pack on the SQL Server (9.0.3054) but that did not help.





Does anyone have any other suggestions to try?





Thanks.



View 4 Replies View Related

How Can I Connect To Sql Sever 2005 Express From The Command Prompt.

Apr 24, 2007

Iam trying to connect to local copy of sql sever express from the command prompt with this command(sqlcmd)  but i get the error below. What should i do to overcome the error. Basically what i want to do is to try out some commandline backup utilities and i deadly want to know how to do a backup from the command prompt. Help is greatly appreciated.
HResult 0x2, level 16, state 1
Named pipes provider: could not open a connection to sql sever [2]
sqlcmd: Error: Microsft sql native client: An error has occurred while estarblishing a connection to the sever. When connecting to sql sever 2005, this failure may be caused by the fact that under the default settings SQL sever does not allow remote connections..
Sqlcmd: Error:  Microsoft sql native client: Login time out expired.

View 3 Replies View Related

Errors While Running Ssis Packages From The Command Prompt.

Dec 23, 2005

I have created ssis package. It has been successfully running at UI level.

But when i am trying to execute it from the command prompt by using dtexec utility it is showing the following error messages.

Error: 2005-12-23 17:01:57.67
   Code: 0xC00470FE
   Source: Data Flow Task DTS.Pipeline
   Description: The product level is insufficient for component "Flat File Source" (1).
End Error
Error: 2005-12-23 17:01:57.67
   Code: 0xC00470FE
   Source: Data Flow Task DTS.Pipeline
   Description: The product level is insufficient for component "Script Component" (9).
End Error


i have entered the command as follows.

dtexec /f "c:somefolderpackage1.dtsx"

 

Any points regarding this issue would be helpful.

 

View 7 Replies View Related

Setting Service Account To LocalSystem Via Command Prompt

Dec 5, 2007



Hello,

I was wondering if there was any way to set the service account on sql server 2005 express to Local System via command prompt.

To giva some background to this issue, I am installing 2005 express via command prompt, however, the default service account is network I believe. However, when running this, I keep getting an "error 3415" whenever I try to attach a database, which states that the files are "read only", which they are not. However, when setting the service account to local or set the security mode to windows authenticaiton, I can attach just fine.

The parameters I use to install are pretty standard:


"/qb ADDLOCAL=ALL INSTANCENAME=<name>SAPWD=<pwrd> SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 SQLAUTOSTART=1"

So I was wondering if there was some way to set the service account to local system to local using some command prompt parameter. OR if there was another way around the error 3415 that will enable me to attach a database, that I do not know about that I can use, preferrably via command prompt, but anything will be fine at this point.

Thank you all in advance.

View 6 Replies View Related

SQL Server Express Edition Silently At Command Prompt

Sep 26, 2006

I want to install the SQL Server Express Edition silently at command prompt (but want the dialog boxes, I mean with /qb option), locally, with no network options.

I want to install it with following options

i) In the Feature Selection, I need
a) Data file (Database Services)
b) Shared tools (Database Services)
c) Connectivity Components (Client Components)
d) Management Studio Express (Client Components)
ii) Instance name as €œDefault Instance€?
iii) Service Account as €œUse Built-in service accountà Local System€?
iv) Authentication Mode as €œMix mode€? with sa password as €˜sysadm€™
v) Collate Settings as €œLatin1_General_CS_AI

How could I achieve this using command prompt?

I already had done

start /wait setup.exe /qb ADDLOCAL=ALL SECURITYMODE=SQL SAPWD=sysadm SQLCOLLATION=Latin1_General_CS_AI

any other attribute need to add?

Regards,
Thanks.
Gurpreet S. Gill

View 10 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved