I have wrestled with a similar problem before (on SQL 7).

If you add 'OPTION (MAXDOP 1)' to the end of the SQL statement, it forces SQL Server to not use...

I don't think you can do that with a Maintenance Plan, but you could easily do it with a SQL Agent job.

Just create a job to execute the command:-

backup database...

You could always backup to the same backup file name each time, and use the 'WITH INIT' clause of the BACKUP command to overwrite the file.

The sp_cursorfetch call is being made by your client machine's database API (e.g. ADO or ODBC) to retrieve data from SQL Server.

The way the API is doing this is...

Just execute this:-

alter database dbname set single_user with rollback immediate

That will roll back any work currently being done by the users immediately, then place the database into single user mode.

...

You don't have to do anything. By default, insert triggers are disabled for bulk insert anyway.

If you want them enabled, you have to specify the 'FIRE_TRIGGERS' option on the bulk...

If you know the sequence you want the countries to apprear in, then use a CASE statement to define the order e.g.

select Street,City,Country,

case Country

when 'United...

I don't think a strategy of indexing these columns just because SQL Server has created statistic on them is necessary.

You should really examine the queries and make a judgement...

Regardless of your recovery model, SQL Server has to use the transaction log to roll back any failed statements (or group of statements if bound up in a single transaction).

Your...

I have seen the same thing.

If you use NT Authentication to connect to Enterprise Manager or Query Analyser, then it seems to propagate the user name as Anonymous to the...

Have you tried zapping the registration on Enterprise Manager and re-creating it?

Consider it, but analyse your queries to see whether they really require an index on those columns.

It may just be that somebody ran a 'one-off' query, and SQL Server wanted...

Not sure if this is still relevant with SQL 200/Windows 2000, but we had a similar problem with NT4 and SQL7 a while back, and it was down to the...

Those indexes are created by SQL Server when you have the 'Auto Create Statistics' on.

They get created when the optimiser needs to create distribution statistics on a non-indexed column, in...

Default parameters must be NULL or a Constant. GETDATE is obviously not a constant.

Try:-

alter PROCEDURE rptCurrentInCome

@RunnerID INT=NULL,

@StartDate DATETIME='01/01/1900',@EndDate DATETIME=NULL

AS

if @enddate is null set @enddate = GETDATE()

...