hot backup: idea

Showing posts with label idea. Show all posts

Friday, March 30, 2012

How can I connect to SQL Server 2005 analysis services server programmatically?

Hi, all here,

Would please anyone here give me any idea about how can I connect to SQL Server 2005 analysis services server and send XML request to it programmatically (with Business intelligence development studio in SQL Server 2005)? Thanks a lot.

With best regards,

Yours sincerely,

That's a big topic - you can start here

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

For the XMLA ThinMiner sample look here

http://www.sqlserverdatamining.com/DMCommunity/LiveSamples/124.aspx

Here's a blog entry of someone who's figured it out as well

http://geekswithblogs.net/darrengosbell/archive/2006/05/25/xmlaClient.aspx

|||Hi, Jamie, thanks a lot.

Wednesday, March 7, 2012

How about getting a dedicated server to run and manage SQL jobs

Hi all:

Give me some feedback.

In my company, we have 10+ sql servers and many sql jobs running on every SQl server.

What about the idea that running all jobs on a dedicated sql servers?

at least 2 advantages

1.easy to managment

2.if agent server down, we restart the server not to impact the downtime of the production server.

any suggestion is welcome.

We had a similar setup which worked well.
Basically had big machines for SQL server and then used blades for "distributed" SSIS jobs.
All you really need is fast procs, lots of memory and not much disk space.
The idea was that as one box would become loaded, we would introduce another. All boxes would have the same jobs on it, but some disabled. The packages were run from a network location so should a box die, we can switch over quite quickly.

The issues are:
Licensing
Network performance
Cost

But if those are not a problem, it is a nice solution.

Monday, February 27, 2012

Hot-standby SQL Server Using Alias Name?

I want to have a hot standby SQL server for my clients. My idea is to install
SQL on two separate machines, SRVA and SRVB, and configure continuous merge
replication between them. Client machines would connect to an alias name,
SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon failure, DNS
would be changed to point to SRVB. Could something like this work? If so, how
would one start to implement it?
Maybe a shorther question would be, is it possible for clients to connect to a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric RobinsonThis is a multi-part message in MIME format.
--=_NextPart_000_0370_01C3A9EA.14018070
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Consider using a clustered installation of SQL Server. It has automatic
failover and requires no human intervention.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Eric Robinson" <eric@._nospam_nvipa.com> wrote in message
news:CFN379384331352315@.news.microsoft.com...
I want to have a hot standby SQL server for my clients. My idea is to
install
SQL on two separate machines, SRVA and SRVB, and configure continuous merge
replication between them. Client machines would connect to an alias name,
SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon failure,
DNS
would be changed to point to SRVB. Could something like this work? If so,
how
would one start to implement it?
Maybe a shorther question would be, is it possible for clients to connect to
a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric Robinson
--=_NextPart_000_0370_01C3A9EA.14018070
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Consider using a clustered =installation of SQL Server. It has automatic failover and requires no human intervention.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Eric Robinson" =wrote in message news:CFN3793843313523=15@.news.microsoft.com...I want to have a hot standby SQL server for my clients. My idea is to =install SQL on two separate machines, SRVA and SRVB, and configure =continuous merge replication between them. Client machines would connect to an alias =name, SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon =failure, DNS would be changed to point to SRVB. Could something like this =work? If so, how would one start to implement it?Maybe a shorther =question would be, is it possible for clients to connect to a SQL server =alias name (not a named instance) instead of the actual machine name of the server?--Eric Robinson

--=_NextPart_000_0370_01C3A9EA.14018070--

Friday, February 24, 2012

Hot Standby Server w/out Clustering?

I want to have a hot standby SQL server for my clients without clustering. My
idea is to install SQL on two separate machines, SRVA and SRVB, and configure
continuous merge replication between them. Client machines would connect to an
alias name, SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon
failure, DNS would be changed to point to SRVB. Could something like this
work?
Maybe a shorther question would be, is it possible for clients to connect to a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric RobinsonWhat it sounds like you need is log shipping, not merge
replication. Replication is not the best of solutions for
a standby solution, and if you use replication for some
form of availability, it's usually transactional.
Replication is good if you have some specific data to make
available, but you're limited by rowsize and such, but as
for a complete copy of your DB, replication is not the
way. Log shipping is the standard SQL method of making a
warm standby.
You can set up NLB to do what you want to alias things,
and this is all covered in the book SQL Server 2000 HIgh
Availability on how to set it up using it as a "switch"
mechanism - not load balanced - for SQL Server. There are
even configuration instructions on the CD-ROM.
>--Original Message--
>I want to have a hot standby SQL server for my clients
without clustering. My
>idea is to install SQL on two separate machines, SRVA and
SRVB, and configure
>continuous merge replication between them. Client
machines would connect to an
>alias name, SRVC, with DNS for SRVC resolving to the IP
address of SRVA. Upon
>failure, DNS would be changed to point to SRVB. Could
something like this
>work?
>Maybe a shorther question would be, is it possible for
clients to connect to a
>SQL server alias name (not a named instance) instead of
the actual machine
>name of the server?
>--Eric Robinson
>.
>|||To have standby , it is better to use Log shipping. U can
even write scripts to take backup and mover to otherserver
and restore ,
Replication is only for data propagation not for Standby.
In case of Replication schema changes won't be applied. Of
course Merge is not useful u need Transactioal replication.
>--Original Message--
>I want to have a hot standby SQL server for my clients
without clustering. My
>idea is to install SQL on two separate machines, SRVA and
SRVB, and configure
>continuous merge replication between them. Client
machines would connect to an
>alias name, SRVC, with DNS for SRVC resolving to the IP
address of SRVA. Upon
>failure, DNS would be changed to point to SRVB. Could
something like this
>work?
>Maybe a shorther question would be, is it possible for
clients to connect to a
>SQL server alias name (not a named instance) instead of
the actual machine
>name of the server?
>--Eric Robinson
>.
>