Viewing 15 posts - 286 through 300 (of 1,536 total)
UAMCRay (11/4/2009)
November 5, 2009 at 10:04 am
If you have the admin access on the server you could just stop the services, copy the mdf's and move them somewhere else. I wouldn't worry so much about the...
November 4, 2009 at 3:55 pm
Enterprise only yeah, but you can drop a grand on a decent backup compression tool if you don't have the finances for EE and get something equally as good.
November 3, 2009 at 9:31 pm
I'd be less worried about the SLA and more about the ability to recover.
I've had really bad experiences with trials of these kinds of backups in the past and...
November 3, 2009 at 3:50 pm
Here's another one that you can try...
Stop all the SQL Services.
Change the SQL Service account to use the localsystem service
Create a batch file with the SQLCMD connection and the...
November 3, 2009 at 1:59 pm
A maxdop of 0 will indeed use all the CPU's, there can be issues where it takes more resources to manage the CPU's than you'll actually get from using them...
June 12, 2009 at 7:41 am
I'd also recommend changing up Windows 2003 to the x64 edition and installing the x64 version of SQL Server 2008
June 12, 2009 at 7:28 am
The Q drive is probably not mapped within the context of the SQL account.
You would be better served replacing the Q mapped drive with the regular UNC path.
June 5, 2009 at 7:25 am
hmmmm, I'm sorry Lynn, I didn't quite understand the link you provided.... :w00t:
June 4, 2009 at 11:13 am
Not applying SP1 on both nodes enables you the ability to go back should you run into a problem. It also minimizes the downtime for patching. Should you patch both...
June 2, 2009 at 9:08 pm
This is one of the awesome things that Microsoft has done with 2008, and really something that has been missing up until now.
The first thing is to download the service...
June 2, 2009 at 7:03 am
Unfortunately that appears to be the issue, yes.
Have you attempted further installs on the original dvd? If you get the same error there then you should work with whoever provided...
June 1, 2009 at 9:23 am
The default block size actually changes depending upon the size of the volume.
Leave the OS disk as is. SQL data and log files are not (I hope) on here. 64k...
May 31, 2009 at 12:21 pm
You mentioned copying the data to your hard drive can you confirm that it's the correct location for the install you are using D:\en_sql_server_2008_developer_x86_x64_ia64_dvd_x14-88839
Looks like the x86\setup100.exe might be...
May 31, 2009 at 12:03 pm
Viewing 15 posts - 286 through 300 (of 1,536 total)