Showing posts with label remote. Show all posts
Showing posts with label remote. Show all posts

Friday, March 30, 2012

job to run a remote process

I have a question regard the scheduling of a database job. I want to run a job that executes the following steps:

1) backup an entire database from DB server A

2) restore the database on DB Sever B

3) run a non database process on Server C (with xp_cmdshell)

Step 1 and 2 are easy enough but how do I start a process on an remote machine (Step 3)?

In my case the process in step 3 is will execute a Cognos DecisionStream job (rundsjob.exe)

My environment is

SQL Server 2000.

Windows Server 2003

Paul

If you are trying to do something like run a batch file remotely, you may want to look at WMIC.

Prior to Windows 2003, you'd use RCMD. This link might help you get started:

http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/featusability/wmic.mspx

-Sue

Monday, March 19, 2012

Job failure notification

Hello,
I created a job that will execute two dts packages at night. Both back up
different databases from the remote server to the local server, so they are
not dependent on each other. Also, if the first one fails, the job steps to
the second one. However, I would like to be notified if either/both of them
fail (and know which one failed).
Can I do this or should I have two separate jobs. If possible, I would
rather get an email saying DTS Package 1 failed versus having to look at the
each log file to determine which one failed.
--
Thanks in advance,
StevenWhy are you using DTS to do backups ?
You can have a job fire that will backup databases. You would have a job
per server you wanted to backup. You can specify the location of the backup
file using UNC. When you say backup do you actually mean data transfer ?
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Steven K" <sckeels@.lucent.com> wrote in message
news:uspA2dlRDHA.2116@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I created a job that will execute two dts packages at night. Both back up
> different databases from the remote server to the local server, so they
are
> not dependent on each other. Also, if the first one fails, the job steps
to
> the second one. However, I would like to be notified if either/both of
them
> fail (and know which one failed).
> Can I do this or should I have two separate jobs. If possible, I would
> rather get an email saying DTS Package 1 failed versus having to look at
the
> each log file to determine which one failed.
> --
> Thanks in advance,
> Steven
>|||Sorry Allan,
What I meant to write was data transfer.
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OtAVkklRDHA.3132@.tk2msftngp13.phx.gbl...
> Why are you using DTS to do backups ?
> You can have a job fire that will backup databases. You would have a job
> per server you wanted to backup. You can specify the location of the
backup
> file using UNC. When you say backup do you actually mean data transfer ?
> --
>
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> "Steven K" <sckeels@.lucent.com> wrote in message
> news:uspA2dlRDHA.2116@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > I created a job that will execute two dts packages at night. Both back
up
> > different databases from the remote server to the local server, so they
> are
> > not dependent on each other. Also, if the first one fails, the job
steps
> to
> > the second one. However, I would like to be notified if either/both of
> them
> > fail (and know which one failed).
> >
> > Can I do this or should I have two separate jobs. If possible, I would
> > rather get an email saying DTS Package 1 failed versus having to look at
> the
> > each log file to determine which one failed.
> >
> > --
> > Thanks in advance,
> >
> > Steven
> >
> >
>

Friday, February 24, 2012

JDBC sample code using named pipe and SQLServer 2005 driver?

Hi,

Does anybody have a working Java code sample that connects to an SQLServer 2005 database on a remote host, via the default named pipe, from a client using the SQLServer 2005 JDBC driver? Could you post it, or a pointer to it?

I've gotten java.sql DriverManager.getConnection() to work fine with TCP/IP connections before. But I'm a newbie with named pipes, and unclear on how the connection string/properties are different. I've tried to piece it together from multiple docs and threads, but haven't found sample code that quite fits my situation. I think a simple working example would best clarify the syntax.

The server is not using SQL Express. Most SQLServer configuration options are defaults; the named pipes protocol is enabled.

Thanks

Hi Dan,

The Microsoft SQL Server 2005 JDBC Driver does not support connections over named pipes. It only supports TCP/IP connections.

--David Olix

|||David,

Thanks for the info and your quick response.

I suggest mentioning this in the JDBC docs. I couldn't find it in my searching.

- Dan N.