Viewing 15 posts - 8,806 through 8,820 (of 9,253 total)
choose the correct recovery model for your database and backup accordingly
October 27, 2008 at 11:20 am
dont forget to run dbcc updateusage against each database and rebuild the indexes too
October 27, 2008 at 11:17 am
GilaMonster (10/26/2008)
There's no direct way to query the filesystem.
i would say this is best done through the web pages code
October 26, 2008 at 12:32 pm
memory support in the main, 64 bit has better support for larger memory configs
October 26, 2008 at 12:21 pm
fivetenmm (10/24/2008)
October 26, 2008 at 9:01 am
victor_bosc (10/23/2008)
And, what do you think about only rebuilding indexes once a week?
that is the strategy i employ
October 26, 2008 at 5:13 am
for the SQL2005 box leave IP1, Ip2, IP3 unset. Configure IP All with the port number and leave dynamic blank. Restart the instance
October 24, 2008 at 10:08 am
have you imported the package to the file system or package store on the server
October 24, 2008 at 10:03 am
Roger Abram (10/22/2008)
October 24, 2008 at 5:40 am
victor_bosc (10/22/2008)
The problem is that the optimization job increases too much the log file,
set the recovery mode to bulk logged before the index rebuild and then back to full...
October 23, 2008 at 2:39 pm
check the file and directory exists, if it does exist check the permissions on them 😉
October 23, 2008 at 12:50 pm
check for any 3rd party apps, i have seen something similar to this before
October 23, 2008 at 12:47 pm
Viewing 15 posts - 8,806 through 8,820 (of 9,253 total)