Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am a SQL Server newbie. I imported a package stored on my filesystem into my SQL Server 2008R2 database. Later on I deleted the package from the file system. However the package continues to remain in the SQL Server database and even executes!
What little I know implies this should not happen since even SQL Server will be referring to that package stored in the filesystem. So my question is: is this behaviour normal? If not what could be the possible reason for it
Cheerio
After much pondering and asking some serious sql-savvy people I feel this behaviour it pretty much natural. The two folders have been created just to distinguish amongst the sources from where the packages were obtained. Once imported the package is saved in the database. Then it’s location does not matter much. In my example, a copy of the package is created and stored in the database.
Thank you all for your help and time 🙂