Showing posts with label tools. Show all posts
Showing posts with label tools. Show all posts

Tuesday, March 20, 2012

Run SQL against SQL Server 2000 on Windows 2003 Web Edition

I have a dedicated Windows 2003 Web Edition server running SQL Server 2000.
SQL Server 2000 was pre-installed. What tools can I use to interrogate and
update the SQL Server 2000 database from the Windows 2003 Web Edition Server
?
Client and Adminstration tools are not supported and will not install on the
Web version of the 2003 operating system.Am Mon, 5 Jun 2006 04:35:02 -0700 schrieb AJ:

> I have a dedicated Windows 2003 Web Edition server running SQL Server 2000
.
> SQL Server 2000 was pre-installed. What tools can I use to interrogate an
d
> update the SQL Server 2000 database from the Windows 2003 Web Edition Serv
er?
> Client and Adminstration tools are not supported and will not install on t
he
> Web version of the 2003 operating system.
Maybe this can help you:
http://www.sqlmanager.net/en/products/mssql/manager
At the bottom you can download a free Lite-version!
bye, Helmut

Friday, March 9, 2012

Run child package independently [FOUND IT]

Hi there

I have a parent package which execute a child package. But when the child package is run from the parent not all of the tools inside is executed. I have a variable "ExecuteStep" from the parent that gives information about which tools, that needs to be executed.

BUT

The child package should be able to run independently also. In this case all tools inside the package should execute.
This is however not possible because my variable "ExecuteStep" does not exist inside the package, it is inheritage from my parent.

If I create a variable with exactly the same name inside my child package, I can run the child independently, but when executed from the parent the value from the parent package is now overwritten by the child variable.

How can I get around this problem?

bjarneThe solution was just in front of me all the time.

As "Package Configuration" I was using the XML file I had generated with the Parent variables.

Instead I should have been using "Parent package variable", this way all works fine.

I found it with a help from Kirk Haselden's blog

http://sqljunkies.com/WebLog/knight_reign/comments/5366.aspx

Bjarne

Run child package independently

Hi there

I have a parent package which execute a child package. But when the child package is run from the parent not all of the tools inside is executed. I have a variable "ExecuteStep" from the parent that gives information about which tools, that needs to be executed.

BUT

The child package should be able to run independently also. In this case all tools inside the package should execute.
This is however not possible because my variable "ExecuteStep" does not exist inside the package, it is inheritage from my parent.

If I create a variable with exactly the same name inside my child package, I can run the child independently, but when executed from the parent the value from the parent package is now overwritten by the child variable.

How can I get around this problem?

bjarneThe solution was just in front of me all the time.

As "Package Configuration" I was using the XML file I had generated with the Parent variables.

Instead I should have been using "Parent package variable", this way all works fine.

I found it with a help from Kirk Haselden's blog

http://sqljunkies.com/WebLog/knight_reign/comments/5366.aspx

Bjarne