Can I use MS SQL Server Express 2005 in Visual Studio 2003?

I have been experiencing troubles since I was decided to install SQL Server Expr 2005 in my PC, first I needed to remove the .NET framework 1.1 in my computer because it is suggested before installing sql server expr 2k5 that cause my vs.net 2003 to stop loading because sql express runs in .NET framework 2.0 and vs.net 2003 is in .Net Framework 1.1 then what I did is to install .Net Framework 1.1 in my PC together with .Net Framework 2.0 and my vs.net started runnning again.

My problem now is when I try to connect to a database using Data Link Properties in the Server Explorer it says "[DBNETLIB][ConnectionOpen](Connect()).]Sql server does not exist or access denied." how could this happen if I can see the sql server in the Server Explorer in my VS.net environment?

Please somebody help me I am just learning to this language and I think I cannot proceed to the next few chapters remaining because of this.

Thank you very much!

Hi,

I dont think that having .Net 1.1 framework is the problem.

There is some other problem in the SQL 2005 installation or in the system.

Try this link too

|||hi kingcobra thank you for spending time for your feedback, maybe I can add you to my windows msgr list as one of my friends I would like to use my windows messenger exclusive for individuals who are specialized in computer and if ever you are the first to be included.thank you friend.

Anyway I removed my sql 2k5 express and installed the old MSDE 2k A I havent tried it yet but there is an icon in my windows taskbar says running \\"My server"\"My instance" - MSSQLServer. thank you friend|||

The issue is not the .Net Framework 1.1, in fact, you must have the .NET Framework 1.1 installed in order for VS 2003 to function, which I think you discovered.

The problem is that the designers in VS 2003 are not compatible with SQL 2005, they only support earlier versions of SQL, i.e. 2000. This was a design decision and is caused by structural changes in the SQL 2005 database format. You can still connect to SQL 2005 programatically from within a program written using VS 2003, but all of the UI designers will be non-functional. At this time, only the VS 2005 designer work for SQL 2005.

Your options to get working designers are:

Move to the VS 2005 environment

Download SQL Server Management Studio Express Edition

|||Sir Mike:

Hi there thank you for the explanation that's a concrete explanation that's what I am looking for.Thank you...as of now I am temporarily using Visual Web Dev. 2k5 express until I find an installer of vs 2k5.thank yah. reply with your messenger id pls I will add you to my list.thanks

Can I use business objects as a data source?

We have decided to use business objects in our new application, which seems to be working well, since they can be used as a binding source for grids, etc.

I am trying to evaluate whether SSIS is a practical solution for our ETL requirements. The problem is, I can't find any examples or references, or even the slightest hint that anyone is using them with business objects. Any attempts to search yield a ton of results which are based on a commercial product called "Business Objects" rather than the design pattern.

It is currently a requirement of our development team that all data access must be done via business objects, rather than communicating directly with the database.

Can anyone provide some more information (besides just suggesting I write a custom connection manager)? Is there anyone who has actually made SSIS work with business objects?

Thanks, Richard

What is a "business object"?|||I don't know what kind of information you're looking for. Yes, it can be done. Yes, you'll have to write custom components to talk to the business objects instead of the database. I've done it for Reporting Services as a custom data extension (source) and it wasn't a bunch of fun. SSIS I think would be even less. Biggest downside I can think of off-hand is that you won't be able to bulk load into the database (think row-by-row), which is going to be really painful in an ETL scenario. I've never heard of an ETL process that wasn't allowed to access the database directly.
|||I'd concur with Jay's assessment. I've done some similar work in the past. Business objects are usually not very efficient for accessing large amounts of data. If your data movement is going to be on an individual row basis, I'm not sure SSIS is the best option for implementing it.|||

We are a 3PL, so in our case, ETL is more along the lines of importing batches of orders and exporting batches of shipping confirmations from and to a variety of data formats. Row-by-row is not an issue.

It would be nice to find a working example of how to do this prior to investing a bunch of time into SSIS.

|||This sounds more like BizTalk than SSIS. It isn't your business objects that I'd be concerned about in SSIS, it's the "variety of data formats". SSIS wants to move 10,000+ rows per second between well-defined sources and destinations and do a bunch of transformations along the way. BizTalk wants to route transactions between different systems and talk different formats to each one.
|||

BizTalk has a price tag. We already have SSIS. Everything I've read to date on it indicates that it is something we should be able to use to meet our needs. I am not questioning whether SSIS is the best choice. I would like to know if anyone has used it successfully with business objects, and if so, can they provide some examples, or other helpful information.

Thanks, Richard.

|||What will your business objects be constructed as? COM objects, web services, .NET assemblies? That has an impact on how easy they are to interface with.|||

SSIS Evaluator wrote:

BizTalk has a price tag. We already have SSIS. Everything I've read to date on it indicates that it is something we should be able to use to meet our needs. I am not questioning whether SSIS is the best choice. I would like to know if anyone has used it successfully with business objects, and if so, can they provide some examples, or other helpful information.

Thanks, Richard.

Can I reiterate Phil's question (above)? What exactly are these "business objects"?

-Jamie

|||

It's a generic term for objects that represent business entities and the rules associated with those entities. So you might have a Customer business object, with all the attributes that a customer has, and methods to represent any operations that can be performed on the customer. Usually, these provide a layer of abstraction between the database and the user interface. Business objects know where their data is stored for persistence, and user interfaces request information from the business objects rather than accessing the database directly. Changes in the data from the UI are also handled through the business object. Data validation, enforcement of business rules, etc, are all handled in the business object.

In the OP's case, evidently they have made an architectural decision that all data access has to go through these business objects. As has been stated, it is possible to do this with SSIS. The degree of complexity depends in large part on how the business objects are implemented. If this is being looked at a method to handle importing or exporting data from business objects to an external database, it might work OK, assuming performance is not the major concern. If it is for business object to business object communication, I really think the OP would be better off investigating other tools.