Viewing 15 posts - 58,906 through 58,920 (of 59,067 total)
> Do you think this may pose deadlock problems? This should be the only stored procedure or even script for that matter that would ever access this table.
Fred,
Yeah, your method...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2004 at 6:16 am
A third party company that we had the great misfortune of hiring, did something similar (nearly identical) in our database... it caused an average of 620 deadlocks a day. The...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2004 at 11:56 pm
Not sure why you wouldn't want to use a set based Trigger for this... it's a tried and true method and will run raster than anything else you could throw...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2004 at 11:08 pm
>Will having 2 records for the one shift with 2 seperate ID's affect my Analyisis Services CUBES?
Here's a bit of code where you will not have two records... most of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2004 at 1:11 am
Perhaps instead of a stored procedure, it should be a view so that you can select from it as if it were a table. Also, take a look at OpenRowSet...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2004 at 8:58 pm
Dude?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2004 at 9:00 am
Do you want to automatically delete the dupes (leaving only the earliest or the latest) or just find them? Frank is correct... the search leads to lot's of "duplicate row" goodies...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2004 at 7:24 am
You're welcome and thanks for the feed back.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2004 at 8:21 am
We ran into a similar problem at work...
You have an IS NULL in the WHERE clause and while that is not in itself a problem, you've probably run into a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2004 at 3:50 am
I ran into a similar problem with a rather lengthy query and it became a real pain. I originally used IF logic but it required that the same lengthy query...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2004 at 2:59 am
Brian,
Really nice job on the "Stored Procedures and Caching" article. Looks like a few other folks share my sentiment. Definitely above the norm of what I've come to expect from...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2004 at 8:33 pm
If you format the "preview" table (also known as a "staging table") correctly, BCP will catch the kinds of errors you mentioned. Dates should always go into a DateTime data-type column. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2004 at 12:08 am
I had some very good luck using a CASE statement in a WHERE clause for just this purpose. Try something like this...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 16, 2004 at 11:54 pm
What are you using to do the export? If you are using BCP and use \" to enclose text fields in quotes in the format file, you should have no...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 8:22 pm
Adam is correct... basically, there is no way to store just the Month and Year in a datetime field. In fact, you cannot store a "formatted" date in a datetime...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2004 at 8:13 pm
Viewing 15 posts - 58,906 through 58,920 (of 59,067 total)