Certificate creation problem

Hello to all

I have two SQL 2005 server and I want to start mirroring a database.
Since there's no windows domain I'm trying to use certificates to grant connection between servers.

At this point I find some difficulties...

I've read on MSDN that 'active FOR begin_dialog = ON' option must be specified; look at the code below, when I execute I get following error:

Msg 156, Level 15, State 1, Line 8

Incorrect syntax near the keyword 'FOR'.

CREATE CERTIFICATE Polx

WITH SUBJECT = 'Mirror certificate',

START_DATE = '10/31/2001',

EXPIRY_DATE = '10/31/2009',

active FOR begin_dialog = ON;

GO

CREATE SYMMETRIC KEY Key1

WITH ALGORITHM = RC4

ENCRYPTION BY CERTIFICATE Polx

GO

Any suggestion will be really appreciated!!!

By the way, do I have to create same certificate on the mirror server after creating it on the master?

Thanks, Carlo

You should try removing the comma before the ACTIVE keyword. From my experience with database mirroring, however, I don't remember this clause being required. The certificate used for mirroring needs to exist on both the principal and the mirror.

Thanks
Laurentiu|||

Here's some additional information about setting up database mirroring. I hope this will help:

http://blogs.msdn.com/lcris/archive/2005/09/14/466268.aspx

Thanks
Laurentiu

caveats for synchronous hardware based replication?

Hello,
Thinking about synchronous hardware based mirroring using EMCs clariion
product line over a dedicated fiber connection between two geographically
separate data centers. I realize that there is a basic speed of light issue
here regarding the distance I can have between the two sites and still keep
my servers synched real-time.
Would someone please shed some more light on what is involved here? What's
the maximum distance I can have betwen these sites and why? Any other
caveats with this setup I should be aware of? Thanks.
BTW - running an OLTP environment SQL2000.
I don't believe that these solutions are truly synchronous, and second its
way slower than the speed of light.
The most significant factors are price and skill set required. If you think
replication is tough wait till you get behind EMC's SRDF.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mb" <mb@.discussions.microsoft.com> wrote in message
news:8AB9A09B-325B-4A59-9C54-1CC65BD1348B@.microsoft.com...
> Hello,
> Thinking about synchronous hardware based mirroring using EMCs clariion
> product line over a dedicated fiber connection between two geographically
> separate data centers. I realize that there is a basic speed of light
issue
> here regarding the distance I can have between the two sites and still
keep
> my servers synched real-time.
> Would someone please shed some more light on what is involved here?
What's
> the maximum distance I can have betwen these sites and why? Any other
> caveats with this setup I should be aware of? Thanks.
> BTW - running an OLTP environment SQL2000.
|||I'm curious why you state the hardware mirroring is not truly synchronous?
It was my understanding that if distances were kept under a certain limit
then this solution could be considered to be essentially synchronous.
Oh, just got your replication book Hilary - great read!
"Hilary Cotter" wrote:

> I don't believe that these solutions are truly synchronous, and second its
> way slower than the speed of light.
> The most significant factors are price and skill set required. If you think
> replication is tough wait till you get behind EMC's SRDF.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "mb" <mb@.discussions.microsoft.com> wrote in message
> news:8AB9A09B-325B-4A59-9C54-1CC65BD1348B@.microsoft.com...
> issue
> keep
> What's
>
>
|||My understanding from EMC is that there are two modes. 1) Synchronous and 2)
asynchronous.
In the Synchronous mode, data is written to the source and the app receives
the commit. Then under the covers the write is written to the destination.
So, its not a true split write. Asynchronous has queuing built in.
Let me check with my EMC rep and confirm this.
Glad you like the book!
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mb" <mb@.discussions.microsoft.com> wrote in message
news:1910F129-8553-42BA-BD15-8B8517D9BC0B@.microsoft.com...[vbcol=seagreen]
> I'm curious why you state the hardware mirroring is not truly synchronous?
> It was my understanding that if distances were kept under a certain limit
> then this solution could be considered to be essentially synchronous.
> Oh, just got your replication book Hilary - great read!
> "Hilary Cotter" wrote:
its[vbcol=seagreen]
think[vbcol=seagreen]
clariion[vbcol=seagreen]
geographically[vbcol=seagreen]