Regarding BULK insert

I am doing a bulk insert and i am A DBO on the database and i can't do it unless i
added my self to the bulkinsert admin server role.
do any body why is that.why it needs a server role..
chinn,
Because of the way BULK INSERT is implemented. The data goes straight
into the server as an OLEDB row set. From Books Online: "the BULK INSERT
statement requires read access to any data on the network and machine
the server is running on." That is why it is locked down.
You might also want to be aware of this gotcha:
BUG: Cannot Perform BULK INSERT with Bulkadmin Privileges
http://support.microsoft.com/?id=302621
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
chinn wrote:
> I am doing a bulk insert and i am A DBO on the database and i can't do it unless i
> added my self to the bulkinsert admin server role.
> do any body why is that.why it needs a server role..

Reduce SQL Server Log File

Hi All
Our SQL Server log file is big enough, and I can't figure out how to reduce
the size of the log file. can you help how to reduce the size?
Thanks you
Some links to look out for help are:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
and Check out DBCC SHRINKFILE in the Books Online.
One of the gotchas regarding log files is that the file will not shrink
until a virtual log boundary has been crossed. This will require subsequent
database updates after the shrink.
Check: http://tinyurl.com/5rc5b
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
http://groups.msn.com/SQLBang
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"Firmansyah" <syahmail@.softhome.net> wrote in message
news:Oc26x9PrEHA.592@.TK2MSFTNGP11.phx.gbl...
> Hi All
> Our SQL Server log file is big enough, and I can't figure out how to
reduce
> the size of the log file. can you help how to reduce the size?
> Thanks you
>
|||Thank you very much your information very useful for me
"Vinodk" <vinodk_sct@.NO_SPAM_hotmail.com> wrote in message
news:OdmvXyQrEHA.2184@.TK2MSFTNGP10.phx.gbl...
> Some links to look out for help are:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> and Check out DBCC SHRINKFILE in the Books Online.
> One of the gotchas regarding log files is that the file will not shrink
> until a virtual log boundary has been crossed. This will require
> subsequent
> database updates after the shrink.
> Check: http://tinyurl.com/5rc5b
> --
> HTH,
> Vinod Kumar
> MCSE, DBA, MCAD, MCSD
> http://www.extremeexperts.com
> http://groups.msn.com/SQLBang
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinf...2000/books.asp
>
> "Firmansyah" <syahmail@.softhome.net> wrote in message
> news:Oc26x9PrEHA.592@.TK2MSFTNGP11.phx.gbl...
> reduce
>
|||Sorry, if I delete the log file, is there any influence ? and is there any
risk if I delete that file?
Thank you
"Firmansyah" <syahmail@.softhome.net> wrote in message
news:uPbD5xRrEHA.2776@.TK2MSFTNGP14.phx.gbl...
> Thank you very much your information very useful for me
>
> "Vinodk" <vinodk_sct@.NO_SPAM_hotmail.com> wrote in message
> news:OdmvXyQrEHA.2184@.TK2MSFTNGP10.phx.gbl...
>
|||You should not delete the log file for any database. It result in log file
not being created and a suspect database and you could end up with much
worse situation. There is a much easier way to reduce the log file size
with SQL Server.
Look at the KB article,
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/?id=272318
If that does not shrink file, you might want to take a look at,
INF: Transaction Log Grows Unexpectedly or Becomes Full on SQL Server
http://support.microsoft.com/?id=317375