Database

Haven't seen that problem but could be related to the fact that the fix is older than your server environment. As a workaround, have you tried enabling MARS? The need to optimize rises from a bad design.My articles[^]

Excellent, there is another potentially useful keyword I have never used (or knew about). Never underestimate the power of human stupidity RAH

Anytime, glad to be of help :-)

Snowflake schema[^] List of common misconceptions

You are looking for a dynamic where clause, take a look at come of these responses[^] Most of these will work with a cursor. Never underestimate the power of human stupidity RAH

PDTUM wrote: PLEASE accept my apology... no problem. PDTUM wrote: I hope that you will want to respond to me the next time Sure, why not?

Put this somewhere where it will run before doing any database stuff: AppDomain.CurrentDomain.SetData("DataDirectory", System.Environment.GetFolderPath(System.Environment.SpecialFolder.CommonApplicationData));//LocalApplicationData)); Depending on whether you're installing for "everyone" or for each individual user, choose the CommonApplicationData or LocalApplicationData "SpecialFolder" there at the end. And, of course, that's where the database file has to sit. (which makes debugging from within Visual Studio a pain in the butt.) I thought you had to go to Pittsburgh for that. My Mu[sic] My Films My Windows Programs, etc.

Building on Chris's post: If you need only max by state you might try something like: select yourtable.serialnumber, yourtable.name, yourtable.city, yourtable.state from yourtable Inner join ( select Max(serialnumber), state from yourtable group by state) as sub1 on yourtable.serialnumber = sub1.serialnumber (NOT TESTED)

But when I click 'Good Answer' on a forum reply, I get a message saying 'Marked as answer'.

Luc Pattyn wrote: DAO Ahhhhh!!!! Good old DAO :-)

That was my opinion, but without the authority of experience I am glad to have it confirmed. That dev now has a refactoring (rewrite) job to do. Luckilly this was the first couple of jobs I have given him. Never underestimate the power of human stupidity RAH

Just one, on SQL Server 6 on WinNT, about ten years ago -- it simply disappeared occasionally. I see no reason to trust them when there are better solutions now.

Shameel wrote: AFAIK, SQL Server does not support packages, only Oracle does FYI, SSIS (SQL Server Intergration Services) does use the term 'packages' for its code base. Common sense is admitting there is cause and effect and that you can exert some control over what you understand.

current1999 wrote: I just wonder that I must have SQL 2000 before I can experiment the conversion The answer is no, if you are just converting an existing package then all you need is the target version. Common sense is admitting there is cause and effect and that you can exert some control over what you understand.

If it was me I would investigate the requirement itself. But other than that presuming it is possible you might to research it using the term "session" or "user session".

The only way you can change the values of a row being updated is in a BEFORE UPDATE trigger. AFTER UPDATE trigger is triggered "after" the row is updated, and therefore, understandably, the :NEW table can't be modified. "Don't confuse experts with facts" - Eric_V modified on Friday, August 19, 2011 10:34 AM

Kyudos wrote: Crappy reasons No worse than some I have heard! Try this, uses join and a sub select. SELECT DISTINCT Components.Description, Temp.Description FROM Assemblies INNER JOIN Components ON Components.ComponentKey = Assemblies.AssemblyKey AND Components.Flags = 1 INNER JOIN (SELECT DISTINCT Assemblies.ItemKey,Components.Description FROM Assemblies INNER JOIN Components on Assemblies.ItemKey = Components.ComponentKey) T ON Assemblies.ItemKey = T.ItemKey Never underestimate the power of human stupidity RAH

Hey, Here is the link to the log with failure : [log] Can not make sense of it. Thanks in advance.