database mirroring question

Is Asynchronous database mirroring support in the Standard Edition of
SQL 2005?
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JD
JoeyD
If I remember well, database mirroring is supported only on Enterprise
Edition
"JoeyD" <joeydba@.gmail.com> wrote in message
news:1168635799.710707.324810@.51g2000cwl.googlegro ups.com...
> Is Asynchronous database mirroring support in the Standard Edition of
> SQL 2005?
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>
|||Synchronous mirroring is supported on Standard and Enterprise editions.
Asynchronous mode is only supported on Enterprise edition.
Paul Randal
Principal Lead Program Manager
Core Storage Engine, Microsoft SQL Server Team
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uh6Amz7NHHA.3916@.TK2MSFTNGP02.phx.gbl...
> JoeyD
> If I remember well, database mirroring is supported only on Enterprise
> Edition
>
> "JoeyD" <joeydba@.gmail.com> wrote in message
> news:1168635799.710707.324810@.51g2000cwl.googlegro ups.com...
>
|||Thanks Paul for the reply. I've done some more testing on my own and
have found this to be true. Not sure what my manager had heard or where
he had heard it.
Joe
Paul S. Randal [MS] wrote:[vbcol=seagreen]
> Synchronous mirroring is supported on Standard and Enterprise editions.
> Asynchronous mode is only supported on Enterprise edition.
> --
> Paul Randal
> Principal Lead Program Manager
> Core Storage Engine, Microsoft SQL Server Team
> http://blogs.msdn.com/sqlserverstorageengine/default.aspx
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:uh6Amz7NHHA.3916@.TK2MSFTNGP02.phx.gbl...

Database Mirroring

I'd like to verify that to use Asynchronous database mirroring is NOT
support for Standard Edition.
I've read some docs that say it isn't. However, my manager saids that
he was told it was (or would work), something about 'single stream'? I
have not been able to find any docs that talks about 'single stream'.
Can anyone advise or point me in the right direction?
thanks all,
JD
Standard Edition Database Mirroring is supported as follows:
Single REDO thread and the safety setting is always on.
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
"JoeyD" wrote:

> I'd like to verify that to use Asynchronous database mirroring is NOT
> support for Standard Edition.
> I've read some docs that say it isn't. However, my manager saids that
> he was told it was (or would work), something about 'single stream'? I
> have not been able to find any docs that talks about 'single stream'.
> Can anyone advise or point me in the right direction?
> thanks all,
> JD
>
sql

Database Maintenance Plan

Hi,
Please tell me why isn't it possible to switch in one maintenance plan
Reorganize data and index pages and Update the statistics used by the query
optimizer?
May be reorganizing data and indexes also updates statistics? but if yes,
updates it all statistics or only some of them?
Thanks
I am not sure if I understand your question 100% but when you reindex with
the maintenance plan it issues a DBCC DBREINDEX. That command updates the
statistics automatically for you.
Andrew J. Kelly SQL MVP
"Przemo" <Przemo@.discussions.microsoft.com> wrote in message
news:7164A315-4775-4D80-BE09-0C06EE5112E5@.microsoft.com...
> Hi,
> Please tell me why isn't it possible to switch in one maintenance plan
> Reorganize data and index pages and Update the statistics used by the
> query
> optimizer?
> May be reorganizing data and indexes also updates statistics? but if yes,
> updates it all statistics or only some of them?
> Thanks

database mail isn't working in the SQL Agent job notification

Hi,

Starting a few weeks ago I stopped receiving notifications when SQL Server Agent Jobs failed. The only error I see from the Error logs is the following: "[264] An attempt was made to send an email when no email session has been established"

I've followed all of the postings about stoping and restarting the Agent service, confirming that the database mail can send out test emails and making sure that database mail account name matches the actual SMTP account.

From my testing, I can successfully send out a test email by right-clicking on "Database Mail" - "Send Test E-Mail."

Here's my setup:
Active/Passive SQL Server 2005 Cluster.
32 bit
SS2005 SP1 installed

Database Mail worked for around 6 months and then stopped. Not sure if it's a permissions issue, patch issue or a configuration issue.

Any help resolving this would be great.

Sincerely,

Steve

Ditto for me. Standard SQL 2005 setup. Engine, AS, Integration, etc. with SP1. I've done all the troubleshooting steps detailed here because this was the closest related issue I found on the Web.
The stored proc sp_send_dbmail works. So I can craft a workaround.

I found the same issue posted under Technet here. Any ideas?

|||

Well this is a slap in the face.

My manager suggested I do a restart of the SQL Server Agent. I had tried that before but since he is the boss I did it again expecting the same results. Well as you might have guessed - its working. And not just on the development server but the production too. Can't figure it.

|||

Restarting has become my habit in debugging now thanks to this

"Restart" has been mentioned in couple threads though if you searched by your error message here (or Google)

It's really weird, SQL Mail stopped working randomly IMO, thank god this doesn't happen to SQL Server

|||

Steve,

I've seen this from time-to-time on our servers, as well. After a restart of SQL Server Agent, database mail will usually run fine for a month and then the error will come back again. It is frustrating especially when it happens on production boxes with replication, but at least it doesn't require a server reboot like SQL Mail always did when it locked up.