"Pippen" <not@valid.mail> wrote in message
news:eOKdnQmC4IBURSrZnZ2dnUVZ_rGdnZ2d@comcast.com...
>I trying to use scptxfr.exe instead of Enterprise Manager to script
>databases.
>
> Here is what I have:
> MS SQL Server 2000 SP 4 Developer Edition and MS SQL Server Enterprise
> Edition
>
> Here is the code I am trying to use
>
> master..xp_cmdshell
> '"C:\Program Files\Microsoft SQL Server\MSSQL\Upgrade\scptxfr.exe"
> /s DEVSRV07 /I d/ master /f e:\Temp\MasterBackup.txt'
>
> What I get is:
>
> Invalid command arguments
> Command Line Syntax:
> SCPTXFR /s <server> /d <database> {[/I] | [/P <password>]}
> {[/F <script files directory>] | [/f <single script file>]}
> /q /r /O /T /A /E /C <CodePage> /N /X /H /G /Y /?
>
> NULL
>
>
>
> When I try the help it DOES work:
> master..xp_cmdshell
> '"C:\Program Files\Microsoft SQL Server\MSSQL\Upgrade\scptxfr.exe" /?'
>
> What I get is:
>
> Command Line Syntax:
> SCPTXFR /s <server> /d <database> {[/I] | [/P <password>]}
> {[/F <script files directory>] | [/f <single script file>]}
> /q /r /O /T /A /E /C <CodePage> /N /X /H /G /Y /?
>
> /s - Indicates the source server to connect to.
> /d - Indicates the source database to script.
> /I - Use integrated security.
> /P - Password to use for 'sa'. Note that login ID is always 'sa'.
> If /P not used or if a password does not follow the flag,
> a null password is used. Not compatible with /I.
> /F - The directory into which the script files should be generated.
> This means one file is generated for each category of objects.
> /f - The single file in which all script is to be saved.
> Not compatible with /F.
> /q - Use quoted identifiers in the generated scripts.
> /r - Include drop statements for the objects in the script.
> /O - Generate OEM script files. Cannot be used with /A or /T.
> This is the default behavior.
> /T - Generate UNICODE script files. Cannot be used with /A or /O.
> /A - Generate ANSI script files. Cannot be used with /T or /O.
> /? - Command line help.
> /E - Stop scripting when error occurs.
> Default behavior is to log the error, and continue.
> /C - Indicate the CodePage which overrides the server CodePage.
> /N - Generate ANSI PADDING.
> /X - Script SPs and XPs to separate files.
> /H - Generate script files without header (default: with header).
> /G - Use the specified server name as the prefix for the generated output
> files (to handle dashes in server name).
> /Y - Generate script for Extended Properties (valid for 8.x server only).
> NULL
>
> Anyone have any ideas? I used the example from
> http://www.norbtechnologies.com/pdf/Technical%20Article%20-%20How%20to%20Schedule%20a%20SQL%20Server%20Database%20Creation%20Script.pdf
> Example 2
>
> Thanks,
>
> -js
>

"Pippen" <not@valid.mail> wrote in message
news:54ydnZwgvMn5RCrZnZ2dnUVZ_oSdnZ2d@comcast.com...
>
> "Pippen" <not@valid.mail> wrote in message
> news:eOKdnQmC4IBURSrZnZ2dnUVZ_rGdnZ2d@comcast.com...
>>I trying to use scptxfr.exe instead of Enterprise Manager to script
>>databases.
>>
>> Here is what I have:
>> MS SQL Server 2000 SP 4 Developer Edition and MS SQL Server Enterprise
>> Edition
>>
>> Here is the code I am trying to use
>>
>> master..xp_cmdshell
>> '"C:\Program Files\Microsoft SQL Server\MSSQL\Upgrade\scptxfr.exe"
>> /s DEVSRV07 /I d/ master /f e:\Temp\MasterBackup.txt'
>>
>> What I get is:
>>
>> Invalid command arguments
>> Command Line Syntax:
>> SCPTXFR /s <server> /d <database> {[/I] | [/P <password>]}
>> {[/F <script files directory>] | [/f <single script file>]}
>> /q /r /O /T /A /E /C <CodePage> /N /X /H /G /Y /?
>>
>> NULL
>>
>>
>>
>> When I try the help it DOES work:
>> master..xp_cmdshell
>> '"C:\Program Files\Microsoft SQL Server\MSSQL\Upgrade\scptxfr.exe" /?'
>>
>> What I get is:
>>
>> Command Line Syntax:
>> SCPTXFR /s <server> /d <database> {[/I] | [/P <password>]}
>> {[/F <script files directory>] | [/f <single script file>]}
>> /q /r /O /T /A /E /C <CodePage> /N /X /H /G /Y /?
>>
>> /s - Indicates the source server to connect to.
>> /d - Indicates the source database to script.
>> /I - Use integrated security.
>> /P - Password to use for 'sa'. Note that login ID is always 'sa'.
>> If /P not used or if a password does not follow the flag,
>> a null password is used. Not compatible with /I.
>> /F - The directory into which the script files should be generated.
>> This means one file is generated for each category of objects.
>> /f - The single file in which all script is to be saved.
>> Not compatible with /F.
>> /q - Use quoted identifiers in the generated scripts.
>> /r - Include drop statements for the objects in the script.
>> /O - Generate OEM script files. Cannot be used with /A or /T.
>> This is the default behavior.
>> /T - Generate UNICODE script files. Cannot be used with /A or /O.
>> /A - Generate ANSI script files. Cannot be used with /T or /O.
>> /? - Command line help.
>> /E - Stop scripting when error occurs.
>> Default behavior is to log the error, and continue.
>> /C - Indicate the CodePage which overrides the server CodePage.
>> /N - Generate ANSI PADDING.
>> /X - Script SPs and XPs to separate files.
>> /H - Generate script files without header (default: with header).
>> /G - Use the specified server name as the prefix for the generated output
>> files (to handle dashes in server name).
>> /Y - Generate script for Extended Properties (valid for 8.x server only).
>> NULL
>>
>> Anyone have any ideas? I used the example from
>> http://www.norbtechnologies.com/pdf/Technical%20Article%20-%20How%20to%20Schedule%20a%20SQL%20Server%20Database%20Creation%20Script.pdf
>> Example 2
>>
>> Thanks,
>>
>> -js
>>
>
> I did try the /P MyPassWord instead of the /I option. The password I used
> was the sa password that I did try to verify.
>
> Thanks,
>
> -p
>