Active/Active Cluster.

Hi everyone,
We have the following setup:
Windows 2003 Server Enterprise edition Cluster with 2 nodes. SQL Server 2000
Enterprise edition Virtual Server1 - currently Active/Passive Cluster.
Shared storage and Quorum drive on SAN.
Database1 on Virtual Server1.
The goal is to set up a reports Database wich will server as a mirror(but
not exact mirror, because it will keep archive data as well) for Database1.
Currently we consider the following proposition:
We want to set up another database(Database2). Our Application will be
writing the same data to both Database1 and Database2(not necessarily at the
same time).
As data gets out of date it will be removed from Database1(but not from
Database2). Database2 is intended to be used for reports(intensive queries).
Would it be a good solution to set up an Active/Active Cluster(another
Virtual Server with the Active/Passive nodes swapped).
If yes, could you provide detailed information(or references/URLs to it)
regarding the implementation - what needs to be done and what are the steps
to follow.
If no, could you propose alternative solutions.
Best Regards.
Sezgin Rafed
I am not sure I have even to go on, no memory requirements, usage hours,
etc. You can indeed create another instance and run it on the current node
or the second node. You can also add a 3 node since you are running on
Windows Server 2003.
With that said, unless unavoidable, I like to stay away running instances on
each node. I like to have a spare at all times.
The setup steps are the same as the default node, except you have to name
the instance.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Sezgin Rafed" <anonymous@.anonymous.com> wrote in message
news:%23ia3zHl6EHA.1204@.TK2MSFTNGP10.phx.gbl...
> Hi everyone,
> We have the following setup:
> Windows 2003 Server Enterprise edition Cluster with 2 nodes. SQL Server
> 2000
> Enterprise edition Virtual Server1 - currently Active/Passive Cluster.
> Shared storage and Quorum drive on SAN.
> Database1 on Virtual Server1.
> The goal is to set up a reports Database wich will server as a mirror(but
> not exact mirror, because it will keep archive data as well) for
> Database1.
> Currently we consider the following proposition:
> We want to set up another database(Database2). Our Application will be
> writing the same data to both Database1 and Database2(not necessarily at
> the
> same time).
> As data gets out of date it will be removed from Database1(but not from
> Database2). Database2 is intended to be used for reports(intensive
> queries).
> Would it be a good solution to set up an Active/Active Cluster(another
> Virtual Server with the Active/Passive nodes swapped).
> If yes, could you provide detailed information(or references/URLs to it)
> regarding the implementation - what needs to be done and what are the
> steps
> to follow.
> If no, could you propose alternative solutions.
> Best Regards.
> Sezgin Rafed
>
sql

Active Directory authorization in RS Standard Edition

It is possible ?
Users connect to database with report data using own Active Directory
domain credentials (not ASPNET account) and users not must write login
and password (login credentials must be send automatic by IE)Bartosz Gorzynski <bartosz.gorzynski@.zapolex.pl> wrote in message news:<#T2XaQU0EHA.3808@.tk2msftngp13.phx.gbl>...
> It is possible ?
> Users connect to database with report data using own Active Directory
> domain credentials (not ASPNET account) and users not must write login
> and password (login credentials must be send automatic by IE)
By changing your securty within ASP.NET to Windows, rather than forms
and then invoking impersonation you should be able to accomplish this.
Samples for this are available at gotdotnet.
Good luck
Cos

Activating Trial Edition of SQL Server 2005

I have the following situation.
I installed a couple of months ago SQL Server 2005 Trial Edition which is En
teprise Edition I guess.
Currently I am testing replication on our company database.
Now. In a few months the Trial Version will expire.
Can I avoid setting up my Merge Replication again and re-installing everythi
ng from scratch?
Is there a way to activate NOT YET expired trial version ?
More to that I prefer to purchase the Standard Ed. which is less expensive t
han Enterprise.
Can I convert somehow the Trial Enteprise ed. into Standard WITHOUT having t
o re-install everything and possibly losing oall my settings.Issue a select @.@.version to determine what you are running. I think your
best bet is to script our your publications and subscribers, and then to
detacth the databases. Remove the trial version and install standard noting
that web synchronization and other features of merge replication present
only in EE will not be available.
Then run the publication and subscription scripts on the new server.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Yuri" <Yuri@.tester.de> wrote in message
news:5o-dnaz5Doik2dvYnZ2dnUVZ8qKdnZ2d@.giganews.com...
>I have the following situation.
> I installed a couple of months ago SQL Server 2005 Trial Edition which is
> Enteprise Edition I guess.
> Currently I am testing replication on our company database.
> Now. In a few months the Trial Version will expire.
>
> Can I avoid setting up my Merge Replication again and re-installing
> everything from scratch?
> Is there a way to activate NOT YET expired trial version ?
> More to that I prefer to purchase the Standard Ed. which is less expensive
> than Enterprise.
> Can I convert somehow the Trial Enteprise ed. into Standard WITHOUT having
> to re-install everything and possibly losing oall my settings.|||Hi Hillary,
thanks for your piece of advice.
This is actually a workaround solution.
Your are right, installing the Standard ed. over Trial Version isn't probabl
y the best idea.
But I guess you are mistaken saying that SE has no Web Merge Replication fea
utures
Look at this table: http://www.microsoft.com/sql/prodin...
es.mspx
Yuri

Activating Trial Edition of SQL Server 2005

I have the following situation.
I installed a couple of months ago SQL Server 2005 Trial Edition which is Enteprise Edition I guess.
Currently I am testing replication on our company database.
Now. In a few months the Trial Version will expire.
Can I avoid setting up my Merge Replication again and re-installing everything from scratch?
Is there a way to activate NOT YET expired trial version ?
More to that I prefer to purchase the Standard Ed. which is less expensive than Enterprise.
Can I convert somehow the Trial Enteprise ed. into Standard WITHOUT having to re-install everything and possibly losing oall my settings.Issue a select @.@.version to determine what you are running. I think your
best bet is to script our your publications and subscribers, and then to
detacth the databases. Remove the trial version and install standard noting
that web synchronization and other features of merge replication present
only in EE will not be available.
Then run the publication and subscription scripts on the new server.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Yuri" <Yuri@.tester.de> wrote in message
news:5o-dnaz5Doik2dvYnZ2dnUVZ8qKdnZ2d@.giganews.com...
>I have the following situation.
> I installed a couple of months ago SQL Server 2005 Trial Edition which is
> Enteprise Edition I guess.
> Currently I am testing replication on our company database.
> Now. In a few months the Trial Version will expire.
>
> Can I avoid setting up my Merge Replication again and re-installing
> everything from scratch?
> Is there a way to activate NOT YET expired trial version ?
> More to that I prefer to purchase the Standard Ed. which is less expensive
> than Enterprise.
> Can I convert somehow the Trial Enteprise ed. into Standard WITHOUT having
> to re-install everything and possibly losing oall my settings.

AccessViolationException and NativeException

Hello,

I'm developing a multithreading application in C# with Compact
Framework 2.0 and Sql Server 2005 Compact Edition. Sometimes and
randomly, the following exception is thrown :

AccessViolationException in System.Data.SqlServerCe.NativeMethod()...

Why ?

Thank you, very much.

What activity triggers the access violation?|||

Yesterday I have solved the problem. There were some DataReader unclosed.

Thank you.

Accessing SQL2005 as a Second Instance to SQL2000

I'm having trouble accessing SQL2005 Standard Edition as a second
instance of SQL Server where the first instance is SQL 2000 Enterprise
Edition. I installed SQL 2005 as a named instance "SQL2005". The
server is running Windows 2000 SP4 ON A 32-Bit machine. When I look in
Services I see the SQL Server (SQL2005), SQL Server Agent (SQL2005)
services there. I went into SQL Server Configuration manager and
disabled the named pipes protocol and only have TCP/IP and by default
Shared Memory enabled to rule out that named pipes is causing the
problem. In SQL Server Configuration Manager I created an alias
"computername$SQL2005" and was able to connect to database engine
"computername\SQL2005" through SQL Server Management Studio WHILE ON
THAT BOX.
But when trying to access the 2005 instance from another server
(64-bit Windows 2003 SP1) I'm having trouble. On the 64-bit machine I
disabled the named pipes protocol for both "SQL Native Client
Configuration (32-bit)" and "SQL Native Client Configuration". Under
32-bit I created the alias "machinename$SQL2005" to point to the IP
address of the 32-bit machine. In SQL Server Management Studio when
trying to connect to the database engine "machinename$SQL2005" it
defaults to the SQL 2000 instance. How do I access the SQL2005
instance from a remote server?

Any help would be appreciated.

MikeThis question seems to crop up a lot; I'm surprised that Microsoft
didn't make a bigger deal about it. By default, SQL Server 2005 does
not allow remote access; you have to turn it on.

Use the Surface Area Configuration tool for SQL Server 2005; under
database engine, select Remote Connections and make sure that local and
remote connections are selected.

HTH,
Stu

Mike wrote:

Quote:

Originally Posted by

I'm having trouble accessing SQL2005 Standard Edition as a second
instance of SQL Server where the first instance is SQL 2000 Enterprise
Edition. I installed SQL 2005 as a named instance "SQL2005". The
server is running Windows 2000 SP4 ON A 32-Bit machine. When I look in
Services I see the SQL Server (SQL2005), SQL Server Agent (SQL2005)
services there. I went into SQL Server Configuration manager and
disabled the named pipes protocol and only have TCP/IP and by default
Shared Memory enabled to rule out that named pipes is causing the
problem. In SQL Server Configuration Manager I created an alias
"computername$SQL2005" and was able to connect to database engine
"computername\SQL2005" through SQL Server Management Studio WHILE ON
THAT BOX.
But when trying to access the 2005 instance from another server
(64-bit Windows 2003 SP1) I'm having trouble. On the 64-bit machine I
disabled the named pipes protocol for both "SQL Native Client
Configuration (32-bit)" and "SQL Native Client Configuration". Under
32-bit I created the alias "machinename$SQL2005" to point to the IP
address of the 32-bit machine. In SQL Server Management Studio when
trying to connect to the database engine "machinename$SQL2005" it
defaults to the SQL 2000 instance. How do I access the SQL2005
instance from a remote server?
>
Any help would be appreciated.
>
Mike

|||Thanks for your response Stu, After checking SQL Server 2005 Surface
Area Configuration it looks like the option for "Local and Remote
Connections" was already selected. I checked under "Database Engine"
under both "View by Instance" and "View by Component" and it seems the
same. I even clicked on "Local connections only" then back to "Local
and Remote Connections" just to make sure the setting was recognized
when hitting "Apply". Then restarted SQL Server (2005) service. Still
unable to access this instance from the other server. Do I need to use
another tcp/ip port for the second instance? I remember reading this
somewhere, but when I tried to use port 1435 because UDP port 1434 is
supposedly disabled in SQL 2005, I still cannot connect.

When I try connecting remotely I'm still getting the SQL 2000 instance.
Any other ideas?

Thanks,

Mike

Stu wrote:

Quote:

Originally Posted by

This question seems to crop up a lot; I'm surprised that Microsoft
didn't make a bigger deal about it. By default, SQL Server 2005 does
not allow remote access; you have to turn it on.
>
Use the Surface Area Configuration tool for SQL Server 2005; under
database engine, select Remote Connections and make sure that local and
remote connections are selected.
>
HTH,
Stu
>
Mike wrote:

Quote:

Originally Posted by

I'm having trouble accessing SQL2005 Standard Edition as a second
instance of SQL Server where the first instance is SQL 2000 Enterprise
Edition. I installed SQL 2005 as a named instance "SQL2005". The
server is running Windows 2000 SP4 ON A 32-Bit machine. When I look in
Services I see the SQL Server (SQL2005), SQL Server Agent (SQL2005)
services there. I went into SQL Server Configuration manager and
disabled the named pipes protocol and only have TCP/IP and by default
Shared Memory enabled to rule out that named pipes is causing the
problem. In SQL Server Configuration Manager I created an alias
"computername$SQL2005" and was able to connect to database engine
"computername\SQL2005" through SQL Server Management Studio WHILE ON
THAT BOX.
But when trying to access the 2005 instance from another server
(64-bit Windows 2003 SP1) I'm having trouble. On the 64-bit machine I
disabled the named pipes protocol for both "SQL Native Client
Configuration (32-bit)" and "SQL Native Client Configuration". Under
32-bit I created the alias "machinename$SQL2005" to point to the IP
address of the 32-bit machine. In SQL Server Management Studio when
trying to connect to the database engine "machinename$SQL2005" it
defaults to the SQL 2000 instance. How do I access the SQL2005
instance from a remote server?

Any help would be appreciated.

Mike

|||Mike (mjorlando@.campsystems.com) writes:

Quote:

Originally Posted by

Thanks for your response Stu, After checking SQL Server 2005 Surface
Area Configuration it looks like the option for "Local and Remote
Connections" was already selected. I checked under "Database Engine"
under both "View by Instance" and "View by Component" and it seems the
same. I even clicked on "Local connections only" then back to "Local
and Remote Connections" just to make sure the setting was recognized
when hitting "Apply". Then restarted SQL Server (2005) service. Still
unable to access this instance from the other server. Do I need to use
another tcp/ip port for the second instance? I remember reading this
somewhere, but when I tried to use port 1435 because UDP port 1434 is
supposedly disabled in SQL 2005, I still cannot connect.

Have you checked that the SQL Browser service is running? You control it
from the SQL Configuration Management tool.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Yes, the SQL Browser service is running. I restarted it just to make
sure. Has there been updates to BOL since May 2006? That is the date
of my SQL 2005 installation. I will download the latest, thanks,
Mike
Erland Sommarskog wrote:

Quote:

Originally Posted by

Mike (mjorlando@.campsystems.com) writes:

Quote:

Originally Posted by

Thanks for your response Stu, After checking SQL Server 2005 Surface
Area Configuration it looks like the option for "Local and Remote
Connections" was already selected. I checked under "Database Engine"
under both "View by Instance" and "View by Component" and it seems the
same. I even clicked on "Local connections only" then back to "Local
and Remote Connections" just to make sure the setting was recognized
when hitting "Apply". Then restarted SQL Server (2005) service. Still
unable to access this instance from the other server. Do I need to use
another tcp/ip port for the second instance? I remember reading this
somewhere, but when I tried to use port 1435 because UDP port 1434 is
supposedly disabled in SQL 2005, I still cannot connect.

>
Have you checked that the SQL Browser service is running? You control it
from the SQL Configuration Management tool.
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

|||Mike (mjorlando@.campsystems.com) writes:

Quote:

Originally Posted by

Yes, the SQL Browser service is running. I restarted it just to make
sure. Has there been updates to BOL since May 2006? That is the date
of my SQL 2005 installation. I will download the latest, thanks,

Yes, there is a new version. (They come out once a quarter.) URL below.

I went back to your original post, and it appears that you have defined
alias which points to the IP Address on the machine with SQL 2000 and
SQL 2005 on. But it is not clear that you specifiec the instance name
in the alias definition. If you only use the IP address you will end up
at the default instance, which I understand is running SQL 2000.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

accessing SQL Server Compact Edition from VBA

Is it possible to connect to SQL Server Compact Edition with Visual Basic for Application?

I want to connect to *.sdf file from MS Access.

I suppose you can do it using OLEDB if VBA allows you to use COM objects (which you should know better as I've never used VBA).

|||

Thanks. I also suspected that, just was not sure is there OLEDB provider version for desktops, and how to access it. Just foud that information in one of the mahdi posts

Dim cnx As ADODB.Connection
Set cnx = New ADODB.Connection
cnx.ConnectionString = "Provider='Microsoft.SQLSERVER.MOBILE.OLEDB.3.0.';Data Source='c:\\B.sdf';"
cnx.Open

Accessing SQL Server 2005 Express

I recently downloaded SQL Server 2005 Express Edition. Everything was installed correctly without any problems. However, when I went to my Program list, the only thing listed for Microsoft SQL Server 2005, was Configuration tool.

Where is the actual program where I can write and run queries? How do I access the server?I think that the 'default' installation only installs SQL Server. If you want the client tools, you will need to insert the media again and select Client Tools (or something like that...)|||The Express SKU does not include the client tools you are referring to. If you want to install these, you need to download Express Advanced and add Management Studio Express. This will give you the UI-based client tools you are looking for.

Thanks,
Sam Lester (MSFT)

Accessing SQL Database created in Visual Studio

I created an SQL database in Visual Studio 2005 Express Edition and would like to edit it in SQL Server Management Studio Express. The only databases listed in the Object Explorer of SQL Server MSE are the system databases (ones that are part of the SQL Server MSE).

If I dig through the directories, I can locate my database under the Visual Studio directory, but I am unable to open it. I get an error message stating, "There is no editor available for [my database]... Make sure the application for the file type (.mdf) is installed."

I'm sure that this is a ridiculously simple rookie mistake that I'm committing somehow, but I'm stumped. Any idea what I'm doing wrong?

What you need to do is "attach" your database in your management studio. This is supprisingly a goofy process, being that this is our newest implementation of a manager for SQL Express, here's some help to get you started.

http://msdn2.microsoft.com/en-us/library/ms190209.aspx

|||

I tried it, and I think that it should have worked, but it didn't. I got a long string of error messages. It's probably just another bug that Microsoft will some day issue a patch for. When I attempted to add my review of the tip to the msdn website my computer locked up. That was kind of a metaphor for the entire experience. I've learned my lesson. Don't make databases in Visual Studio - do it in SQL Studio or MySQL.

|||

I've never had an issue with the Management Studio, or SQL Express databases, I'm not sure what your experiencing, but they arent as unreliable as your making them out to be.

Sorry you couldnt get it fixed.

Accessing remote SQL 2005 db using C# express edition

I have downloaded Visual C# express edition and SQL Server 2005 Express
Edition.
Installed Visual C# Express and SQL Server Express edition on Windows XP Sp2
and .NET framework 2.0
I am trying to write a C# program using ADO.NET to access a SQL 2000
database stored on a remote server Windows 2003 Sp1.
User logged in on this XP machine does not have rights on Windows 2003 serve
r.
Getting some kind of errors that login failed. And if I use user name and
password while connecting to SQL 2000 database getting some different errors
.
My questions are:
1. Is it possible with Visual C# express edition to access remote server SQL
db?
or do I need to use local database?
2. Is it possible to import SQL 2000 datbase in SQL 2005 Express edition?
Please advise.
Thanks in advance.Hi
1. If you are using windows authentication then there will need to be a
trust between the server and workstation if they are not on the same domain.
If you have mixed mode authentication then you may be able to use a SQL
Server login. Try connecting with osql first.
2. You can backup/restore from SQL 2000 to SQL 2005.
John
"SPD" wrote:

> I have downloaded Visual C# express edition and SQL Server 2005 Express
> Edition.
> Installed Visual C# Express and SQL Server Express edition on Windows XP S
p2
> and .NET framework 2.0
> I am trying to write a C# program using ADO.NET to access a SQL 2000
> database stored on a remote server Windows 2003 Sp1.
> User logged in on this XP machine does not have rights on Windows 2003 ser
ver.
> Getting some kind of errors that login failed. And if I use user name and
> password while connecting to SQL 2000 database getting some different erro
rs.
> My questions are:
> 1. Is it possible with Visual C# express edition to access remote server S
QL
> db?
> or do I need to use local database?
> 2. Is it possible to import SQL 2000 datbase in SQL 2005 Express edition?
> Please advise.
> Thanks in advance.
>