Question to Thread " Usage of Association Rules"

"If you have a pressing need for this fix, please contact our customer support team."

Yes I have a pressing need for this fix, where I have to contact your customer support team. How do I do that?

You know I only have the evaluation version of SQL Server, but I have to show that this programm is good enough to solve Association Analysis. If I can not show this it wouldn't be bought. Please help me.

TNX

Answered on other thread - http://support.microsoft.com

In this case, contact me at jamiemac "at" microsoft.com

Question on Report Builder/Designer

I have Visual Studio 2005 Team Developer. I don't need SQL2005 since I have SQL2000. How do I get Report Designer/Builder for VS2005? I would like to use the Report Designer/Builder to build reports for Windows applications. Do I HAVE to buy SQL 2005?

Thanks.

Reporting services is an add-on for SQL 2000, but it is available. You can download a 120-day evaluation version here:

http://www.microsoft.com/downloads/details.aspx?familyid=BA517C01-2E2F-4BC7-84AF-149B7637F807&displaylang=en

|||

I don't want SQL2000 I already have SQL2000. What I want to find is the Report Builder/Designer to use with VB programs within Windows. It is suppose to plug into Visual Studio 2005 which I have but I don't want to spend the money for SQL2005 just to get the plug in. I don't need Report Server just the Report Designer/Builder.

Jim

|||Report Builder is included with Reporting Services. For example, when I load my SQL Server 2005 Reporting Services site and click Build Reports, it launches the Report Builder.|||

It is also an snap-in to Visual Studio. Everything I have read is that you use it to develop reports for Windows Apps, which is what I want to do. I don't use SQL as a database generally. I normally use Access because they are small apps. But I would like to use the Report Builder/Designer to develop these app reports. That is where I'm trying to get to.

If I can get Report Builder/Designer into Visual Studio2005 then I can write reports for Windows Apps which they say you can do and is a replacement for Crystal. Also that you don't need SQL or SSRS to do this.

I just don't know where to get the snap/plug-in.

Question on Deployment

hello everyone,

I have a question on deployment of SSIS.

My team plans to develop a lot of SSIS packages.

I want my deployment environment to be as centralized as possible, but the processing environment to be distributed.

Here is what I had in mind. I have one server running SQL Server DB and SQL Server Agent. I have all the SSIS packages deployed on this server and schedule them as jobs in SQL Server Agent.

Now I have two other machines just running SSIS service (no other component). When the agent executes the packages, he should use either of the two machines. (Load balancing would be good, or I can manually assign the packages to the machines too).

is this possible? recommended?

Another approach would be that each SSIS Server, also has SQL Server and Agent installed. And respective packages are installed and scheduled on their respective servers. But here I have to maintain the packages and schedules on 2 machines.

regards,
Abhishek.

MSDN Student wrote:

hello everyone,

I have a question on deployment of SSIS.

My team plans to develop a lot of SSIS packages.

I want my deployment environment to be as centralized as possible, but the processing environment to be distributed.

Here is what I had in mind. I have one server running SQL Server DB and SQL Server Agent. I have all the SSIS packages deployed on this server and schedule them as jobs in SQL Server Agent.

Now I have two other machines just running SSIS service (no other component). When the agent executes the packages, he should use either of the two machines. (Load balancing would be good, or I can manually assign the packages to the machines too).

is this possible? recommended?

Another approach would be that each SSIS Server, also has SQL Server and Agent installed. And respective packages are installed and scheduled on their respective servers. But here I have to maintain the packages and schedules on 2 machines.

regards,
Abhishek.

You cannot execute packages remotely so the first scenario you outlined is not possible.

-Jamie

|||

OK. How about this one

On one machine I have SQL Server installed where I deploy all my SSIS packages. On the other two machines I have SQL Agent and SSIS Service installed.

The two machines will read the common SQL Server repository to read SSIS packages and execute them on the respective machines.

I will still be able to keep all the packages in one central SQL Server location, but I will have to configure the SQL Jobs on both the SSIS servers.

Will this work?

regards,
Abhishek.

|||

Yep, that will work fine.

I have to ask why do you want to do this? Unless you are re-using exactly the same (version) package across several machines, it seems like the central dependency doesn't offer that much.