Is your table size about 5 MB

MW

DBCC SHOWCONTIG

It Will show you page density, extent switches and so on.

refer it on BOL

MW

z

MW

If you're planning to use QA then the user need permission to exec. xp_cmdshell

otherwise just the appropriate permissions to write data.

for bulk insert:

Your user has to be a member of...

I tried this query, which is similar to yours and the execution plan seem very efficient

I don't know, but you can try the query to see if you get same...

Not being harsh but still cryptic

please show us your table structure and your sample query

Also let us know what the criterias are for selecting, updating or ...

MW

I've tested this script and it should work.

Try it and if you have questions, I'll check your reply.

Note: I've generated my own data, so if you want you can comment...

Try un-registering the server in EM and registering it again.

You can also change the value for LOCK_TIMEOUT setting.

More info. on BOL

MW

Use the SQL server network utility wizard and check for

enabled protocols and their properties.

MW

Create Table #Temp_Table (BackUp_Location VARCHAR(40))

Declare @Error INT

Insert Into #Temp_Table

Exec @Error = Master..xp_cmdshell 'env | FindStr /I "SQL_BACKUP"' (Change SQL_BACKUP

...

Have you tried changing the value for Lock_Timeout sys. var

Also you can refer to "Troubleshooting Deadlocks" on BOL

MW

Just another way of doing it

Select a.*, c.*

From ArchivedLeads.dbo.allAgedLeads a, applicant c

Where Exists(Select alp.leadSourceId

From AgedLeadPlanMatchedLead alp

...

I usually use bulk insert to perform quick imports

I don't know what you're using but try this

Bulk Insert (Table_Name) From 'Input_FilePath'

With (FieldTerminator = 'Field_Delimeter',

...

Unless you're an expert in Regex

MW

Check the data type of your app. variable

Your app. variable is most likely wrong data type.

MW

Edited by - mworku on 06/12/2003 6:40:36 PM