Viewing 15 posts - 48,406 through 48,420 (of 59,095 total)
keywestfl9 (9/8/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2008 at 7:18 pm
rg (9/8/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2008 at 7:11 pm
Thanks, Gaby... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2008 at 7:05 pm
I haven't used DiskKeeper in 10 years, but the folks at work swear by it. Your SysAdmin probably did a great job insisting that it be installed.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2008 at 7:01 pm
It'[s pretty simple with Bulk Insert and a BCP format file. Take a look in Books Online. If your were to provide the first 100 lines of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 5:31 pm
talentguy123 (9/7/2008)
Create a SP to and schedule it as a job, I use this and works very fast..
That works great, but if you go back to the very first post,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 5:25 pm
If you read the table using WITH (NOLOCK), you will be able to see the progress of the updates. Of course, that requires a separate parallel process.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 5:22 pm
raym (9/7/2008)
The tables have been reduced in size and I have listed the new tables. Can Bcp work on these ?
Heh... sure... we've already established that it could... you still...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 3:36 pm
Yep... that'll work... just as soon as you identify what you want to order by, like I said.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 12:17 pm
Joseph (9/5/2008)
can any one tell me how can we run a long script or query in smaller batches. sometimes I hear my boss telling to developer...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 11:23 am
You MUST change the defaults for TempDB or you'll end up having 73 fragments by the time it grows to 1GB.
I normally start out a new system with 1000MB allocated...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 11:16 am
sandhyarao49 (9/6/2008)
Hi Folks,I have a small doubt.
suppose in a table there are 100 rows.
I want to retrieve only 40 th row.Could any one help me out.
Thanks,
Sandhya
Just how do you identify...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 11:07 am
It would be easier to simply delete the hacked rows and insert the repaired rows. If the ID column is important for identification of the row, you can use...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 11:02 am
p.s.
We have some fairly large systems... in my last job, we booted TempDB at 9GB and in my current job, we boot it at 6GB. TempDB is an important...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 10:49 am
The default settings for TempDB are to start at 1MB with 10% growth. If you do the math, it'll take 73 growths to get to 1GB... 73 growths also...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2008 at 10:40 am
Viewing 15 posts - 48,406 through 48,420 (of 59,095 total)