Max file group per database in SQL Server 2005.

Hi All,
What’s the max number of file group in SQL Server 2005 database? I knew that
in SQL Server 2000, the max file group per database is 16.
Regards,
Chen
Actually there were 256 in SQL2000. In 2005 there are 32,767.
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/13e95046-0e76-4604-b561-d1a74dd824d7.htm
Andrew J. Kelly SQL MVP
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:81540E0C-F76D-462E-9C4B-42E0C683D63E@.microsoft.com...
> Hi All,
> What?Ts the max number of file group in SQL Server 2005 database? I knew
> that
> in SQL Server 2000, the max file group per database is 16.
> Regards,
> Chen
>
|||From Books Online (2005): 32,767
The 2000 Books Online claims that max number of filegroups per database is 256. Did you try to
create more than 16? Either we have an error in Books Online, a bug in the product or perhaps you
was misinformed?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:81540E0C-F76D-462E-9C4B-42E0C683D63E@.microsoft.com...
> Hi All,
> What’s the max number of file group in SQL Server 2005 database? I knew that
> in SQL Server 2000, the max file group per database is 16.
> Regards,
> Chen
>
|||On Mon, 23 Apr 2007 20:24:41 +0100, "David Portas"
<REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote:

>http://msdn2.microsoft.com/en-us/library/aa933149(SQL.80).aspx
>According to my 2000 BOL the maximum was 256 in 2000 as well. I can't say
>I've ever put those limits to the test.
>It is often recommended that you should aim to have the same number of files
>as you have processors. On that basis you would be unlikely to need as many
>as 256 filegroups.
In regards to the processors, I would point out that this should be
read as relating to the number of processors for *active* filegroups,
you may want some more to hold archive stuff, and to facilitate
backups, to support partitioned tables, and to map to different
classes of storage (RAID 1,5,10).
All those good reasons, and I've never really played much with it
myself!
Josh
sql

Max file group per database in SQL Server 2005.

Hi All,
What’s the max number of file group in SQL Server 2005 database? I knew th
at
in SQL Server 2000, the max file group per database is 16.
Regards,
Chen"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:81540E0C-F76D-462E-9C4B-42E0C683D63E@.microsoft.com...
> Hi All,
> What's the max number of file group in SQL Server 2005 database? I knew
> that
> in SQL Server 2000, the max file group per database is 16.
> Regards,
> Chen
>
BOL is your friend:
http://msdn2.microsoft.com/en-us/library/aa933149(SQL.80).aspx
According to my 2000 BOL the maximum was 256 in 2000 as well. I can't say
I've ever put those limits to the test.
It is often recommended that you should aim to have the same number of files
as you have processors. On that basis you would be unlikely to need as many
as 256 filegroups.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Actually there were 256 in SQL2000. In 2005 there are 32,767.
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/13e95046-0e76-4604-b561-
d1a74dd824d7.htm
Andrew J. Kelly SQL MVP
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:81540E0C-F76D-462E-9C4B-42E0C683D63E@.microsoft.com...
> Hi All,
> What?Ts the max number of file group in SQL Server 2005 database? I knew
> that
> in SQL Server 2000, the max file group per database is 16.
> Regards,
> Chen
>|||From Books Online (2005): 32,767
The 2000 Books Online claims that max number of filegroups per database is 2
56. Did you try to
create more than 16? Either we have an error in Books Online, a bug in the p
roduct or perhaps you
was misinformed?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:81540E0C-F76D-462E-9C4B-42E0C683D63E@.microsoft.com...
> Hi All,
> What’s the max number of file group in SQL Server 2005 database? I knew
that
> in SQL Server 2000, the max file group per database is 16.
> Regards,
> Chen
>|||On Mon, 23 Apr 2007 20:24:41 +0100, "David Portas"
<REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote:

>http://msdn2.microsoft.com/en-us/library/aa933149(SQL.80).aspx
>According to my 2000 BOL the maximum was 256 in 2000 as well. I can't say
>I've ever put those limits to the test.
>It is often recommended that you should aim to have the same number of file
s
>as you have processors. On that basis you would be unlikely to need as many
>as 256 filegroups.
In regards to the processors, I would point out that this should be
read as relating to the number of processors for *active* filegroups,
you may want some more to hold archive stuff, and to facilitate
backups, to support partitioned tables, and to map to different
classes of storage (RAID 1,5,10).
All those good reasons, and I've never really played much with it
myself!
Josh

Max file group per database in SQL Server 2005.

Hi All,
Whatâ's the max number of file group in SQL Server 2005 database? I knew that
in SQL Server 2000, the max file group per database is 16.
Regards,
Chen"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:81540E0C-F76D-462E-9C4B-42E0C683D63E@.microsoft.com...
> Hi All,
> What's the max number of file group in SQL Server 2005 database? I knew
> that
> in SQL Server 2000, the max file group per database is 16.
> Regards,
> Chen
>
BOL is your friend:
http://msdn2.microsoft.com/en-us/library/aa933149(SQL.80).aspx
According to my 2000 BOL the maximum was 256 in 2000 as well. I can't say
I've ever put those limits to the test.
It is often recommended that you should aim to have the same number of files
as you have processors. On that basis you would be unlikely to need as many
as 256 filegroups.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Actually there were 256 in SQL2000. In 2005 there are 32,767.
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/13e95046-0e76-4604-b561-d1a74dd824d7.htm
--
Andrew J. Kelly SQL MVP
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:81540E0C-F76D-462E-9C4B-42E0C683D63E@.microsoft.com...
> Hi All,
> Whatâ?Ts the max number of file group in SQL Server 2005 database? I knew
> that
> in SQL Server 2000, the max file group per database is 16.
> Regards,
> Chen
>|||From Books Online (2005): 32,767
The 2000 Books Online claims that max number of filegroups per database is 256. Did you try to
create more than 16? Either we have an error in Books Online, a bug in the product or perhaps you
was misinformed?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:81540E0C-F76D-462E-9C4B-42E0C683D63E@.microsoft.com...
> Hi All,
> Whatâ's the max number of file group in SQL Server 2005 database? I knew that
> in SQL Server 2000, the max file group per database is 16.
> Regards,
> Chen
>|||On Mon, 23 Apr 2007 20:24:41 +0100, "David Portas"
<REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote:
>http://msdn2.microsoft.com/en-us/library/aa933149(SQL.80).aspx
>According to my 2000 BOL the maximum was 256 in 2000 as well. I can't say
>I've ever put those limits to the test.
>It is often recommended that you should aim to have the same number of files
>as you have processors. On that basis you would be unlikely to need as many
>as 256 filegroups.
In regards to the processors, I would point out that this should be
read as relating to the number of processors for *active* filegroups,
you may want some more to hold archive stuff, and to facilitate
backups, to support partitioned tables, and to map to different
classes of storage (RAID 1,5,10).
All those good reasons, and I've never really played much with it
myself!
Josh

Max Column Total in SQL Server 2005

Hello,

Is there a maximum total of columns that SQL Server 2005 limits? I have a rather lengthy import file in regards to column count, and was wondering if there was a total number of columns that a table is limited to.

Thanks.

I think it is 255, I am not so sure

|||

please check this, it may help you.

http://msdn2.microsoft.com/en-us/library/ms143432.aspx

Matrix Report RDL Generation

Hi,
I have not seen any sample that generate an Matrix Report RDL file on the
fly... Have any one tried doing that...
Thanks,
Vinodh KumarVinodh,
I have developed a simple app that creates a tabular report programatically
but the process should be the same. To minimize your development effort, you
may decide to pre-generate an empty matrix report and save it as a xml
template. Then, based on your requirements, you would generate the required
dynamic and static groups, as well as add data sources, datasets, etc.
The link to my sample WinForm app in case you decide to give it a try:
http://www.prologika.com/downloads/TechEd/2004/DAT354%20Code.zip
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"Vinodh Kumar[MS MVP]" <VinodhKumarMSMVP@.discussions.microsoft.com> wrote in
message news:FCCD9049-77CE-423A-957E-C862E98C7E6B@.microsoft.com...
> Hi,
> I have not seen any sample that generate an Matrix Report RDL file on the
> fly... Have any one tried doing that...
> Thanks,
> Vinodh Kumar|||Hi Lachev,
I was following the same approch as u mentioned but the problem i face is
setting the layout for each textbox in the column and rows dynamically. when
i create with out any layout setting it just shows the first column and
remain column hides.
Thanks,
Vinodh Kumar
"Teo Lachev" wrote:
> Vinodh,
> I have developed a simple app that creates a tabular report programatically
> but the process should be the same. To minimize your development effort, you
> may decide to pre-generate an empty matrix report and save it as a xml
> template. Then, based on your requirements, you would generate the required
> dynamic and static groups, as well as add data sources, datasets, etc.
> The link to my sample WinForm app in case you decide to give it a try:
> http://www.prologika.com/downloads/TechEd/2004/DAT354%20Code.zip
> --
> Hope this helps.
> ---
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> http://www.prologika.com
>
> "Vinodh Kumar[MS MVP]" <VinodhKumarMSMVP@.discussions.microsoft.com> wrote in
> message news:FCCD9049-77CE-423A-957E-C862E98C7E6B@.microsoft.com...
> > Hi,
> >
> > I have not seen any sample that generate an Matrix Report RDL file on the
> > fly... Have any one tried doing that...
> >
> > Thanks,
> >
> > Vinodh Kumar
>
>

mastlog.ldf

our mastlog.ldf file of Master database got deleted accidently by some user.
Is there anyway that the database could be started and new log file created
. master.mdf file is intact.
Thanks
ATDid you try restarting the server? If it won't start then you can rebuild
Master using the rebuildm utility (see Books Online for details). Then start
the server in single-user mode, restore Master from a backup (you do backup
the Master database don't you...?) or manually reattach your databases,
recreate logins, etc.
Make sure that the location of your database files is only accessible by the
administrator and the SQL Server service account so that this can't happen
again.
David Portas
SQL Server MVP
--|||David,
There is no backup available for master database. all I have is mdf file. Is
n't there any way that I can use this file to rebuild master database.
Thanks
AT|||HI
Maybe help for you:
I tested the following procedure, and successfully completed, but not guaran
tee your success.
And the future: Backup system databases periodically (daily)!
Copy to test server the master.mdf and rename
Use sp_attach_single_file_db wit another name than master (eg: NewMaser)
Use rebuilm.exe. (Copy SQL setup cd to hard disk and remove the read only fl
ag from files!)
Reinstall Service Packs and patches.
Stop the SQL server.
Create file backup from master.mdf and mastlog.ldf (Maybe You need restart
the restore)
Then start the server in single-user mode
--Like another way from here
Allow modifications to be made directly to the system catalogs
Update sysconfigures, syscurconfigs, tables from NewMaster database
Create insert statements and copy data from NewMaster to master database (US
E: WHERE NOT IN NEW MASTER..TABLE)
-sysaltfiles (or attach all production database and distribution if exist)
-sysservers (better: Recreate Linked Servers from documentation.)
-sysmessages (It is easy)
-sysxlogins (better: use the another way procedure for recreate logins)
-sysusers (or recreate users in master)
Disable modifications to be made directly to the system catalogs
Backup the master database
Test the server
Restart server
Backup master database
Another way:
-Recreate logins:
read the folowing: Microsoft Knowledge Base Article - 246133
< http://support.microsoft.com/defaul...133&Product=sql
>
Rewrite the sp_help_revlogin (use the attachaed database as source eg: FROM
master..sysxlogins --> FROM TESTSERVER.NewMaster.dbo.sysxlogins)
Recreate Linked Servers from documentation. (If You used remote server for r
eplication create linked server instead of remote)
Recreate users on master
Attach all production databases and distribution database.
Import custom sysmessages from NewMaster
Disable modifications to be made directly to the system catalogs
Backup the master database
Test the server
Restart server
Backup master database
At end:
Create scheduled backup for system databases.
And repair and repair until errors disappear. (The original values in NewMas
ter help You, do not drop!)
JBandi

master.dbo.xp_cmdshell is failing

Please help !
I run an ftp task which picks up a file from an ftp server through a package it runs fine - no errors.
If I schedule the same dts or if I run the following code in query analyser it fails
declare @.cmd varchar(2000)
declare @.ftpcommandfile varchar(2000)
--Get list of remote files
set @.ftpcommandfile = '-s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Collections\Dialer\Dialer_Files\GetDialerFile.txt'
set @.cmd = 'ftp -i -s:' + @.ftpcommandfile
Exec master.dbo.xp_cmdshell @.cmd
I get the following message:
output ---
Error opening script file -s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Collections\Dialer\Dialer_Files\GetDialerFile.txt.
Transfers files to and from a computer running an FTP server service
(sometimes called a daemon). Ftp can be used interactively.
FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-A] [-x:sendbuffer] [-r:recvbuffer] [-b:asyncbuffers] [-w:windowsize] [host]
-v Suppresses display of remote server responses.
-n Suppresses auto-login upon initial connection.
-i Turns off interactive prompting during multiple file
transfers.
-d Enables debugging.
-g Disables filename globbing (see GLOB command).
-s:filename Specifies a text file containing FTP commands; the
commands will automatically run after FTP starts.
-a Use any local interface when binding data connection.
-A login as anonymous.
-x:send sockbuf Overrides the default SO_SNDBUF size of 8192.
-r:recv sockbuf Overrides the default SO_RCVBUF size of 8192.
-b:async count Overrides the default async count of 3
-w:buffer size Overrides the default transfer buffer size of 65535.
host Specifies the host name or IP address of the remote
host to connect to.
Notes:
- mget and mput commands take y/n/q for yes/no/quit.
- Use Control-C to abort commands.
NULLYes, the error is in the FTP command, the s parameter is included twice.
--
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
"Aman" <Aman@.discussions.microsoft.com> wrote in message
news:641A9145-D95F-4D9B-A037-603546DA9178@.microsoft.com...
> Please help !
> I run an ftp task which picks up a file from an ftp server through a
package it runs fine - no errors.
> If I schedule the same dts or if I run the following code in query
analyser it fails
> declare @.cmd varchar(2000)
> declare @.ftpcommandfile varchar(2000)
> --Get list of remote files
> set @.ftpcommandfile ='-s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Collections\Dialer\Dialer_
Files\GetDialerFile.txt'
> set @.cmd = 'ftp -i -s:' + @.ftpcommandfile
> Exec master.dbo.xp_cmdshell @.cmd
> I get the following message:
>
---
> Error opening script
file -s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Collections\Dialer\Dia
ler_Files\GetDialerFile.txt.
> Transfers files to and from a computer running an FTP server service
> (sometimes called a daemon). Ftp can be used interactively.
> FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-A] [-x:sendbuffer]
[-r:recvbuffer] [-b:asyncbuffers] [-w:windowsize] [host]
>
> -v Suppresses display of remote server responses.
> -n Suppresses auto-login upon initial connection.
> -i Turns off interactive prompting during multiple file
> transfers.
> -d Enables debugging.
> -g Disables filename globbing (see GLOB command).
> -s:filename Specifies a text file containing FTP commands; the
> commands will automatically run after FTP starts.
> -a Use any local interface when binding data connection.
> -A login as anonymous.
> -x:send sockbuf Overrides the default SO_SNDBUF size of 8192.
> -r:recv sockbuf Overrides the default SO_RCVBUF size of 8192.
> -b:async count Overrides the default async count of 3
> -w:buffer size Overrides the default transfer buffer size of 65535.
> host Specifies the host name or IP address of the remote
> host to connect to.
> Notes:
> - mget and mput commands take y/n/q for yes/no/quit.
> - Use Control-C to abort commands.
> NULL
>

master.dbo.xp_cmdshell is failing

Please help !
I run an ftp task which picks up a file from an ftp server through a package it runs fine - no errors.
If I schedule the same dts or if I run the following code in query analyser it fails
declare @.cmd varchar(2000)
declare @.ftpcommandfile varchar(2000)
--Get list of remote files
set @.ftpcommandfile = '-s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Co llections\Dialer\Dialer_Files\GetDialerFile.txt'
set @.cmd = 'ftp -i -s:' + @.ftpcommandfile
Exec master.dbo.xp_cmdshell @.cmd
I get the following message:
output ---
Error opening script file -s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Co llections\Dialer\Dialer_Files\GetDialerFile.txt.
Transfers files to and from a computer running an FTP server service
(sometimes called a daemon). Ftp can be used interactively.
FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-A] [-x:sendbuffer] [-r:recvbuffer] [-b:asyncbuffers] [-w:windowsize] [host]
-v Suppresses display of remote server responses.
-n Suppresses auto-login upon initial connection.
-i Turns off interactive prompting during multiple file
transfers.
-d Enables debugging.
-g Disables filename globbing (see GLOB command).
-s:filename Specifies a text file containing FTP commands; the
commands will automatically run after FTP starts.
-a Use any local interface when binding data connection.
-A login as anonymous.
-x:send sockbuf Overrides the default SO_SNDBUF size of 8192.
-r:recv sockbuf Overrides the default SO_RCVBUF size of 8192.
-b:async count Overrides the default async count of 3
-w:buffer size Overrides the default transfer buffer size of 65535.
host Specifies the host name or IP address of the remote
host to connect to.
Notes:
- mget and mput commands take y/n/q for yes/no/quit.
- Use Control-C to abort commands.
NULL
Add PRINT @.cmd before the xp_cmdshell to see what the caommand is, but I think you have -s: in there twice.
"Aman" wrote:

> Please help !
> I run an ftp task which picks up a file from an ftp server through a package it runs fine - no errors.
> If I schedule the same dts or if I run the following code in query analyser it fails
> declare @.cmd varchar(2000)
> declare @.ftpcommandfile varchar(2000)
> --Get list of remote files
> set @.ftpcommandfile = '-s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Co llections\Dialer\Dialer_Files\GetDialerFile.txt'
> set @.cmd = 'ftp -i -s:' + @.ftpcommandfile
> Exec master.dbo.xp_cmdshell @.cmd
> I get the following message:
> output ---
> Error opening script file -s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Co llections\Dialer\Dialer_Files\GetDialerFile.txt.
> Transfers files to and from a computer running an FTP server service
> (sometimes called a daemon). Ftp can be used interactively.
> FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-A] [-x:sendbuffer] [-r:recvbuffer] [-b:asyncbuffers] [-w:windowsize] [host]
>
> -v Suppresses display of remote server responses.
> -n Suppresses auto-login upon initial connection.
> -i Turns off interactive prompting during multiple file
> transfers.
> -d Enables debugging.
> -g Disables filename globbing (see GLOB command).
> -s:filename Specifies a text file containing FTP commands; the
> commands will automatically run after FTP starts.
> -a Use any local interface when binding data connection.
> -A login as anonymous.
> -x:send sockbuf Overrides the default SO_SNDBUF size of 8192.
> -r:recv sockbuf Overrides the default SO_RCVBUF size of 8192.
> -b:async count Overrides the default async count of 3
> -w:buffer size Overrides the default transfer buffer size of 65535.
> host Specifies the host name or IP address of the remote
> host to connect to.
> Notes:
> - mget and mput commands take y/n/q for yes/no/quit.
> - Use Control-C to abort commands.
> NULL
>
|||Yes, the error is in the FTP command, the s parameter is included twice.
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
"Aman" <Aman@.discussions.microsoft.com> wrote in message
news:641A9145-D95F-4D9B-A037-603546DA9178@.microsoft.com...
> Please help !
> I run an ftp task which picks up a file from an ftp server through a
package it runs fine - no errors.
> If I schedule the same dts or if I run the following code in query
analyser it fails
> declare @.cmd varchar(2000)
> declare @.ftpcommandfile varchar(2000)
> --Get list of remote files
> set @.ftpcommandfile =
'-s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Co llections\Dialer\Dialer_
Files\GetDialerFile.txt'
> set @.cmd = 'ftp -i -s:' + @.ftpcommandfile
> Exec master.dbo.xp_cmdshell @.cmd
> I get the following message:
>

> Error opening script
file -s:\\mathshr01\Marketing\Wr_mrktg_s\SHARED\WM_IM\Co llections\Dialer\Dia
ler_Files\GetDialerFile.txt.
> Transfers files to and from a computer running an FTP server service
> (sometimes called a daemon). Ftp can be used interactively.
> FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-A] [-x:sendbuffer]
[-r:recvbuffer] [-b:asyncbuffers] [-w:windowsize] [host]
>
> -v Suppresses display of remote server responses.
> -n Suppresses auto-login upon initial connection.
> -i Turns off interactive prompting during multiple file
> transfers.
> -d Enables debugging.
> -g Disables filename globbing (see GLOB command).
> -s:filename Specifies a text file containing FTP commands; the
> commands will automatically run after FTP starts.
> -a Use any local interface when binding data connection.
> -A login as anonymous.
> -x:send sockbuf Overrides the default SO_SNDBUF size of 8192.
> -r:recv sockbuf Overrides the default SO_RCVBUF size of 8192.
> -b:async count Overrides the default async count of 3
> -w:buffer size Overrides the default transfer buffer size of 65535.
> host Specifies the host name or IP address of the remote
> host to connect to.
> Notes:
> - mget and mput commands take y/n/q for yes/no/quit.
> - Use Control-C to abort commands.
> NULL
>

master.dbo.xp_cmdshell is failing

Please help !
I run an ftp task which picks up a file from an ftp server through a package
it runs fine - no errors.
If I schedule the same dts or if I run the following code in query analyser
it fails
declare @.cmd varchar(2000)
declare @.ftpcommandfile varchar(2000)
--Get list of remote files
set @.ftpcommandfile = '- s:\\mathshr01\Marketing\Wr_mrktg_s\SHARE
D\WM_IM\Col
lections\Dialer\Dialer_Files\GetDialerFi
le.txt'
set @.cmd = 'ftp -i -s:' + @.ftpcommandfile
Exec master.dbo.xp_cmdshell @.cmd
I get the following message:
output
--
--
Error opening script file - s:\\mathshr01\Marketing\Wr_mrktg_s\SHARE
D\WM_IM\C
ollections\Dialer\Dialer_Files\GetDialer
File.txt.
Transfers files to and from a computer running an FTP server service
(sometimes called a daemon). Ftp can be used interactively.
FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a]
[-A] [-x:sendbuffer] [-r:recvbuffer] [-b:asyncbuffers] [
-w:windowsize] [host]
-v Suppresses display of remote server responses.
-n Suppresses auto-login upon initial connection.
-i Turns off interactive prompting during multiple file
transfers.
-d Enables debugging.
-g Disables filename globbing (see GLOB command).
-s:filename Specifies a text file containing FTP commands; the
commands will automatically run after FTP starts.
-a Use any local interface when binding data connection.
-A login as anonymous.
-x:send sockbuf Overrides the default SO_SNDBUF size of 8192.
-r:recv sockbuf Overrides the default SO_RCVBUF size of 8192.
-b:async count Overrides the default async count of 3
-w:buffer size Overrides the default transfer buffer size of 65535.
host Specifies the host name or IP address of the remote
host to connect to.
Notes:
- mget and mput commands take y/n/q for yes/no/quit.
- Use Control-C to abort commands.
NULLAdd PRINT @.cmd before the xp_cmdshell to see what the caommand is, but I th
ink you have -s: in there twice.
"Aman" wrote:

> Please help !
> I run an ftp task which picks up a file from an ftp server through a packa
ge it runs fine - no errors.
> If I schedule the same dts or if I run the following code in query analys
er it fails
> declare @.cmd varchar(2000)
> declare @.ftpcommandfile varchar(2000)
> --Get list of remote files
> set @.ftpcommandfile = '- s:\\mathshr01\Marketing\Wr_mrktg_s\SHARE
D\WM_IM\
Collections\Dialer\Dialer_Files\GetDiale
rFile.txt'
> set @.cmd = 'ftp -i -s:' + @.ftpcommandfile
> Exec master.dbo.xp_cmdshell @.cmd
> I get the following message:
> output
--
--
> Error opening script file - s:\\mathshr01\Marketing\Wr_mrktg_s\SHARE
D\WM_IM
\Collections\Dialer\Dialer_Files\GetDial
erFile.txt.
> Transfers files to and from a computer running an FTP server service
> (sometimes called a daemon). Ftp can be used interactively.
> FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a
] [-A] [-x:sendbuffer] [-r:recvbuffer] [-b:asyncbuffers]
1;-w:windowsize] [host]
>
> -v Suppresses display of remote server responses.
> -n Suppresses auto-login upon initial connection.
> -i Turns off interactive prompting during multiple file
> transfers.
> -d Enables debugging.
> -g Disables filename globbing (see GLOB command).
> -s:filename Specifies a text file containing FTP commands; the
> commands will automatically run after FTP starts.
> -a Use any local interface when binding data connection.
> -A login as anonymous.
> -x:send sockbuf Overrides the default SO_SNDBUF size of 8192.
> -r:recv sockbuf Overrides the default SO_RCVBUF size of 8192.
> -b:async count Overrides the default async count of 3
> -w:buffer size Overrides the default transfer buffer size of 65535.
> host Specifies the host name or IP address of the remote
> host to connect to.
> Notes:
> - mget and mput commands take y/n/q for yes/no/quit.
> - Use Control-C to abort commands.
> NULL
>|||Yes, the error is in the FTP command, the s parameter is included twice.
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
"Aman" <Aman@.discussions.microsoft.com> wrote in message
news:641A9145-D95F-4D9B-A037-603546DA9178@.microsoft.com...
> Please help !
> I run an ftp task which picks up a file from an ftp server through a
package it runs fine - no errors.
> If I schedule the same dts or if I run the following code in query
analyser it fails
> declare @.cmd varchar(2000)
> declare @.ftpcommandfile varchar(2000)
> --Get list of remote files
> set @.ftpcommandfile =
'- s:\\mathshr01\Marketing\Wr_mrktg_s\SHARE
D\WM_IM\Collections\Dialer\Dialer_
Files\GetDialerFile.txt'
> set @.cmd = 'ftp -i -s:' + @.ftpcommandfile
> Exec master.dbo.xp_cmdshell @.cmd
> I get the following message:
>
---
> Error opening script
file - s:\\mathshr01\Marketing\Wr_mrktg_s\SHARE
D\WM_IM\Collections\Dialer\Dia
ler_Files\GetDialerFile.txt.
> Transfers files to and from a computer running an FTP server service
> (sometimes called a daemon). Ftp can be used interactively.
> FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-
A] [-x:sendbuffer]
[-r:recvbuffer] [-b:asyncbuffers] [-w:windowsize] [host]
>
> -v Suppresses display of remote server responses.
> -n Suppresses auto-login upon initial connection.
> -i Turns off interactive prompting during multiple file
> transfers.
> -d Enables debugging.
> -g Disables filename globbing (see GLOB command).
> -s:filename Specifies a text file containing FTP commands; the
> commands will automatically run after FTP starts.
> -a Use any local interface when binding data connection.
> -A login as anonymous.
> -x:send sockbuf Overrides the default SO_SNDBUF size of 8192.
> -r:recv sockbuf Overrides the default SO_RCVBUF size of 8192.
> -b:async count Overrides the default async count of 3
> -w:buffer size Overrides the default transfer buffer size of 65535.
> host Specifies the host name or IP address of the remote
> host to connect to.
> Notes:
> - mget and mput commands take y/n/q for yes/no/quit.
> - Use Control-C to abort commands.
> NULL
>

Master, Tempdb, Msdb, Model?

I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:

> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||And also move the log file to a separate file
"JLS" wrote:

> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
> Any opinions are appreciated!
>
|||I use to have data and log on same drive for system databases. The possible exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as for other databases.
Also, moving database files for system databases is a bit special, so read KB 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!
|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFTNGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on the same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user database & logs on separate drives, but I am not sure of what a "best practice" is for the Sql system databases.
Any opinions are appreciated!

Master, Tempdb, Msdb, Model?

I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:

> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||And also move the log file to a separate file
"JLS" wrote:

> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||I use to have data and log on same drive for system databases. The possible
exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as f
or other databases.
Also, moving database files for system databases is a bit special, so read K
B 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system da
tabases.
Any opinions are appreciated!|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!