Linker IT Software
Google
Web www.oraxcel.com
menubar-top-links menubar-top-rechts
Home Help Search Login
Welcome, Guest. Please Login.
SQL*XL: Database to Excel bridge litLIB: Excel power functions pack ExcelLock: Locking and securing your valuable Excel spreadsheets encOffice: Protect your Excel file easy and safe encOffice: Protect your Excel file easy and safe
Pages: 1
SQL Server test and production databases (Read 10646 times)
Gerrit-Jan Linker
YaBB Administrator
*****




Posts: 75
SQL Server test and production databases
27.12.08 at 11:16:13
 
SQL Server test and production databases
 
Quote:
Have a bit of a hitch I am hoping you can help with. We have a test server and a production server. Each of the dbs are called the same thing. When I try to create a connection for one or the other, the first one sets up and connects just fine. The second connection does not configure. I am guessing since the db names are the same this is an issue? They are on different servers, IP's, and have different pw's. However the db name and login user account are the same.
Is there a way around this without major changes to SQLServer?

If not I can put one on one box and the other on another box and just access the db's from different machine. I have both a laptop and a desktop.
Back to top
 
 

Gerrit-Jan Linker
Linker IT Software
Email WWW Gerrit-Jan Linker   IP Logged
Gerrit-Jan Linker
YaBB Administrator
*****




Posts: 75
Re: SQL Server test and production databases
Reply #1 - 27.12.08 at 11:16:46
 
Interesting!
 
What would help me to investigate the possibilities is the following. Can you sennd the connection strings for both connections?
 
I know you cannot configure both connections but perhaps you can create one, copy the connection string, delete the connection to do the same for the second connection.  
 
The connection string can be copied from the editor that is started with the edit button on the connection hostory list.
Back to top
 
 

Gerrit-Jan Linker
Linker IT Software
Email WWW Gerrit-Jan Linker   IP Logged
Gerrit-Jan Linker
YaBB Administrator
*****




Posts: 75
Re: SQL Server test and production databases
Reply #2 - 27.12.08 at 11:18:27
 
Quote:
One is called staging, the other production.

Staging:
Driver={SQL Server}; Server=SLCIWAP8\YUKON; Database=MyDatabase; Uid=; Pwd=

Production:
Driver={SQL Server}; Server=slciaccdb; Database=MyDatabase;
Trusted_Connection=yes

I note that there slight differences.

I copied the connection string from the current available which in this
case was production. Went to the New Connection/Connection String
Editor, pasted the connection string, edited for the appropriate db. It
configured but still did not display it in the history list.
Interesting. I could send some screen shots if you would like.
Back to top
 
 

Gerrit-Jan Linker
Linker IT Software
Email WWW Gerrit-Jan Linker   IP Logged
Gerrit-Jan Linker
YaBB Administrator
*****




Posts: 75
Re: SQL Server test and production databases
Reply #3 - 27.12.08 at 11:19:13
 
The problem is simply that it checks that the user and database is unique. If it finds another connection with the same user and database it will replace the connection. Perhaps I should do something else there.  
 
I will review it and see what I can do.
Back to top
 
 

Gerrit-Jan Linker
Linker IT Software
Email WWW Gerrit-Jan Linker   IP Logged
Gerrit-Jan Linker
YaBB Administrator
*****




Posts: 75
Re: SQL Server test and production databases
Reply #4 - 27.12.08 at 11:22:21
 
This is one workaround. I noticed I am connecting through OLE DB (SQLOLEDB) myself. My databases are listed as server\database. This would be a workaround to your problem. My connection string is:
 
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=gjlinker;Initial Catalog=littest;Data Source=VM-SQL2005XP\SQLEXPRESS
Back to top
 
 

Gerrit-Jan Linker
Linker IT Software
Email WWW Gerrit-Jan Linker   IP Logged
Gerrit-Jan Linker
YaBB Administrator
*****




Posts: 75
Re: SQL Server test and production databases
Reply #5 - 27.12.08 at 12:00:30
 
I have made a code change to display the database name for SQL Server databases as server\sqlserver instance\database.
 
When I connect using a connection string as:
Driver={SQL Server}; Server=VM-SQL2005XP\SQLEXPRESS; Database=littest;
 
the connection shows as  
Database = VM-SQL2005XP\SQLEXPRESS\littest
 
This change will be made available in SQL*XL 4.3.12.
Back to top
 
« Last Edit: 27.12.08 at 12:02:39 by Gerrit-Jan Linker »  

Gerrit-Jan Linker
Linker IT Software
Email WWW Gerrit-Jan Linker   IP Logged
Pages: 1