 | |
Newbie - Help -Integration Services project
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#21
 
| |||
| |||
|
Re: Newbie - Help -Integration Services project -
06-25-2008
, 04:10 PM
|
Hello Dennis: If you have been using DTS in the past, you will find that SSIS is designed along the concept of Development/Production environments. Do your design work in VS 2005, then when you are done, you deploy or promote the SSIS Package to the server. From your description, it really sounds like you were making changes in VS 2005, but the *deployed* package was not changing. The two are different animals. After making changes, re-deploy (or import, or install, however you choose to do it) the finished packaged into SSIS, replacing the old one. HTH -- Todd C "Irvine, Dennis" wrote: As an update. I tried doing a "Save a copy as...." on the offending project and was able to run the copy without problems, from the SQL server manager. So I can solve my problem by saving a copy, then deleting the original project and then renaming the copy to the same name as the original. But there appears to be a bug somewhere that does not completely delete connections when saving modified projects. "Irvine, Dennis" <dennis.irvine (AT) plumasnt (DOT) com> wrote in message news:e0efzM0yIHA.2068 (AT) TK2MSFTNGP05 (DOT) phx.gbl... OK, I give up. Can not figure this out. I have an Integration Services project which runs fine in VS 2005. But when I switch to the SQL server management and connect to Integration services it gets "Connection Manager" errors. Specifically it keeps trying to connect to a database that does not exist any longer. I have removed that database from the connection manager in VS 2005 and saved the package, but it won't go away in Server Manager So, when developing the package in VS 2005 I had two databases. Lets say DB#1 and DB#2. both on the same SQL server say SERVER1 I later realized I did not need DB#2 and actually deleted the database from the server and from the connection manager in the package. I have even gone through each step in the package, one by one, to make sure there are no references to the old DB#2 database anywhere. I have even made slight modifications to the package and re-saved it. Anyway, when I go over to the Server Manager and connect to the Integration Services, my list of packages comes up. but when I try to run the package it keeps having an error in which it is trying to open the DB#2 during the validation phase. If I look at the connection manager list in the Execution window, it still shows DB#2 in the list of connections. How do I get rid of this invalid reference to an old , deleted, database connection. Any suggestions appreciated. I have run out of ideas. Thanks |
#22
| |||
| |||
|
|
Hello Dennis: If you have been using DTS in the past, you will find that SSIS is designed along the concept of Development/Production environments. Do your design work in VS 2005, then when you are done, you deploy or promote the SSIS Package to the server. From your description, it really sounds like you were making changes in VS 2005, but the *deployed* package was not changing. The two are different animals. After making changes, re-deploy (or import, or install, however you choose to do it) the finished packaged into SSIS, replacing the old one. HTH -- Todd C "Irvine, Dennis" wrote: As an update. I tried doing a "Save a copy as...." on the offending project and was able to run the copy without problems, from the SQL server manager. So I can solve my problem by saving a copy, then deleting the original project and then renaming the copy to the same name as the original. But there appears to be a bug somewhere that does not completely delete connections when saving modified projects. "Irvine, Dennis" <dennis.irvine (AT) plumasnt (DOT) com> wrote in message news:e0efzM0yIHA.2068 (AT) TK2MSFTNGP05 (DOT) phx.gbl... OK, I give up. Can not figure this out. I have an Integration Services project which runs fine in VS 2005. But when I switch to the SQL server management and connect to Integration services it gets "Connection Manager" errors. Specifically it keeps trying to connect to a database that does not exist any longer. I have removed that database from the connection manager in VS 2005 and saved the package, but it won't go away in Server Manager So, when developing the package in VS 2005 I had two databases. Lets say DB#1 and DB#2. both on the same SQL server say SERVER1 I later realized I did not need DB#2 and actually deleted the database from the server and from the connection manager in the package. I have even gone through each step in the package, one by one, to make sure there are no references to the old DB#2 database anywhere. I have even made slight modifications to the package and re-saved it. Anyway, when I go over to the Server Manager and connect to the Integration Services, my list of packages comes up. but when I try to run the package it keeps having an error in which it is trying to open the DB#2 during the validation phase. If I look at the connection manager list in the Execution window, it still shows DB#2 in the list of connections. How do I get rid of this invalid reference to an old , deleted, database connection. Any suggestions appreciated. I have run out of ideas. Thanks |
#23
| |||
| |||
|
|
Hello Dennis: If you have been using DTS in the past, you will find that SSIS is designed along the concept of Development/Production environments. Do your design work in VS 2005, then when you are done, you deploy or promote the SSIS Package to the server. From your description, it really sounds like you were making changes in VS 2005, but the *deployed* package was not changing. The two are different animals. After making changes, re-deploy (or import, or install, however you choose to do it) the finished packaged into SSIS, replacing the old one. HTH -- Todd C "Irvine, Dennis" wrote: As an update. I tried doing a "Save a copy as...." on the offending project and was able to run the copy without problems, from the SQL server manager. So I can solve my problem by saving a copy, then deleting the original project and then renaming the copy to the same name as the original. But there appears to be a bug somewhere that does not completely delete connections when saving modified projects. "Irvine, Dennis" <dennis.irvine (AT) plumasnt (DOT) com> wrote in message news:e0efzM0yIHA.2068 (AT) TK2MSFTNGP05 (DOT) phx.gbl... OK, I give up. Can not figure this out. I have an Integration Services project which runs fine in VS 2005. But when I switch to the SQL server management and connect to Integration services it gets "Connection Manager" errors. Specifically it keeps trying to connect to a database that does not exist any longer. I have removed that database from the connection manager in VS 2005 and saved the package, but it won't go away in Server Manager So, when developing the package in VS 2005 I had two databases. Lets say DB#1 and DB#2. both on the same SQL server say SERVER1 I later realized I did not need DB#2 and actually deleted the database from the server and from the connection manager in the package. I have even gone through each step in the package, one by one, to make sure there are no references to the old DB#2 database anywhere. I have even made slight modifications to the package and re-saved it. Anyway, when I go over to the Server Manager and connect to the Integration Services, my list of packages comes up. but when I try to run the package it keeps having an error in which it is trying to open the DB#2 during the validation phase. If I look at the connection manager list in the Execution window, it still shows DB#2 in the list of connections. How do I get rid of this invalid reference to an old , deleted, database connection. Any suggestions appreciated. I have run out of ideas. Thanks |
#24
| |||
| |||
|
|
Hello Dennis: If you have been using DTS in the past, you will find that SSIS is designed along the concept of Development/Production environments. Do your design work in VS 2005, then when you are done, you deploy or promote the SSIS Package to the server. From your description, it really sounds like you were making changes in VS 2005, but the *deployed* package was not changing. The two are different animals. After making changes, re-deploy (or import, or install, however you choose to do it) the finished packaged into SSIS, replacing the old one. HTH -- Todd C "Irvine, Dennis" wrote: As an update. I tried doing a "Save a copy as...." on the offending project and was able to run the copy without problems, from the SQL server manager. So I can solve my problem by saving a copy, then deleting the original project and then renaming the copy to the same name as the original. But there appears to be a bug somewhere that does not completely delete connections when saving modified projects. "Irvine, Dennis" <dennis.irvine (AT) plumasnt (DOT) com> wrote in message news:e0efzM0yIHA.2068 (AT) TK2MSFTNGP05 (DOT) phx.gbl... OK, I give up. Can not figure this out. I have an Integration Services project which runs fine in VS 2005. But when I switch to the SQL server management and connect to Integration services it gets "Connection Manager" errors. Specifically it keeps trying to connect to a database that does not exist any longer. I have removed that database from the connection manager in VS 2005 and saved the package, but it won't go away in Server Manager So, when developing the package in VS 2005 I had two databases. Lets say DB#1 and DB#2. both on the same SQL server say SERVER1 I later realized I did not need DB#2 and actually deleted the database from the server and from the connection manager in the package. I have even gone through each step in the package, one by one, to make sure there are no references to the old DB#2 database anywhere. I have even made slight modifications to the package and re-saved it. Anyway, when I go over to the Server Manager and connect to the Integration Services, my list of packages comes up. but when I try to run the package it keeps having an error in which it is trying to open the DB#2 during the validation phase. If I look at the connection manager list in the Execution window, it still shows DB#2 in the list of connections. How do I get rid of this invalid reference to an old , deleted, database connection. Any suggestions appreciated. I have run out of ideas. Thanks |
#25
| |||
| |||
|
|
Hello Dennis: If you have been using DTS in the past, you will find that SSIS is designed along the concept of Development/Production environments. Do your design work in VS 2005, then when you are done, you deploy or promote the SSIS Package to the server. From your description, it really sounds like you were making changes in VS 2005, but the *deployed* package was not changing. The two are different animals. After making changes, re-deploy (or import, or install, however you choose to do it) the finished packaged into SSIS, replacing the old one. HTH -- Todd C "Irvine, Dennis" wrote: As an update. I tried doing a "Save a copy as...." on the offending project and was able to run the copy without problems, from the SQL server manager. So I can solve my problem by saving a copy, then deleting the original project and then renaming the copy to the same name as the original. But there appears to be a bug somewhere that does not completely delete connections when saving modified projects. "Irvine, Dennis" <dennis.irvine (AT) plumasnt (DOT) com> wrote in message news:e0efzM0yIHA.2068 (AT) TK2MSFTNGP05 (DOT) phx.gbl... OK, I give up. Can not figure this out. I have an Integration Services project which runs fine in VS 2005. But when I switch to the SQL server management and connect to Integration services it gets "Connection Manager" errors. Specifically it keeps trying to connect to a database that does not exist any longer. I have removed that database from the connection manager in VS 2005 and saved the package, but it won't go away in Server Manager So, when developing the package in VS 2005 I had two databases. Lets say DB#1 and DB#2. both on the same SQL server say SERVER1 I later realized I did not need DB#2 and actually deleted the database from the server and from the connection manager in the package. I have even gone through each step in the package, one by one, to make sure there are no references to the old DB#2 database anywhere. I have even made slight modifications to the package and re-saved it. Anyway, when I go over to the Server Manager and connect to the Integration Services, my list of packages comes up. but when I try to run the package it keeps having an error in which it is trying to open the DB#2 during the validation phase. If I look at the connection manager list in the Execution window, it still shows DB#2 in the list of connections. How do I get rid of this invalid reference to an old , deleted, database connection. Any suggestions appreciated. I have run out of ideas. Thanks |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.