Cluster setup question

Im viewing the Cluster setup instructions at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
_clustering_51rm.asp
But it doesnt say where to install SQL. It seems to me that if I wanted to
have an Active/ Passive Cluster I would need to intsall it on both boxes? Is
this correct? Are there better links I should be using?
--
SQL2K SP3
TIA, ChrisRYou begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>|||Well, that is close, but not quite accurate.
Even on a stand-alone installation, when you run the setup dialogue in
interactive mode, all that really happens is that a custom .iss file is
generated from your responses to the questions. Once all of the information
is gathered, setup then executes the setupsql with the newly created
setup.iss file as a parameter.
A cluster install is similar, except the setup.iss is deployed to both
nodes. During the installation, the cluster fails the disk over to each
node so that the individual setup.iss files can be ran against two
independently executed setupsql commands. This creates registry keys.
However, since the first install already created the directory structure,
deployed the binaries, installed the .sql scripts to master, model, and
msdb, this part of the process does not run again a second time. Just the
registry keys, performance counters, and client side tools. And, of course,
the MDAC, which is client side and IS NOT cluster aware.
Also, there is such a thing as the "Primary Node." This is nothing more
than the node from which you started the installation. It does not matter
which node you begin the installation on, as long as it is the node that
currently owns the disk resource you plan on installing SQL Server to.
However, it is important that you keep in mind which node this was.
This node will be the only one that maintains a record of the setup logs.
There is also special CLSIDs that only this node will contain that will not
propagate to the other. The nodes are close to the same configuration, BUT
NOT EXACT. This will be important in the future when you try to add
additional disk resources or swap out old disks for new, if you ever need to
modify or add an additional IP resource, or change the domain the cluster
belongs to. Keeping in mind which node was PRIMARY will only be to your
benefit.
Sincerely,
Anthony Thomas
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
You begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>|||I have had to change accounts and add/remove disk resources. As long as I
use the current owner node, everything works fine.
Yes, there are some subtle differences such as log files between nodes but
that is only relevant during installation failure troubleshooting. Once
everythign is running, there is no practical difference between nodes,
unlike SQL 7.0 clustering.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:OfrkU8e$EHA.1084@.tk2msftngp13.phx.gbl...
> Well, that is close, but not quite accurate.
> Even on a stand-alone installation, when you run the setup dialogue in
> interactive mode, all that really happens is that a custom .iss file is
> generated from your responses to the questions. Once all of the
information
> is gathered, setup then executes the setupsql with the newly created
> setup.iss file as a parameter.
> A cluster install is similar, except the setup.iss is deployed to both
> nodes. During the installation, the cluster fails the disk over to each
> node so that the individual setup.iss files can be ran against two
> independently executed setupsql commands. This creates registry keys.
> However, since the first install already created the directory structure,
> deployed the binaries, installed the .sql scripts to master, model, and
> msdb, this part of the process does not run again a second time. Just the
> registry keys, performance counters, and client side tools. And, of
course,
> the MDAC, which is client side and IS NOT cluster aware.
> Also, there is such a thing as the "Primary Node." This is nothing more
> than the node from which you started the installation. It does not matter
> which node you begin the installation on, as long as it is the node that
> currently owns the disk resource you plan on installing SQL Server to.
> However, it is important that you keep in mind which node this was.
> This node will be the only one that maintains a record of the setup logs.
> There is also special CLSIDs that only this node will contain that will
not
> propagate to the other. The nodes are close to the same configuration,
BUT
> NOT EXACT. This will be important in the future when you try to add
> additional disk resources or swap out old disks for new, if you ever need
to
> modify or add an additional IP resource, or change the domain the cluster
> belongs to. Keeping in mind which node was PRIMARY will only be to your
> benefit.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
> You begin the installation from the node that currently owns the disk
> resource you want SQL data files installed to. You can add additional
disk
> resources after the installation. The SQL installer adds code
automagically
> to the nodes you specify, provided they actually exist and are running at
> install time. You can add or remove nodes from the SQL installation later
> if you need to. Once SQL is installed, there is no difference between
> installed nodes except for which one is actually running SQL at a given
> moment.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "ChrisR" <bla@.noemail.com> wrote in message
> news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> > Im viewing the Cluster setup instructions at:
> >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> > _clustering_51rm.asp
> >
> > But it doesnt say where to install SQL. It seems to me that if I wanted
to
> > have an Active/ Passive Cluster I would need to intsall it on both
boxes?
> Is
> > this correct? Are there better links I should be using?
> >
> > --
> > SQL2K SP3
> >
> > TIA, ChrisR
> >
> >
>sqlsql

ClubSite template + sql server 2005 not cooperating...

I've managed to get the clubsite template from asp.net up and running, sorda (http://www.flysniper.com), I get a system error which I believe is related to the fact that my DB isn't working correctly.

I'm trying to configure it to work with ms sql server 2005 which is running on the same machine as the website.

I've followed the instructions of Scott Gu (http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx)

while trying to run aspnet_regsql.exe I get the following error

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regsql.exe -S XXXXXXXXXX
-U YYYYYYYY -P ZZZZZZZZZ -A all -d flysniper

Start adding the following features:
Membership
Profile
RoleManager
Personalization
SqlWebEventProvider

.................
An error has occurred. Details of the exception:
An error has occurred while establishing a connection to the server. When conne
cting to SQL Server 2005, this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Unable to connect to SQL Server database.

I have tried several different things (shooting in the dark) to resolve this issue, including:

verifing that port 445 is avaliable on the firewall per these directions:http://support.microsoft.com/default.aspx?scid=kb;en-us;839269

configured SQL server 2005 to allow remote connections following these directions:http://support.microsoft.com/kb/914277

with no change in results.

Anything else I should look into?

Thanks in advance,

Mike

I get that message when I forget to start sql server before trying to connect to the website.

|||

LockH - thanks for your response, I have confirmed that the SQL Service is up and running.

UPDATE: I have managed to get the aspnet_regsql.exe to run and the tables are created.

I have tried to set the connection string up correctly: <addname="ClubSiteDB"connectionString="Data Source=StormTrooper\FlySniper;Initial Catalog=FlySniperDev;Persist Security Info=True;User ID=XXXXXXXXXXXXX;Password=YYYYYYYYYYYY;"providerName="System.Data.SqlClient"/>

I think its just a switch somewhere that I'm missing.

I have set up a developer website for testing purposes, please usehttp://dev.flysniper.com/flysniperClubSite to see the actual error.

TIA,

Mike

|||

Did you create the tables in the database on the server, or did you copy the database files from your dev machine?

If you copied the database files onto that machine, did you go into database admin and attach the database files to that server?

|||

The tables were created directly on the server. It's my personal machine so I have direct access to it.

Thanks for you time,

Mike

CLR Stored Procedures & VS2005 ASP.NET designer support?

I have successfully created CLR stored procures using c# and SQL Server 2005. Now I want to use the CLR stored procedures with some ASP.NET controls. I can add the CLR stored procedure to the dataset designer and have it add a new table adapter but it does not list the columns in the designer view. This forces me to code the column references manually into the controls (tried: DropDownList, GridView).

I can deal with adding the columns manually for controls using a CLR stored procedure, but I want to make sure I was not missing something, am I?

BTW: TSQL stored procedures work as expected (show columns in the dataset designer)

thanks!

-pieter

Hi,

as metadata can be defined on the fly in a stored procedure by building your rowset one by one and then sending it through the pipe, I don′t really know if there is a way to give the designer a hint via some properties or anything else to sniff into the CLR resultset.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks. Your reply does help.

I just wanted to be sure it was not something I was doing incorrectly. The CLR stored procedures do indeed have a great deal of power available to them.

Let us hope the VS team can find some way of bringing the two closer together in the future.

-pieter

closing the database connection

Hi all,
sorry if this is in another post - I did a few searches and found nothing.
We have a custom asp .net ui and are rendering our reports directly to pdf.
We are running sql server stored procedures to populate our reports. What I
have noticed, however, during the course of testing the reports, is that if
you look in SQL Server EM the connections (listed as .Net SQL Client
Provider) seem to stay open for quite some time. This is a concern, and I am
trying to figure out if there is a way that we can close the connection(s) as
soon as the data has been retrieved and the report populated. I believe this
must be the connection from RS directly calling the SP to populate - has
anyone else seen this?
Thanks,Perhaps you can set some timers in the rsconfig.
I've noticed that my oracle connenctions stay open relatively long to;
although it has something to do with congestion on either de DB-server or the
RS-server. I notice that when I automticly rennder a number of reports (to
make chached-reports for all parameter values) the RS-jobs sometimes heap up
and the open connections do also (although there are never more than tree
reports rendered at the same time). The problem solves itself automaticly
thoug, everything slows down and apperantly RS gets time to clean it up.
"Myles" wrote:
> Hi all,
> sorry if this is in another post - I did a few searches and found nothing.
> We have a custom asp .net ui and are rendering our reports directly to pdf.
> We are running sql server stored procedures to populate our reports. What I
> have noticed, however, during the course of testing the reports, is that if
> you look in SQL Server EM the connections (listed as .Net SQL Client
> Provider) seem to stay open for quite some time. This is a concern, and I am
> trying to figure out if there is a way that we can close the connection(s) as
> soon as the data has been retrieved and the report populated. I believe this
> must be the connection from RS directly calling the SP to populate - has
> anyone else seen this?
> Thanks,

Closing a connection created from a SQLDataSource

I'm new to ASP.NET and I've searched before posting.

I have a simple form containing a FormView control. The FormView uses a SQLDataSource. This works fine and in 30 seconds I have a working form without writing any code.

A form built this way causes problems with connection pooling because I am not closing the connection. What is the best method for me to remedy this?

Every resource I've found explains that I have to explicitly close the connection. How do I do that in this case? Dispose the SQLDataSource in the FormView DataBound event? Rewrite the form so I can control opening and closing of the connection?

Thanks in advance.How about disconnecting on the page.OnUnload event?

Client Side Printing SQL Report

Can anyone explain and maybe post some code on how to print a SQL Report in asp .net - I'm using SQL Reporting sp2 and I just can't find anything that works out there. Your help would be greatly appreciated... I tried RSClientprint.dll and had no luck...

thanks
rich

We're using "OfficeWriter" by a company called SoftArtisans. Note, it's not cheap.|||

I see - I'm looking for the ability to print the report only no need for all the other features - Thanks for your reply...

rich

|||

rperreta wrote:

Can anyone explain and maybe post some code on how to print a SQL Report in asp .net - I'm using SQL Reporting sp2 and I just can't find anything that works out there. Your help would be greatly appreciated... I tried RSClientprint.dll and had no luck...

thanks
rich

Why aren't you using the exporting features from RS? The client can preview and then export to the available formats, with the capability to save them AND print them.|||You can try Windows Script Host for clientside object creation and printing. It is Free by Microsoft.
http://msdn.microsoft.com/library/en-us/script56/html/wsconswitchingnetworkedprintersonoff.asp?frame=true
Regards,
Hemchand|||Hello!
I may not understand on "How To Print a Report in SQL Report in Asp.Net" but in the latest Service Pack 2 for Reporting Services there was an Active X control that displays an Icon on the toolbar that provides for direct printing of a Reporting Services report directly to any printer on your network.
From MS www site:
Key Functional EnhancementsReports can now be printed directly from within Internet Explorer. A Microsoft ActiveX control is provided to support a rich client-side printing experience including full page preview.|||

hi,

i would like to check where do u find the RSClientprint.dll? i try search my pc for the dll file but invalid.

if any1 can tell mi where to find it..greatly appreciated

your regards

angela

|||Hello:
There is a CAB file RSCLIENTPRINT in
(at least on my server) c:\Program files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin
I just then moved the dll's to the bin directory within the same directory structure above.
Best Reagrds,
|||hi,
i know of the active x print that will call the print frm RSClientPrint but the main issue that i concern is how can i not display the print dialog box where by it prompt the user to select the printer and print. Because i want to print the report automatically once i evoke a print button on my .net application. is there any ways to do it?
cheers
Angela|||

hooligannes97 wrote:

rperreta wrote:

Can anyone explain and maybe post some code on how to print a SQL Report in asp .net - I'm using SQL Reporting sp2 and I just can't find anything that works out there. Your help would be greatly appreciated... I tried RSClientprint.dll and had no luck...

thanks
rich

Why aren't you using the exporting features from RS? The client can preview and then export to the available formats, with the capability to save them AND print them.

RS? Microsoft Reporting Services?|||

rperreta wrote:

RS? Microsoft Reporting Services?

Correct

Client Logo is not display on client computer

We are using Crystal Report 11 with ASP.Net 2005 and Sql Server 2005 as database.
When the application is deployed to a client computer and the report is previewed, the report appears but the Client Logo (JEPG Imange) do not.
in place of logo it is displaying cross.

Kindly help me to solve this problem as soon as possible

Regards
Amit JoshiIs it a client server application.

If yes, you need to put the picture on client machine as well or access it from server.

check out the path you specified for image.

Hope this Helps you.|||Thanx for reply.
No This is web based application. while testing it was woking fine in test server but after deploy on client PC (UK) it client logo is not showing.

Kindly help to solve this..

Regards
Amit|||Thanx for reply.
No This is web based application. while testing it was woking fine in test server but after deploy on client PC (UK) it client logo is not showing.

Kindly help to solve this..

Regards
Amit

I would say 90% that it's going to be the file path. either the client PC can't see it or it can't access it.

Check you server logs for 404 errors coming from the client.