Viewing 15 posts - 35,971 through 35,985 (of 59,102 total)
Looks like the stress you were talking about caught up with you, Jack. I've actually been through that a couple of times including the trips to the hospital. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 7:58 pm
Alvin Ramard (11/22/2010)
Brandie Tarvin (11/22/2010)
CirquedeSQLeil (11/22/2010)
Alvin Ramard (11/22/2010)
Brandie Tarvin (11/22/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 7:46 pm
WayneS (11/22/2010)
Jeff Moden (11/22/2010)
I just don't ever want to be that "productive". Down-time is very important to me.
Yes, but I refer back to what Steve posted above:
If a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 7:35 pm
Grant Fritchey (11/22/2010)
Jeff Moden (11/22/2010)
I just don't ever want to be that "productive". Down-time is very important to me.What is this "down-time" of which you speak?
Heh... yeah... I know...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 7:29 pm
I just don't ever want to be that "productive". Down-time is very important to me.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 3:15 pm
I guess my question would be, what are you doing where you'd ever need almost a T-Byte of TempDB? What's the total MDF/LDF size for that server?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 3:14 pm
kevin4u06 (11/22/2010)
There is one more added complexity , in some recordds the state has for exampleArizona
New Jersy
instead of just their abbreviation
Build a table of long names and short names and...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 3:09 pm
GSquared (11/22/2010)
churlbut (11/22/2010)
DROP TABLE #Temp
DECLARE @X int
SET @X = 1
CREATE TABLE #Temp (Phone varchar(17) null)
WHILE @X < 101
BEGIN
INSERT INTO #Temp(Phone) select Phone from People...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 2:00 pm
Sachin Nandanwar (11/22/2010)
Jeff Moden (11/22/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 7:57 am
Sachin Nandanwar (11/22/2010)
keymoo (11/22/2010)
Thanks it doesn't give me the correct results for dates that are the same. Is there a tweak needed to do that?
Please post some sample data and...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 7:53 am
Eralper (11/22/2010)
I checked the BOL and I found :
The amount of logging for SELECT...INTO depends on the recovery model in effect for the database. Under the simple recovery model...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 6:10 am
S_Kumar_S (11/22/2010)
So it concludes that there is no simple work around expect if I can find...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 6:03 am
Heh... yes... ask an "SQL Server DBA". 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 1:01 am
You can get around some of the logging issues by using a SELECT/INTO to copy only the rows you want to keep and then renaming the table(s). Read up...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 12:49 am
Sachin Nandanwar (11/17/2010)
dlam 18073 (11/16/2010)
I dont get it. clientNumber in tblClientList is primary key.can you tell me abit more in detail. thx!!
Then why are you checking whether the clientNumber exists?If...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2010 at 12:43 am
Viewing 15 posts - 35,971 through 35,985 (of 59,102 total)