Conlidate databases for multiple installations

1. install a SQL Express instance such as myexpress;

2. create some databases with tables such as db1 and db2;

3. Reinstall SQL Express with the same instance name "myexpress". I assume we need reinstall SQL Express myexpress again becuase of bad operations.

4. Open the myexpress by management tool but I can not see db1 and db2 databases but the datafiles and logfiles are in the data directory.

The question is what I need to do so I can consolidate exited databases so they can be seen in "myexpress" instance by management tool?

Hmmm it seems it has nothing to do with Team System, I would recommend you to ask this in the SQL Server forums, in which you will get more help for sure, sorry and good luck.

I also think the step you are not doing is an attach of the databases.

Confused about MSSQL Express installations

I have this confusion because as I am trying to install "SQL Server Management Studio Express", the installers said I already have it.

Q1. Do I need it if I already have SQL Server Management Studio for Server 2005?

Q2.

How many ways to have SQL Express installed on your PC?

- Seperate downloads

- Visual Studio 2005 Retail

- SQL Server 2005

In that regards, will all methods are basically install the same set of components into the machine?

Q3. I don't find any relevant item in the "Add or Remove Programs" regarding to SQL Express.

Is that because SQLExpress is just an database instance not a application item?

Q4. Where are the files of Express in the file system?

I saw in c:\Program files\Microsoft SQL Server, a few directories like

80, 90, MSSQL.1, MSSQL.2, MSSQL.3, MSSQL.3, MSSQL.4

Which one of those belongs to SQL Express and which belongs to SQL Server 2005?

Is the directory structure identical with other types of installation (standalone and VS IDE)?

Thanks

Stanley

If you have the full version of SQL Management studio the installer will not allow you to install the express version as it is already installed.

Each of the numbered directories refers to an instance of sql server 2005 installed on the system. The engine tool and shared files are stored inside the version directories ie 80 or 90... where 80 is sql server 2000 and 90 is sql server 2005.

|||I too have had problems re the above. I uninstalled what I had, and then reinstalled my first download of SQLexpress. I configured (re help), added in online books, searched for answers re an interface and found something on dnncreative forum re the management download. This time I was able to install it.

Sorry for not being too specific, but it all became a blurr. Perhaps you could try without configuring, if that doesnt work, youll find what you need to know online amongst the configuring ...

Conflict with logins/usres when Importing databases

Hi,

We have imported several databases from an old SQL Server 2000 deployment in a SQL Server 2005 instance. After the installations we have check that the import doesn't create the logins associated with the users nad now it seems impossible to create "manually" the login. What should be do? Re-import the database after having created the login?

Thanks
You should still be able to create the login using CREATE LOGIN and then run the system proc
sp_change_users_login to map the existing users to the newly created login.

Reimporting the database will probably not work as the SIDs of the new logins will not match those of the old logins.

HTH.
|||Effectively, we have been able to create the login but we are unable to associate it to the user using the the "User Properties". The field "Login" appears empty and disabled, so there is no way to assign a user from this screen.

Reading your answer I understand that I can map the users to the newly created logins using the sp_change_users_login function. It's true? Could you send me a sample of use of this function? How should we execute it? (We are SQL Server newbies coming from Oracle world......)+

Thanks
|||

I assume you imported only your user-database probably using import wizard or something. Security information (users and logins) is stored in 'master' database in SQL Server world. You have to transfer these information from your old database to new one.

Check this out.

How to transfer logins and passwords between instances of SQL Server

http://support.microsoft.com/kb/246133/en-us

|||sample:

sp_change_users_login 'AUTO_FIX', 'some_login'

|||Check the information in Books Online which will give you a full explanation of the options open to you:

http://msdn2.microsoft.com/en-us/library/ms174378.aspx

Essentially to map an existing user Bob to a new login of Bob you're looking at running:

sp_change_users_login 'Update_One', 'Bob', 'Bob';

Hope this helps;