Viewing 15 posts - 50,296 through 50,310 (of 59,091 total)
To the best of my knowledge, point of time recovery that includes bulk inserts, is possible only with FULL RECOVERY... and then only if you're backing up the log very...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 9:54 am
mobasha (5/26/2008)
he ask for sa i say i have no such login, tell me what u want and i will provide u with a user to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 9:37 am
Without knowing the structure of the data at hand, I'd say just load it, edit it when necessary, and add to it whenever you need to. If necessary, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 9:33 am
I've found that there's a "tipping" point between the performance gains realized in denormalizing information and joining for the same information. If the denormalization results in millions of rows,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 9:29 am
Believe it or not, it means it's connected and working fine. I had the same problem when I first saw it... Red usually means something is wrong.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 9:19 am
I'm pretty sure that you just shot yourself in the head performance wise... the myth that all CLR's are faster than T-SQL is just that... a myth. Most of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 9:14 am
If you want the data automatically from the previous month based on today's date, do NOT use BETWEEN because it will either miss most of the last day of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 9:09 am
I agree... shared locks on a set of reporting tables aren't much more expensive than using a WITH (NOLOCK), and WITH (NOLOCK) will not prevent deadlocks. Don't forget that...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 8:51 am
I can't get over the gut feeling that it's a bad idea, but here goes...
First, make sure that some other user, preferably some DBA (yourself?) has SA privs.
Second, open SSMS...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 7:17 am
One more quick question... which table are all the times (and other columns) coming from? I can't tell because you're not using table aliases on the columns. The...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2008 at 7:07 am
I agree with Gus... multiple-choice questions make a test easy to grade and that's all. My "favorite" multiple choice question looks something like the following...
Which of the following roles...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2008 at 7:24 pm
I don't see why you need a CASE statement to begin with...
CONVERT(DECIMAL(6,2),ISNULL(SUM(CONVERT(NUMERIC,CRC.Contact))/NULLIF(SUM(TalkTime+HoldTime+WrapTime+WaitTime+PreviewTime+DeadTime)/3600.0,0),0))
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2008 at 5:56 pm
One simple forumla will return correctly whether the domain is present or not...
DECLARE @MyDomainName SYSNAME
SET @MyDomainName = 'firstname.lastname'
SELECT SUBSTRING(@MyDomainName,CHARINDEX('\',@MyDomainName)+1,128)
SET @MyDomainName = 'DOMAIN\firstname.lastname'
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2008 at 10:00 am
p.s.
I don't know what the code is actually trying to do nor why you feel you need dynamic SQL to do it, but if you break all the lines just...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2008 at 9:29 am
Issam,
Are you simply trying to slice a given number into slices containing 3 digits each?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 25, 2008 at 9:09 am
Viewing 15 posts - 50,296 through 50,310 (of 59,091 total)