Showing posts with label import. Show all posts
Showing posts with label import. Show all posts

Monday, March 26, 2012

Running a DTS

Hi there
I've been trying to do this all w and it's driving me mad !
All I want to do is run a DTS import from a SQL script. When it's run
manually it takes 15 seconds.
The Dts is called "DTS_LisImport"
The DB is "sqlReleaseTwo"
I'm running SQL7
Many thanks
Paul.try
[url]http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_11959518.html[/ur
l]
"Paul in Harrow" <PaulinHarrow@.discussions.microsoft.com> wrote in message
news:D0CC5A4A-5E73-4A91-A17C-344852ED2F7D@.microsoft.com...
> Hi there
> I've been trying to do this all w and it's driving me mad !
> All I want to do is run a DTS import from a SQL script. When it's run
> manually it takes 15 seconds.
> The Dts is called "DTS_LisImport"
> The DB is "sqlReleaseTwo"
> I'm running SQL7
> Many thanks
> Paul.
>|||See if this helps: http://www.sqldts.com/default.aspx?210
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Paul in Harrow" <PaulinHarrow@.discussions.microsoft.com> wrote in message
news:D0CC5A4A-5E73-4A91-A17C-344852ED2F7D@.microsoft.com...
Hi there
I've been trying to do this all w and it's driving me mad !
All I want to do is run a DTS import from a SQL script. When it's run
manually it takes 15 seconds.
The Dts is called "DTS_LisImport"
The DB is "sqlReleaseTwo"
I'm running SQL7
Many thanks
Paul.|||Tried something different:
Use msdb
execute sp_start_job @.job_id= "7B42CBCD-A615-4CF4-B204-8FE4A31E65B1"
[Open sysjobs_view in msdb to get the job_id]
gives me: "Job 'DTS__LisImport' started successfully."
Is there a sp_run_job anywhere?
Paul

Wednesday, March 21, 2012

Run the job

I have question, in sql server i created a job to import data and schedule it on every night, But now i want to run again as the original data has been changed. I don't want to wait tonight, How can i do this? After i run one time, i still want this job to run on schedule.
Another question, after i create the job, can i see the content of the job as i want to modify.Yes you can,

You just right click on the job and choose start job.

and it will run that instance and it will run again according to the schedule you have set for it.

Lystra|||Thanks, i got it. I had a question, Can i see the content of the job as this job was created long time ago, i want to modified, How can i see the content? Thanks again!|||Double click on the job, click on the step tab and double click on the step you want to see.

Lystra|||Thank, i tried to use your way to run the job once, it didn't work, i found when i create a job, it also create local package, so i have go the DTS folder then click the local package, right click the package i want to run then execute the package, then it worked, why i right the job to start the job it didn't work?|||You said a job, But if it is a DTS package you can excute it directly from the package.

As for the 'job create a local package' it's the other way around, a local packages create a job if you add a schedule.

Thanks

Lystra|||Thank you very much!

Wednesday, March 7, 2012

Run a SSIS Package including Windows Tasks Scheduler?

Hello

As a beginner I have created some Packages to import Data to SQL Server.

The Packages are running well.

I have created a Task to run the Package on a SQL SERVER 2005 Express. The Task starts.

Then a Execute Package Wizard Picture appears on the Screen.

I have mannually to select the Connection Manager and the Connection String.

After the selection the Task runs without any Problem.

Now I like to get the Task to run without any manual intervention.

I was looking in Internet but could not find a solution.

Can someone give me a hint how to get the Task working without intervention?

Thanks for an early answer.

Regards

Chaepp

Specify dtexec.exe as executable to run in the Job definition.
See Books Online for dtexec command line parameters reference. In simplest case: "dtexec.exe /f c:\package.dtsx"|||

Hello Michael

I'ts working now. Thank you very much for your help!

Regards

Chaepp

RUN A SAVED SSIS Package in 2005

I saved a SSIS ( data Import package in SQL SERV 2005)
how can i run it??I'm also interested to know. is it a must to have at least standard edition in order to run a SSIS (.dtsx file) package? Is it possible to use an alternative to execute it on ad hoc basis?

run a query against another server

Hi, I have got SSMSE installed and am seeing how I can use it for my work stuff rather than MSDE.

I used to import using Enterprise Manager tables from our corp servers into my local MSDE to work with.

I have managed to create the required tables in SQL Exprerss and can see I have a connection to my local server (SQL Express) and my corp server.

When I query sys.servers I only see SQL Express and not the corp one. How do I run a select query that selects from the corp and inserts into the local. I have all the insert fields etc but it errors stating the corp database is not in sys.serevrs?

Thanks

hi,

you have to define a "linked server"..

select the Server Objects->Linked Servers node in SSMSE in your local connection server... add a linked server pointing to the corp server providing the appropriate credentials..

you can then query the linked server providing the 4 part naming of the object like

SELECT * FROM linked_server_name.database_name.schema_name.object_name;

once you have the connection working, you can then INSERT SELECT into your local database..

regards

|||Hi, I tried this but get errors?

I can connect in server explorer within VS.NET 2005 Pro IDE and get the following information:

Provider=
.NET Framework Data Provider for SQL Server

Connection String=
Data Source=Virtue;Initial Catalog=orbital;Integrated Security=True

I do not get an option to choose this provider in the combobox on the New Linked Server page?

So I get this error?

TITLE: Microsoft SQL Server Management Studio Express

"The linked server has been created but failed a connection test. Do you want to keep the linked server?"

ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

The OLE DB provider "SQLNCLI" for linked server "VIRTUE" reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "VIRTUE".
OLE DB provider "SQLNCLI" for linked server "VIRTUE" returned message "Invalid authorization specification".
OLE DB provider "SQLNCLI" for linked server "VIRTUE" returned message "Invalid connection string attribute". (Microsoft SQL Server, Error: 7399)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=7399&LinkId=20476

|||

hi,

pachjo wrote:

Hi, I tried this but get errors?

I can connect in server explorer within VS.NET 2005 Pro IDE and get the following information:

Provider=
.NET Framework Data Provider for SQL Server

Connection String=
Data Source=Virtue;Initial Catalog=orbital;Integrated Security=True

I do not get an option to choose this provider in the combobox on the New Linked Server page?

this information is relative to the "Add connection" wizard in the Server Explorer, isn't it?

actually the .NET Framework Data Provider for SQL Server is SQL Native Client and, in my installation, it is obviously available in SSMSE as well as SQLNCLI..

So I get this error?

TITLE: Microsoft SQL Server Management Studio Express

"The linked server has been created but failed a connection test. Do you want to keep the linked server?"

ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

The OLE DB provider "SQLNCLI" for linked server "VIRTUE" reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "VIRTUE".
OLE DB provider "SQLNCLI" for linked server "VIRTUE" returned message "Invalid authorization specification".
OLE DB provider "SQLNCLI" for linked server "VIRTUE" returned message "Invalid connection string attribute". (Microsoft SQL Server, Error: 7399)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=7399&LinkId=20476

did you provide the correct credential info for the remote server?

regards

|||Well I can connect no problem through server explorer and accerss the data. I used the same connection string from there and tried various things such as:

Linked Server = Virtue
Provider=SQL Native Client
Product Name=Virtue (not sure what to put here?)
Data source=Virtue
Connection String=Data Source=Virtue;Initial Catalog=orbital;Integrated Security=True
Catalog=blank

I am unsure what I am doing wrong here?
|||

hi,

Linked Server: network name of the remote SQL Server instance

Provider = SQL Native Client

Product Name = Provider = SQL Native Client

then you can go on bypassing the additional info of the "General" tab of the "Add linked server" dialog...

in the "Security" tab select the appropriate mapping or specify a specif SQL Server login (Be made using this security context)..

regards

|||

This is really getting me down as I am getting no where Sad

I set the details as above and tried entering my nt logon details in various ways to include/omit the domain name but still no joy!

What I dont get is within VS.NET it connects straight away without bother and I can acces the tables! ?

|||

HI,

OK I am sort of there, but not completely?

I have created a connection to the remote server and created a linked server to it using the same coalation as the remote.

But when I create the tables, import the date all is well until I try to run a script and I get a coaltion conflict?

The remote is SQL_Latin1_General_CP1_CI_AS but I get an error complaining about

Latin1_General_CI_AS?

When I look at the remote and the linked they both say SQL_Latin1_General_CP1_CI_AS so I don't know where SQL_Latin1_General_CI_AS is coming from?

Help anyone....

|||

Oh...hold the phone!

I think I have found it?

The local database has the wrong coalation so.......I will start again ;-)