The error is caused by next run date which can be 0

a simple workaround

CASE

WHEN msdb..sysjobschedules.next_run_date =0 THEN NULL

ELSE cast(cast(msdb..sysjobschedules.next_run_date as varchar(15)) as datetime)

END AS next_run_date

,

since it are all inner joins, what about

SELECT d.item_number, h.order_date, h.order_number, h.invoice_number, d.order_amount

FROM factsql.dbo.sopinh h

INNER JOIN factsql.dbo.sopind d

ON d.company_number = h.company_number

AND d.order_number = h.order_number

AND d.invoice_number =...

Found a link of 2003 versions comparisions:

http://www.microsoft.com/windowsserver2003/evaluation/features/compareeditions.mspx

I believe the big difference is the amount of hardware it can address (cpu/memory/clustering)

1)you can change the timeout settings of enterprise manager in the Tools menu -> Options.

2)Is there a linked server in the query (default time out 600 seconds)

3)Enterprise Manager is quite...

That square could be a half line feed.

Are the textfile originating from mac or unix systems?

If you open the textfile with notepad,do you see the squares too?

Perhaps this script can help you out:

http://www.sqlservercentral.com/scripts/contributions/1301.asp

Mostly we create a Trigger on a table:

Table Original

Column1 (PK)

Column2

Table History

Column1

Column2

ChangedDate

ChangedUser

CREATE TRIGGER TR_ORIGINAL_INSERT ON dbo.Original

FOR INSERT /*INSERTS ONLY*/

INSERT INTO dbo.HISTORY

(column1,column2,ChangedDate,ChangedUser)

SELECT Column1,Column2,CURRENT_TIMESTAMP,CURRENT_USER

from inserted.column1,inserted.column2

Your application can read out the columns and concatenate...

No longer reliable for sql server 2000

See the books online.

Sql 6.5

The DBCC PERFMON and DBCC SQLPERF statements documented SQL Server performance statistics used for studying SQL Server performance.

Sql 2000

No longer...

Why would you need the client tools on each pc?

MDAC 2.8 or later should be sufficient.

The same questions popped up earlier this week.

Have a look at

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=222383

or try a search on the forums on

blob, pdf ...

Haven't done it myself

CREATE TRIGGER TR_EMPLOYER_HISTORY /*NAME OF TRIGGER*/

ON dbo.[Emp Table] /*NAME OF TABLE

/*Darn spaces*/

FOR UPDATE /*ONLY FOR UPDATES*/

/*Only inserts when the salary is modified*/

INSERT INTO EmpHis

( /*COLUMNNAMES HERE*/

)

SELECT

INSERTED.Column1,INSERTED.Column2,...

FROM INSERTED /*CONTAINS THE...

seems enterprise manager has a limit of 1024 / field

http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1124064,00.html

Are you monitoring SQL memory usage using the performance counters SQL Server provides or via the task-manager?

So @SeedTableName,@TestExecutionTableName are variable tables?

Looks like xpstar.dll has not been put in the registry.

Try adding it by using regsvr32

like regsvr32 xpstar.dll in the directory where xpstar.dll is located.