Viewing 15 posts - 241 through 255 (of 2,436 total)
Please try sending a test email via the GUI and post the screen shot of the error.
Also, try sending a test email via the query window and post the ewrror...
August 18, 2009 at 8:13 am
I believe that 'Database 2' is tempdb.
Try stopping and restarting SQL Server.
August 14, 2009 at 11:08 am
How about one more solution:
use master
go
select createdate as 'Sql Server Installation Date'
from sys.syslogins
where sid = 0x010100000000000512000000 -- language neutral for NT AUTHORITY\SYSTEM
go
August 12, 2009 at 9:28 am
try this:
stop the SQL Agent
execute the following query:
alter database msdb set enable_broker
restart the SQL Agent
Even though the Service Broker may not be installed I have found...
August 11, 2009 at 11:04 am
I can replicate it. I have attached the screen shot as well.
August 11, 2009 at 8:39 am
Also ...
Our database backup throughput to local or SAN disk is about 1 Gb/Minute.
Our network database backups average about 500 Mb/Minute.
August 10, 2009 at 9:14 am
I really think that your network has issues ...
We toss around Terrabytes of data fairly regularly.
Our network throughput in copy these 200-500 Gb backup files ranges anywhere from 375 Mb/Minute...
August 10, 2009 at 9:11 am
It seems to be more of a case of avoiding 'planned downtime' in order to increase 'availability' while at the same time increasing the possibility and length of 'unplanned downtime'....
August 4, 2009 at 11:37 am
Please take Ed's advice ... the money you will spend on experienced consultants with the knowledge-base you need will be paltry (50-100k) compared to the millions your servers, SAN storage...
July 30, 2009 at 12:17 pm
I am going to guess that you are installing from a network share.
If this is the case copy the installation media to local disk and try it again.
July 27, 2009 at 2:25 pm
Interesting - I had the chance to work with a few Exchange ROSS and SQL ROSS engineers over the last decade at various stops in my career. It seemed that...
July 22, 2009 at 3:29 pm
Since this is a maintenance plan try querying the msdb maintenance history table:
select * from msdb..sysdbmaintplan_history
where plan_name = 'your_plan_name'
I have found that this table sometimes has better info than the...
July 22, 2009 at 11:32 am
It sounds like Gordon Bell is doing exactly what he and MS want - sometyhing 'fun' and definitely outside of the box. My hat is off to him and MS...
July 22, 2009 at 10:28 am
It took google and wikipedia 60 seconds to provide the answer for me.
At first I thought what in the world does this have to do with SQL - then started...
July 22, 2009 at 8:17 am
Viewing 15 posts - 241 through 255 (of 2,436 total)