|
The connection string was missing the password attribute because you hadn't checked the "Allow saving password" checkbox in the Data Link Properties dialog, and you were not using NT integrated security (this is assuming use of the OLEDB Provider for SQL Server, since providers differ on the connection info they gather). "Saving the password" means that the final connection string built and used by the Object Mapper contains all information required to connect to the database server.
If you use NT Integrated security, your Windows userid must have permissions to the SQL Server and the database objects. The connection string will not contain user/password information, but instead contain the attribute "Integrated Security=SSPI". It will look something like this:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=IdeaBladeTutorial;Data Source=.
If you use SQL Server authentication, both userid and password should be present, and your connection string will look something like this:
Provider=SQLOLEDB.1;Persist Security Info=True;User ID=kim;Password=kim;Initial Catalog=IdeaBladeTutorial;Data Source=.
The SQL login id used by the Object Mapper - whether using integrated security or SQL security - does not require admin rights. It requires permission to connect, and query permission on the database objects to be mapped. It's frequently easier to login with an admin user id, particularly when doing development work, but it is not required.
|