Showing posts with label existing. Show all posts
Showing posts with label existing. Show all posts

Monday, March 26, 2012

Running a package in C#

Hello all. I am trying to run a package in C# and have come accross the help file of how to do it in Visual Basic ('Running an Existing Package using Visual Basic'). However, I cannot find a reference to anything relating to DTS in my reference dialog. In the help file it says to add a reference to Micorsoft.SQLServer.ManagedDTS.DLL, however, I cannot find this reference anywhere. Am I missing something?
Thanks,
MikeAre you using Visual Studio .NET 2005?
Visual Studio .NET 2002/2003 projects can't have references to
Microsoft.SQLServer.ManagedDTS.DLL, since it is built with .NET 2.0.
|||Sorry, yes I am running .NET 2005 June CTP.|||Have you GACd it? I'm not sure if you have to but its worth a try.

-Jamie|||Pardon my ignorance, but GAC? Not sure what you are referring to here?|||GAC stands for Global Assembly Cache. its basically where you put your assemblies that you want to use in a .net app (I think).

The default location is %windows-dir%/assembly/ I think.

-Jamie|||I haven't put any assemblies anywhere. From what I understand, the .dll that I cannot find is supposed to be one of the built in ones. It is not one that I have created. I guess it deals with running the SSIS packages. Kinda like DTSRun was for SQL 2000.
Now the one thing that I have noticed that I forgot to mention above is that my VS 2005 is running on my local box and my SQL Server Business Intelligence stuff and SQL Server 2005 is running on a different box. Not sure if this would make a differnce. I hope not, but thought I would check.|||You are correct that from a high level that DLL is used in running the packages. But your .net app doesn't know where to find that DLL so I'm guessing that you need to put it somewhere where it knows where to look for it - that place is the GAC.

Hopefully someone can confirm this. I'm not absolutely sure.

Check in your GAC to see if you can see Microsoft.SQLServer.DTSPipelineWrap

-Jamie|||Hi Jamie. Sorry to sound frustrated, just a bad morning. I guess I should clarify that I did a search on my computer and that .dll is nowhere on my machine. So I couldn't move it if I wanted to. I guess what I really need to know is at which point does that .dll get loaded? When installing SQL Server 2005 or when installing VS 2005? Like I stated earlier, my VS2005 install and my SQL Server 2005 intsall are on two seperate computers. If it is installed when SQL Server 2005 is installed, is there a way to install just the Business Intelligence without installing SQL Server?
On my computer I have absolutely NO references to ANYTHING having to do with DTS. I have even done a search for anything containing DTS in the name and nothing was found.
Sorry for being confusing. Like I said, it has been a rough morning!
Thanks for your kind help!
Tazz|||The DLL gets loaded when you install Integration Services (as far as I know).

-Jamie|||The assembly that's being discussed, Microsoft.SqlServer.ManagedDts.dll, contains the Microsoft.SqlServer.Dts.Runtime namespace and thus the Application and Package objects. It is installed by default to C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies.

I believe that this file is installed if you install Business Intelligence Development Studio only, as BIDS installs everything necessary to design and test SSIS packages, but I can't easily verify this with my own eyes at the moment.

Now that SSIS exists as a robust ETL platform, it is no longer "redistributable" in the way that DTS was, simply by copying a few DLLs to client machines.

-Doug
|||The Add Reference dialog in VS does not use the GAC, but certain other folders, known "assembly" folders that VS knows to check. There is a KB which I assume is valid for VS2005, which describes is a registry key with the folders listed. So the assembly needs to be in a VS known location, not the GAC at this stage. (Jamie remember the fun with adding a reference to a Script Task).

The DLL may be installed in the GAC as well to help it be located at run-time, and save having multiple installs etc, but that is not the issue for Add References. Obviously as has now been determined, you need to install BIDS to get the DTS/SSIS assemblies, when they will be installed suitable folders, and actually in the GAC as well.|||

Tazzmann wrote:

...is there a way to install just the Business Intelligence without installing SQL Server?
...

Yes and I have it that way.
While installing you have to select only the option to install BIDS (I forgot the exact name of the option to select, but it is something like "development tools, documentation...")

HTH,
Nitesh

Running a job at database startup

Is it possible to run a job (O/S cmd) each time a database is restarted? I
would like to automatically move the existing 'blackbox' trace(s) out of the
default folder at startup time so that they can be analyzed more
conveniently.
Hi
Look at sp_procoption with the startup parameter in BOL.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JHowell" wrote:

> Is it possible to run a job (O/S cmd) each time a database is restarted? I
> would like to automatically move the existing 'blackbox' trace(s) out of the
> default folder at startup time so that they can be analyzed more
> conveniently.
|||It is possible to have a stored procedure execute at startup. Must be in the
Master DB.
"JHowell" <JHowell@.discussions.microsoft.com> wrote in message
news:4139206F-7C3C-4F8F-8DA9-AF9280A2CC87@.microsoft.com...
> Is it possible to run a job (O/S cmd) each time a database is restarted?
I
> would like to automatically move the existing 'blackbox' trace(s) out of
the
> default folder at startup time so that they can be analyzed more
> conveniently.

Running a job at database startup

Is it possible to run a job (O/S cmd) each time a database is restarted? I
would like to automatically move the existing 'blackbox' trace(s) out of the
default folder at startup time so that they can be analyzed more
conveniently.Hi
Look at sp_procoption with the startup parameter in BOL.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JHowell" wrote:

> Is it possible to run a job (O/S cmd) each time a database is restarted?
I
> would like to automatically move the existing 'blackbox' trace(s) out of t
he
> default folder at startup time so that they can be analyzed more
> conveniently.|||It is possible to have a stored procedure execute at startup. Must be in the
Master DB.
"JHowell" <JHowell@.discussions.microsoft.com> wrote in message
news:4139206F-7C3C-4F8F-8DA9-AF9280A2CC87@.microsoft.com...
> Is it possible to run a job (O/S cmd) each time a database is restarted?
I
> would like to automatically move the existing 'blackbox' trace(s) out of
the
> default folder at startup time so that they can be analyzed more
> conveniently.

Running a job at database startup

Is it possible to run a job (O/S cmd) each time a database is restarted? I
would like to automatically move the existing 'blackbox' trace(s) out of the
default folder at startup time so that they can be analyzed more
conveniently.Hi
Look at sp_procoption with the startup parameter in BOL.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JHowell" wrote:
> Is it possible to run a job (O/S cmd) each time a database is restarted? I
> would like to automatically move the existing 'blackbox' trace(s) out of the
> default folder at startup time so that they can be analyzed more
> conveniently.|||It is possible to have a stored procedure execute at startup. Must be in the
Master DB.
"JHowell" <JHowell@.discussions.microsoft.com> wrote in message
news:4139206F-7C3C-4F8F-8DA9-AF9280A2CC87@.microsoft.com...
> Is it possible to run a job (O/S cmd) each time a database is restarted?
I
> would like to automatically move the existing 'blackbox' trace(s) out of
the
> default folder at startup time so that they can be analyzed more
> conveniently.

Wednesday, March 21, 2012

Run SQL Server 7.0 in Windows 2003

Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>

Run SQL Server 7.0 in Windows 2003

Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
Ellis
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>
|||Do you have a test environment where you could test the application as a SS 2K installation but running in 7.0 compatibility mode? I'd try it with a full blown upgrade but, if you run into problems, try again in the old 7.0 compatibility.
Sincerely,
Anthony Thomas

"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message news:OeIJSk20EHA.1204@.TK2MSFTNGP10.phx.gbl...
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...

> Dear all,
>
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using

SQL7

> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using

SQL7

> in windows 2003? Please help
>
> Best Rdgs
> Ellis
>
>

Run SQL Server 7.0 in Windows 2003

Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>|||Do you have a test environment where you could test the application as a SS
2K installation but running in 7.0 compatibility mode? I'd try it with a fu
ll blown upgrade but, if you run into problems, try again in the old 7.0 com
patibility.
Sincerely,
Anthony Thomas
--
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message new
s:OeIJSk20EHA.1204@.TK2MSFTNGP10.phx.gbl...
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So i
f
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
>
> Lately, we bought a new server to replace existing old one. Afte
r
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
>
> Best Rdgs
> Ellis
>
>

Wednesday, March 7, 2012

Run an SQL function interdatabase.

Hi all,

I have a User function created within one SQL DB (an allways existing DB), but I want to run it on DB's (with same structure: tabels, views,...) that are dinamically created (one per mount), is this possible?

ThX

NeuralCyou can write the queries in the stored proc as a generalized ones using opendatasource etc and pass the server name,databsse name as parameters but it could be very slow..

hth