Cluster installation

Hi guys,
Tks a million for your prompt reply. I have another question to ask u guys.
What are the order of installing server and sql clustering?
Is it W2k3sp1,MSCS,MSDTC,SQL,SQLsp3?
Tks once again for your help.
Message posted via http://www.droptable.com
You got it right. the only other thing I'd add is the SQL hotfix after
applying SQL SP3a:
http://support.microsoft.com/default...b;en-us;821277
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Mohd Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:958ee67996bc41df83c74e63f49157d4@.droptable.co m...
Hi guys,
Tks a million for your prompt reply. I have another question to ask u guys.
What are the order of installing server and sql clustering?
Is it W2k3sp1,MSCS,MSDTC,SQL,SQLsp3?
Tks once again for your help.
Message posted via http://www.droptable.com

cluster check

Guys,
Apart from cluster administrator, is there any way to check from inside SQL
server to know whether a particular installation is clustered?
select serverproperty('IsClustered') will tell you if a particular instance
is part of a cluster
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
> Guys,
> Apart from cluster administrator, is there any way to check from inside
> SQL
> server to know whether a particular installation is clustered?
|||thanks jasper...
"Jasper Smith" wrote:

> select serverproperty('IsClustered') will tell you if a particular instance
> is part of a cluster
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
>
>

cluster check

Guys,
Apart from cluster administrator, is there any way to check from inside SQL
server to know whether a particular installation is clustered?select serverproperty('IsClustered') will tell you if a particular instance
is part of a cluster
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
> Guys,
> Apart from cluster administrator, is there any way to check from inside
> SQL
> server to know whether a particular installation is clustered?|||thanks jasper...
"Jasper Smith" wrote:

> select serverproperty('IsClustered') will tell you if a particular instanc
e
> is part of a cluster
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
>
>

cluster check

Guys,
Apart from cluster administrator, is there any way to check from inside SQL
server to know whether a particular installation is clustered?select serverproperty('IsClustered') will tell you if a particular instance
is part of a cluster
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
> Guys,
> Apart from cluster administrator, is there any way to check from inside
> SQL
> server to know whether a particular installation is clustered?|||thanks jasper...
"Jasper Smith" wrote:
> select serverproperty('IsClustered') will tell you if a particular instance
> is part of a cluster
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
> > Guys,
> >
> > Apart from cluster administrator, is there any way to check from inside
> > SQL
> > server to know whether a particular installation is clustered?
>
>

Clone SQL SERVER question

Hello Guys,
I am working in a clone of SQL server and I have some question:
NEW SQLSERVER = Copy of OLD SQLSERVER
As the new sql server "NEW SQLSERVER" has the same configuration as
the "OLD SQLSERVER" all the jobs and others setups have still the old
"OLD SQLSERVER" settings. I have already done this operation for the
backups.
update backupset
set machine_name= 'NEW SQLSERVER'
where machine_name = 'OLD SQLSERVER'
what do you advice me to do in order to set up this machine currently
Any suggestion will be appreciate
Ina
Hi
Have you scripted the jobs and changed any references to the old server? Are
there any hard coded references in Stored procedure, triggers, views etc?
DTS packages can be exported using the DTS Backup tool
http://www.sqldts.com/default.aspx?242
Are you using replication?
If the server is not on the same domain or if you had local accounts for
logins, you will have to change them see
http://support.microsoft.com/kb/246133/. It may be necessary to also change
orphaned users http://support.microsoft.com/kb/274188/
John
"ina" wrote:

> Hello Guys,
> I am working in a clone of SQL server and I have some question:
> NEW SQLSERVER = Copy of OLD SQLSERVER
> As the new sql server "NEW SQLSERVER" has the same configuration as
> the "OLD SQLSERVER" all the jobs and others setups have still the old
> "OLD SQLSERVER" settings. I have already done this operation for the
> backups.
> update backupset
> set machine_name= 'NEW SQLSERVER'
> where machine_name = 'OLD SQLSERVER'
> what do you advice me to do in order to set up this machine currently
> Any suggestion will be appreciate
> Ina
>
|||Thanks John,
I haven't done anything concerning replication, views and triggers in
the old server, I had only setup up backups and maintenance plans.
Thanks for this documents I will get through.
Ina
Thank you a lot for all
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you scripted the jobs and changed any references to the old server? Are
> there any hard coded references in Stored procedure, triggers, views etc?
> DTS packages can be exported using the DTS Backup tool
> http://www.sqldts.com/default.aspx?242
> Are you using replication?
> If the server is not on the same domain or if you had local accounts for
> logins, you will have to change them see
> http://support.microsoft.com/kb/246133/. It may be necessary to also change
> orphaned users http://support.microsoft.com/kb/274188/
>
> John
> "ina" wrote:

Clone SQL SERVER question

Hello Guys,
I am working in a clone of SQL server and I have some question:
NEW SQLSERVER = Copy of OLD SQLSERVER
As the new sql server "NEW SQLSERVER" has the same configuration as
the "OLD SQLSERVER" all the jobs and others setups have still the old
"OLD SQLSERVER" settings. I have already done this operation for the
backups.
update backupset
set machine_name= 'NEW SQLSERVER'
where machine_name = 'OLD SQLSERVER'
what do you advice me to do in order to set up this machine currently
Any suggestion will be appreciate
InaHi
Have you scripted the jobs and changed any references to the old server? Are
there any hard coded references in Stored procedure, triggers, views etc?
DTS packages can be exported using the DTS Backup tool
http://www.sqldts.com/default.aspx?242
Are you using replication?
If the server is not on the same domain or if you had local accounts for
logins, you will have to change them see
http://support.microsoft.com/kb/246133/. It may be necessary to also change
orphaned users http://support.microsoft.com/kb/274188/
John
"ina" wrote:
> Hello Guys,
> I am working in a clone of SQL server and I have some question:
> NEW SQLSERVER = Copy of OLD SQLSERVER
> As the new sql server "NEW SQLSERVER" has the same configuration as
> the "OLD SQLSERVER" all the jobs and others setups have still the old
> "OLD SQLSERVER" settings. I have already done this operation for the
> backups.
> update backupset
> set machine_name= 'NEW SQLSERVER'
> where machine_name = 'OLD SQLSERVER'
> what do you advice me to do in order to set up this machine currently
> Any suggestion will be appreciate
> Ina
>|||Thanks John,
I haven't done anything concerning replication, views and triggers in
the old server, I had only setup up backups and maintenance plans.
Thanks for this documents I will get through.
Ina
Thank you a lot for all
John Bell wrote:
> Hi
> Have you scripted the jobs and changed any references to the old server? Are
> there any hard coded references in Stored procedure, triggers, views etc?
> DTS packages can be exported using the DTS Backup tool
> http://www.sqldts.com/default.aspx?242
> Are you using replication?
> If the server is not on the same domain or if you had local accounts for
> logins, you will have to change them see
> http://support.microsoft.com/kb/246133/. It may be necessary to also change
> orphaned users http://support.microsoft.com/kb/274188/
>
> John
> "ina" wrote:
> > Hello Guys,
> >
> > I am working in a clone of SQL server and I have some question:
> >
> > NEW SQLSERVER = Copy of OLD SQLSERVER
> >
> > As the new sql server "NEW SQLSERVER" has the same configuration as
> > the "OLD SQLSERVER" all the jobs and others setups have still the old
> > "OLD SQLSERVER" settings. I have already done this operation for the
> > backups.
> >
> > update backupset
> > set machine_name= 'NEW SQLSERVER'
> > where machine_name = 'OLD SQLSERVER'
> >
> > what do you advice me to do in order to set up this machine currently
> >
> > Any suggestion will be appreciate
> >
> > Ina
> >
> >

Clone SQL SERVER question

Hello Guys,
I am working in a clone of SQL server and I have some question:
NEW SQLSERVER = Copy of OLD SQLSERVER
As the new sql server "NEW SQLSERVER" has the same configuration as
the "OLD SQLSERVER" all the jobs and others setups have still the old
"OLD SQLSERVER" settings. I have already done this operation for the
backups.
update backupset
set machine_name= 'NEW SQLSERVER'
where machine_name = 'OLD SQLSERVER'
what do you advice me to do in order to set up this machine currently
Any suggestion will be appreciate
InaHi
Have you scripted the jobs and changed any references to the old server? Are
there any hard coded references in Stored procedure, triggers, views etc?
DTS packages can be exported using the DTS Backup tool
http://www.sqldts.com/default.aspx?242
Are you using replication?
If the server is not on the same domain or if you had local accounts for
logins, you will have to change them see
http://support.microsoft.com/kb/246133/. It may be necessary to also change
orphaned users http://support.microsoft.com/kb/274188/
John
"ina" wrote:

> Hello Guys,
> I am working in a clone of SQL server and I have some question:
> NEW SQLSERVER = Copy of OLD SQLSERVER
> As the new sql server "NEW SQLSERVER" has the same configuration as
> the "OLD SQLSERVER" all the jobs and others setups have still the old
> "OLD SQLSERVER" settings. I have already done this operation for the
> backups.
> update backupset
> set machine_name= 'NEW SQLSERVER'
> where machine_name = 'OLD SQLSERVER'
> what do you advice me to do in order to set up this machine currently
> Any suggestion will be appreciate
> Ina
>|||Thanks John,
I haven't done anything concerning replication, views and triggers in
the old server, I had only setup up backups and maintenance plans.
Thanks for this documents I will get through.
Ina
Thank you a lot for all
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you scripted the jobs and changed any references to the old server? A
re
> there any hard coded references in Stored procedure, triggers, views etc?
> DTS packages can be exported using the DTS Backup tool
> http://www.sqldts.com/default.aspx?242
> Are you using replication?
> If the server is not on the same domain or if you had local accounts for
> logins, you will have to change them see
> http://support.microsoft.com/kb/246133/. It may be necessary to also chang
e
> orphaned users http://support.microsoft.com/kb/274188/
>
> John
> "ina" wrote:
>

Client viewing KPI Browser and cube browser

Hi guys

I am just wondering, i know that within VS the developer has access to the KPI Browser and cube browser. How do i give access to the KPI Browser to a business user and allow them to play with the cube browser (without giving them VS ). I know that Reporting services can hook onto the cubes and create reports from that but that’s not quite the same, as I would have to create a report that looks like one that is already available in VS.

I read a little bit here http://office.microsoft.com/en-us/sharepointserver/HA101742051033.aspx which says that sharepoint might be able to access the KPI data and display it but if this is the case does it look the same as it does in VS? Also if i don’t have sharepoint this doesn't help me all that much.

Also i know that a business user has access to the report builder but i have not seen anything in it yet that looks like the cube browser. The closest it comes is the matrix view, which i wouldn't have thought was exactly the same.

Thanks for the help

Anthony

Have you considered end-user tools like Excel 2007 and Proclarity - these can connect to cube KPI's, and are better suited to business users? The latest versions of some other AS 2005 client tools also support KPI's.

Client Network Utility

Guys,
Anybody knows how the client network utility can be configured PROGRAMATICALLY.
What I wanna do ultimately, is to run a batch file and set an alias for the client network utility.
Thanks,
Regards,Any possibilities thru OSQL? I haven't found anything yet.|||Double posting. :)|||I'm pretty sure that you can do it with a registry file... don't have SQL Server on my new laptop yet so I can't tell you what key, but it should be in HKEY_LOCAL_MACHINE somewhere

all you should have to do is set it up, do a search in the registry (using regedit) for the alias or whatever you added, export that key to a *.reg file, clean up the file a bit (to get rid of duplicate or extraneous keys) and import it on a test machine to check it out.

I use that method to add system ODBC data sources all the time, never done it with the Client Network Utility though... standard disclaimer however... if you mess up the registry it's your fault and don't forget to back it up before importing anything|||Hey thanx Drew. Interesting idea. I'll give it a try and let you know what happened.|||sure thing... I'll be in the office tomorrow and will post it up if I get to it before you, been meaning to do it for a long time to make client config as dummy proof as possible so I don't have to sit on the phone t-shooting stupid crap like that