i'm sorry man no was my intention

i′m sorry my bad english

i have a dts in sql server 2005

for example in sql server 2000 i can do that :

over DTS right-clik choose option "Scheduled pachage" and this create a scheduled what i mean is that this produces a "JOB"

what i mean is that i need to know how can to create a scheduled to DTS′s in sql 2005

Please anyone of you provide some solution for this.

Okay, I completely misunderstood what you wanted before. But, I think I can help you now.

Once you have the SSIS package (DTS packages mean something else - like packages from SQL SERVER 2000 DTS) you can use SQL Server Agent to shedule the package to be run at a certain time.

Use the SQL Server Agent to schedule your package.

|||

sorry man:

what i do in sql server 2005 is:

right-click over SQL Server Agent , choose the option "New" and choose option "Schedule" but isn't what i want, may be i am not specfic

when i do right-click over dts in sql server 2000 and choose the option schedule package this produces an scheduled and i can see it in the part of the jobs

Now how i can do that in sql server 2005? i need to see of my DTSs the jobs that i created and you said me that i can do by SQL Server Agent in SQL server 2005 and this isn′t do what i want.

Please anyone of you provide some solution for this.
Thanks :)

|||

limon26,

I merged this post into your earlier thread. If you want to reply to another reply you should use the reply button and not the new thread button. This will keep the discussion in one thread and others that can help will be able to follow the discussion more easy.

Thanks.

|||

i apologies for that

so what can i do about my DTSs in sql server 2005 ?

|||

I am not that experienced with SSIS for 2005, hopefully swells or somebody else will be able to help you further...

|||

In SQL Server 2000, you could create a schedule by right-clicking on a package in Enteprise Manager and selecting "Schedule Package." SQL Server 2000 created the SQL Server Agent job. You could find the jobs in Enterprise Manager under the Management folder, in the jobs tree.

In SQL Server 2005 there are some changes ...

1. SQL Server Agent is not automatically enabled. Make sure the service has been started.

2. You do not automatically create scheduled jobs for SSIS. You should right click on the SQL Server Agent icon in the SQL Server Object Explorer in the Management Studio and select to create a new Agent Job. When you do that, you can add a new job step to execute an SSIS package. You can also add a new schedule.

The end result is similar to 2000 - jobs are listed under the SQL Server Agent node; jobs have steps - one step executes a package; and jobs have schedules.

An important difference is that SSIS now has an Agent subsytem for more better integrated execution.

hth

Donald

|||

After create your ssis package. Here is step you have to do to make a job run....

My ssis is running every 10 min.....

Here is what I do to make it work.......

Create the proxy account, And SQL Server Agent running under your NT Acount and then the job Steps running under the "SQL Agent Service Account" and your nt account as the owner of the job. It will works perfect.

I don't know if you know how to create proxy account. Here is how to create:

Use master

CREATE CREDENTIAL [MyCredential] WITH IDENTITY = 'yourdomain\myWindowAccount', secret = 'WindowLoginPassword'

Use msdb

Sp_add_proxy @.proxy_name='MyProxy', @.credential_name='MyCredential'

Sp_grant_login_to_proxy @.login_name=' devlogin', @.proxy_name='MyProxy'

Sp_grant_proxy_to_subsystem @.proxy_name='MyProxy', @.subsystem_name='SSIS'

Use master

CREATE CREDENTIAL [MyCredential] WITH IDENTITY = 'yourdomain\myWindowAccount', secret = 'WindowLoginPassword'

Use msdb

Sp_add_proxy @.proxy_name='MyProxy', @.credential_name='MyCredential'

Sp_grant_login_to_proxy @.login_name=' devlogin', @.proxy_name='MyProxy'

Sp_grant_proxy_to_subsystem @.proxy_name='MyProxy', @.subsystem_name='SSIS'

kenny

|||Similar problems, but (so far) the credentials/proxy doesn't seem to resolve it.
We have two people who have developed some SSIS packages, myself and another developer. The other developer's SSIS package runs fine from BIDS, DTexec and DTexecUI, but not from SQL Server agent. My SSIS package runs fine from BIDS, DTexec, DTexecUI and local SQLServer Agent. I haven't had the opportunity to have it deplyed into another environment to check if I have problems from the server.
What was interesting to me, in attempting to test the credentials, was that the working SQL Server Agent job, it I edit it to use the proxy, fails. If I edit the job back to using the SQL Agent Service Account (on the RUN AS tab on the task), then it works successfully.
Now this may be because I've set up the credential incorrectly, since it was my first time (be gentle :-)). I'm going to try and modify the script above and see if that works any better. The credential I set up used a local user I created that was part of the powerusers group. The package does file operations locally (based on the current configuration file). The 'ProtectLevel' was set to 'EncryptSenstitiveWithPassword', and this specific test job is using SQL Server as the package source.
Nay help? The KB http://support.microsoft.com/kb/918760 states that this is ' This behavior is by design.' - but surely it should also be easy to use?
|||using the scipr (after removing the duplicate, and adding exec's), I generated a proxy and a credential. The user being used is the same one I create earlier (which is a member of the power user group on my laptop). I get the following error:
-
Date 25/07/2006 14:21:59
Log Job History (Test Excel Orchestration)
Step ID 1
Server MyLaptop\SQL2005_SP1_TEST
Job Name Test Excel Orchestration
Step Name Invoke Excel Orchestration
Duration 00:00:01
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: MyLaptop\SSISAgentJobCredUser. The package could not be loaded. The step failed.
-
this proves the credential at least worked - it did try to run with the correct user, but still no joy.
.... even less joy now, since I now get the following, trying to use this in the way that worked before:

Date 25/07/2006 14:27:45
Log Job History (Test Excel Orchestration)
Step ID 1
Server MyLaptop\RGALBRAITH\SQL2005_SP1_TEST
Job Name Test Excel Orchestration
Step Name Invoke Excel Orchestration
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account. The step failed.

|||

Hey,

Today I got the same error as you, to fixed I didn't create the credentials, I changed the owner for the Scheduled Jobs instead, and it's works great!

|||

I fixed this by adding the owner of the package to the owned schema's in the agent roles in msdb.

take a look at this link:

http://www.microsoft.com/technet/prodtechnol/sql/2005/newsqlagent.mspx

i want to convert sql stored procedures to dll

can anyone help me and excuse my terrible english. i want to convert sql stored procedures to dll.

If i got you correctly then I don't think you can do so (convert stored procedure to dll) - the stored procedures reside in your database as its objects. Perhaps a little detail with what you want to achieve actually would have been of more help.

sql

i really need some help!!!!!!!

well......im from peru....i dont speak english too well.......but...i have the SQL express edition....but when i open it....i gotta to connect to a server.....but i dont have any server.....what do i should put to in "server name" and "authentication"...to star to use the SQL express edition....

well..if there are some grammathical mistakes....sorry...im learnin` english

please answer me
is an emergency!!!!
Jaime

well generally you connect to the local computer\SQLExpress:

(local)\SQLExpress

in regards to authentication, again it depends what type of authentication you set up. Was it Windows/trusted authentication or SQL authentication? if its Windows then you just type in your Windows username followed by the Windows password I believe otherwise its the SQL user account you created

|||well if you can tell me what do i should put in "server name" and "authentication"......i`ll fell better|||

servername AFAIK is usually:

(local)\SQLExpress

as for authentication as stated, depends on the type of authentication you have set up. If its Windows, then enter your username and password you use for Windows login. If its SQL user account, enter the username and password for the SQL user account you created.

|||ahmedilyas...im 17...........im learnin SQL in my university....i dont understand what u said.......but-......how do i know the type of authentication i set up?....can u help me please!!!!!!!|||

try www.connectionstrings.com

Attach a database file on connect to a local SQL Server Express instance:

"Server=.\SQLExpress;AttachDbFilename=c:\asd\qwe\mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
- or -
"Server=.\SQLExpress;AttachDbFilename=|DataDirectory|mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
(use |DataDirectory| when your database file resides in the data directory)

Why is the "Database" parameter needed? Answer: If the database was previously attached, SQL Server does not reattach it (it uses the attached database as the default for the connection).

Using "User Instance" on a local SQL Server Express instance:

"Data Source=.\SQLExpress;integrated security=true;attachdbfilename=|DataDirectory|\mydb.mdf;user instance=true;"

The "User Instance" functionality creates a new SQL Server instance on the fly during connect. This works only on a local SQL Server 2005 instance and only when connecting using windows authentication over local named pipes. The purpose is to be able to create a full rights SQL Server instance to a user with limited administrative rights on the computer. To enable the functionality: sp_configure 'user instances enabled','1' (0 to disable)

Using SQL Server 2005 Express? Don't miss the server name syntax: SERVERNAME\SQLEXPRESS (Substitute "SERVERNAME" with the name of the computer)

|||

Hi Jamie,

When you installed SQL Express, you installed the server onto your computer. SQL Express installs by default to something called a named instances, which is just the way we refer to the name of the server. As long as you didn't change anything when you were installing, the name of your SQL Express instance is "SQLEXPRESS". When connecting to SQL Server, you have to specify both the machine name and the instance name, in the format <machine name>\<instance name>. In cases where you are connecting to a SQL Server that is on the same machine that your are logged into, you can replace the <machine name> part with either the word "(local)" or with a period "." as form of short hand. So, in order to connect to the default copy of SQL Express on the computer you are logged into, you would put the following in the Server name text box:

(local)\SQLEXPRESS

Normally, SQL Express uses Windows Authentication, which means that SQL will recognize the same user account that you use when logging onto Windows. If you did not change anything when you installed SQL Express, you should just be able to select Windows Authentication and SQL Express will recognize you without providing any additional user name or password.

Hope this helps,

Mike

|||Hi Michael,

I love your messages! You are excellent

at explaining answers to problems and queries for beginners.

You're the TOP answer provider on the MSDN site in terms of

quality! Thank you!

For your information, this query is probably a popular one due to that

lack of explanation on the SQL video lesson05. He simply assumes

that you can click on the "Connect" button without any explanation

about server name etc - and any beginner will, of course, probably be

opening SQL Server Management for the first time, so therefore would

require this information to continue further.

Like Me!!!

However, following your instructions, I now have another error message

that, according to your information re local connections sounds bizzaar.

I typed in:

(local)SQLEXPRESS

I left "Windows Authentication" as is.

And clicked connect.

The User Name came up with:

YOUR-6202AC0500\user

(which I vaguely recognise as seen somewhere else and appears to

describe my PC.) My directory for "Documents and Settings" is

"user's Documents" (I obviously haven't named my PC) and the owner is

Fran Smith (in case this is relevant) - sorry - as mentioned, beginner.

The error says the following:

Connect to Server

Cannot connect to (localSQLEXPRESS)

Additional Information:

An error has occurred while establishing a connection to the

server. When connecting 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)(Microsoft

SQL Server, Error: 53)

There's a little "Show Technical Details" icon at the bottom of the

error message, which I clicked on which provided a "For Help:" http

link. This took me to a page that began "We're sorry.

There's no additional information...". The "Help" icon took me to

the same page.

Why is it seemingly attempting to connect to a remote server when a)

I've specified local and b) it has also even found my PC user

name? What do I do to correct this. I did install it

accepting the defaults provided.

Thank you in advance.

I'm now a little frustrated. I have began the video sequences

(which is a fabulous learning tool because it is explained WHY etc, not

just click here/do this as the written tutorials tend to do); however I

am stuck awaiting answers to all three sequences:

VB - on the

databinding issue: I read the other forums etc, and found the

basic problem regarding the two databases/saving to only the

one/debugging overwrites etc, but I wanted to know how then, do we save

to the actual database, how and when does this occur, if not at that

time? refer VBLesson09.

VWD - userCount

doesn't work for me - either in FireFox (where it doesn't increment) or

in IE7 (where it continues to increment each time a window is

refreshed). refer VWDLesson03

And now, SQL Lesson05.

My other username is BasilTabethaCat. These have been outstanding

for 3 and 2 days respectively, with no reply attempts or answers.

How do I invoke an answer?

I am now stuck as I would rather not continue the learning process

while I have a hole in my understanding (I am a student teacher - so

I'm well informed on the pitfalls of this!)

HELP!!

Cheers,

Fran...

PS I meant the compliment above - your answers in several areas have helped me a lot!

i really need some help!!!!!!!

well......im from peru....i dont speak english too well.......but...i have the SQL express edition....but when i open it....i gotta to connect to a server.....but i dont have any server.....what do i should put to in "server name" and "authentication"...to star to use the SQL express edition....

well..if there are some grammathical mistakes....sorry...im learnin` english

please answer me
is an emergency!!!!
Jaime

well generally you connect to the local computer\SQLExpress:

(local)\SQLExpress

in regards to authentication, again it depends what type of authentication you set up. Was it Windows/trusted authentication or SQL authentication? if its Windows then you just type in your Windows username followed by the Windows password I believe otherwise its the SQL user account you created

|||well if you can tell me what do i should put in "server name" and "authentication"......i`ll fell better|||

servername AFAIK is usually:

(local)\SQLExpress

as for authentication as stated, depends on the type of authentication you have set up. If its Windows, then enter your username and password you use for Windows login. If its SQL user account, enter the username and password for the SQL user account you created.

|||ahmedilyas...im 17...........im learnin SQL in my university....i dont understand what u said.......but-......how do i know the type of authentication i set up?....can u help me please!!!!!!!|||

try www.connectionstrings.com

Attach a database file on connect to a local SQL Server Express instance:

"Server=.\SQLExpress;AttachDbFilename=c:\asd\qwe\mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
- or -
"Server=.\SQLExpress;AttachDbFilename=|DataDirectory|mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
(use |DataDirectory| when your database file resides in the data directory)

Why is the "Database" parameter needed? Answer: If the database was previously attached, SQL Server does not reattach it (it uses the attached database as the default for the connection).

Using "User Instance" on a local SQL Server Express instance:

"Data Source=.\SQLExpress;integrated security=true;attachdbfilename=|DataDirectory|\mydb.mdf;user instance=true;"

The "User Instance" functionality creates a new SQL Server instance on the fly during connect. This works only on a local SQL Server 2005 instance and only when connecting using windows authentication over local named pipes. The purpose is to be able to create a full rights SQL Server instance to a user with limited administrative rights on the computer. To enable the functionality: sp_configure 'user instances enabled','1' (0 to disable)

Using SQL Server 2005 Express? Don't miss the server name syntax: SERVERNAME\SQLEXPRESS (Substitute "SERVERNAME" with the name of the computer)

|||

Hi Jamie,

When you installed SQL Express, you installed the server onto your computer. SQL Express installs by default to something called a named instances, which is just the way we refer to the name of the server. As long as you didn't change anything when you were installing, the name of your SQL Express instance is "SQLEXPRESS". When connecting to SQL Server, you have to specify both the machine name and the instance name, in the format <machine name>\<instance name>. In cases where you are connecting to a SQL Server that is on the same machine that your are logged into, you can replace the <machine name> part with either the word "(local)" or with a period "." as form of short hand. So, in order to connect to the default copy of SQL Express on the computer you are logged into, you would put the following in the Server name text box:

(local)\SQLEXPRESS

Normally, SQL Express uses Windows Authentication, which means that SQL will recognize the same user account that you use when logging onto Windows. If you did not change anything when you installed SQL Express, you should just be able to select Windows Authentication and SQL Express will recognize you without providing any additional user name or password.

Hope this helps,

Mike

|||Hi Michael,

I love your messages! You are excellent

at explaining answers to problems and queries for beginners.

You're the TOP answer provider on the MSDN site in terms of

quality! Thank you!

For your information, this query is probably a popular one due to that

lack of explanation on the SQL video lesson05. He simply assumes

that you can click on the "Connect" button without any explanation

about server name etc - and any beginner will, of course, probably be

opening SQL Server Management for the first time, so therefore would

require this information to continue further.

Like Me!!!

However, following your instructions, I now have another error message

that, according to your information re local connections sounds bizzaar.

I typed in:

(local)SQLEXPRESS

I left "Windows Authentication" as is.

And clicked connect.

The User Name came up with:

YOUR-6202AC0500\user

(which I vaguely recognise as seen somewhere else and appears to

describe my PC.) My directory for "Documents and Settings" is

"user's Documents" (I obviously haven't named my PC) and the owner is

Fran Smith (in case this is relevant) - sorry - as mentioned, beginner.

The error says the following:

Connect to Server

Cannot connect to (localSQLEXPRESS)

Additional Information:

An error has occurred while establishing a connection to the

server. When connecting 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)(Microsoft

SQL Server, Error: 53)

There's a little "Show Technical Details" icon at the bottom of the

error message, which I clicked on which provided a "For Help:" http

link. This took me to a page that began "We're sorry.

There's no additional information...". The "Help" icon took me to

the same page.

Why is it seemingly attempting to connect to a remote server when a)

I've specified local and b) it has also even found my PC user

name? What do I do to correct this. I did install it

accepting the defaults provided.

Thank you in advance.

I'm now a little frustrated. I have began the video sequences

(which is a fabulous learning tool because it is explained WHY etc, not

just click here/do this as the written tutorials tend to do); however I

am stuck awaiting answers to all three sequences:

VB - on the

databinding issue: I read the other forums etc, and found the

basic problem regarding the two databases/saving to only the

one/debugging overwrites etc, but I wanted to know how then, do we save

to the actual database, how and when does this occur, if not at that

time? refer VBLesson09.

VWD - userCount

doesn't work for me - either in FireFox (where it doesn't increment) or

in IE7 (where it continues to increment each time a window is

refreshed). refer VWDLesson03

And now, SQL Lesson05.

My other username is BasilTabethaCat. These have been outstanding

for 3 and 2 days respectively, with no reply attempts or answers.

How do I invoke an answer?

I am now stuck as I would rather not continue the learning process

while I have a hole in my understanding (I am a student teacher - so

I'm well informed on the pitfalls of this!)

HELP!!

Cheers,

Fran...

PS I meant the compliment above - your answers in several areas have helped me a lot!