double check your client software has SP4 applied (or the software level of your connected SQL2000 instance).

GSquared (1/7/2010)

---

Servers usually aren't all that loud, but the limit would really...

Gail published a very explanatory article at SSC:

http://www.sqlservercentral.com/articles/64582/

Or by activating a login trigger (needs sp2) which only alows 'sa' or members of sysadmins sqlgroup.

Could be usefull if you intend to acivate it for a maintenance window, but...

if you want to, you can attach the errorlog file to your reply (if it is not to big) so we can have a look

How does your .net application connect to sqlserver

or

how is the webservice you are calling connecting to sqlserver ?

If it is tunneling credentials, chances are a user ( or...

Spend 100$ for a 1.5TB USB disk.

Hook that onto your server.

Create the db backup to that usb disk

robocopy the backup file to your network safe zone location.

Is your target transaction log big enough to be able to process all incoming replication commands ?

- file size

- autogrow enabled ? ( grow by reasonable MB !)

- can your...

You need to provide full rows (all columns and in the exact column order ! ) if you want to use bulk insert !

Workaround:

Create a view that contains only the...

GoofyKC (1/5/2010)

---

Thanks Rahul, We are running SQL Server 2008 SP1 (10.0.2531). Did Microsoft give you any KB for this Traceflag? I have tried to google it and what little I...

btw Error: 250071 is an error number > 49999 which indicates it is a user defined error code !

Order your devs to figure out in which occasions they raise this...

why would you only allow sa to connect ?

Is it for sql server (software) maintenance ?

You could start sqlserver using the maintenance parameter. (check books onlin for startup parameters...

You are probably on the right track ...

tempdb is used for way more activities than just holing the data for temporary tables. Cursors, sorts, group by, intermediate results for working...

I would first restrict the growth of tempdb, so it doesn't fill up your disk.

I would start a sqlserver profiler session to capture the ongoing queries.

You'll probably find a set...

of course you should also pose the question : WHY ??

If this is some kind of "primitive" encryption, SQLServer nowadays has a better alternative !

Is it to confuse network sniffers...