I agree, *might* work.. Not promising, but it is a place to start and if he has a couple different servers he can find out for himself.

CEWII

You *might* find something in the registry.. Here is a little taste of where to look:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQLEXPRESS\Setup]

"ProductCode"="{B5153233-9AEE-4CD4-9D2C-4FAAC870DBE2}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQLEXPRESS\Setup\SQL_Engine_Core_Inst]

"ProductCode"="{B5153233-9AEE-4CD4-9D2C-4FAAC870DBE2}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQLEXPRESS\Setup\SQL_Engine_Core_Inst\1033]

"ProductCode"="{58721EC3-8D4E-4B79-BC51-1054E2DDCD10}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQLEXPRESS\Setup\SQL_FullText_Adv]

"ProductCode"="{06A7EA72-0F00-4D53-A81C-A5D925711141}"

CEWII

I'm going to go with Jeff on most of this. I'd almost be willing to bet money that you are experiencing I/O bottlenecks. How is your disk subsystem...

Although I'm not sure this is relavent..

Perhaps:

vars("AOMDate").Value = ActualDate.ToString("MM-dd-yyyy")

Should be:

vars("User::AOMDate").Value = ActualDate.ToString("MM-dd-yyyy")

I can't remember if it cares..

CEWII

So you are saying there was no error generated but the statement just didn't work?

CEWII

At first blush that looks like a workable solution..

CEWII

I try to never store passwords or other sensitive data IN my packages. Trusted security used for all connections if possible. I also tend to store such things...

Short answer is that the compilation figures out how the execution of the stored procedure will occur, how tables will be accessed and how joins will be handled. It...

What method are you using to tell that the files are for today? Is there a code in the filename or are you using file date?

If there is a...

The error message would have helped..

But, I seem to remember something about:

SET <table1>.<field1> = <table2>.<field1>,<table1>.<field2> = 'blah'

I think it should just be:

SET <field1> = <table2>.<field1>,<field2> = 'blah'

You have already told...

Peter Samson (2/4/2010)

---

First, can you give us an approximation of the workload and concurrent users? Small, moderate, large?

Second, are there a lot of Functions or Stored Procedures created for...

I stand corrected then.

CEWII

In SQL 2000 that would probably be right.

In SQL 2005 you right click and choose "Edit Top 200 Rows". This is the limitation.

However, I would say you should only...

Wow, that is about as simple as it gets.. And since you already checked for default, that is really odd.

CEWII

In files specify:

sqlserver_????????.xls

It could pickup sqlserver_AAAAAAAA because ? is not specific to numbers.. But this is about the only way I can think of..

CEWII