[web2py] Re: mssql connection URGENT!

2015-02-02 Thread Omi Chiba
Thank you for the reply. I found that that problem was why it doesn't 
accept IP Address instead of Named Instance and fixed the SQL Server 
configuration to use static IP to connect SQL Server. 

I can't connect to my servers SQL database via an IP Address
http://dba.stackexchange.com/questions/62165/i-cant-connect-to-my-servers-sql-database-via-an-ip-address

Problem Solved!

On Monday, February 2, 2015 at 1:33:35 PM UTC-6, Massimo Di Pierro wrote:

 The problem is that since you did not specify a name for the .table files 
 you get default (nobody does). default is a hash of the db uri so if you 
 change it the .table files break. If this is just a change in the name but 
 the tables are already in the database, the you should enable a 
 fake_migration (
 http://www.web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#migrate--fake_migrate)
  
 so that new .table files are created. If this is a new database, you need 
 to enable migrations (I see they are disabled for you). Make sure you do 
 not change the database schema until this is resolved else there is no way 
 for me to tell in which state you db and your .table are.

 Massimo

 On Monday, 2 February 2015 08:29:23 UTC-6, Omi Chiba wrote:

 The below connection statement was working fine and the SQL Servers's 
 instance was HELPDESK/HELPDESK.

 dbh = DAL(mssql2://username:password@HELPDESK/HS2000CS, 
 migrate_enabled=False)

 Now, our vendor change the name of instance to  HELPDESK/HELPDESK_VM.

 I tried, 
 dbh = DAL(mssql2://username:password@[HELPDESK/HELPDESK_VM]/HS2000CS, 
 migrate_enabled=False)
 dbh = DAL(mssql2://username:password@10.30.6.222/HS2000CS, 
 migrate_enabled=False)

 SQL Server is in our local network and 10.30.6.222 is the local ip 
 address.

 but both doesn't work.

 It's in production and I need to fix in a few hours. Please help!



-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
web2py-users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[web2py] Re: mssql connection URGENT!

2015-02-02 Thread Omi Chiba
Thanks!

On Monday, February 2, 2015 at 3:06:05 PM UTC-6, Niphlod wrote:

 uhm. Technically having more than one instance of mssql running on the 
 same ip is possible (multiple named instances) but it involves a totally 
 different connection handshake. 
 If you don't specify different port numbers, you can still have them 
 dynamic but you have to resort to have SQL Server Browser running on the 
 server and specifying a connection using the odbc connectionstring 
 notation (mssql://{Driver={SQL 
 Server};Server=hostname\instancename;..}), that will trigger that new 
 handshakeeverything works fine, I use it every day.


-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
web2py-users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[web2py] Re: mssql connection URGENT!

2015-02-02 Thread Niphlod
uhm. Technically having more than one instance of mssql running on the same 
ip is possible (multiple named instances) but it involves a totally 
different connection handshake. 
If you don't specify different port numbers, you can still have them 
dynamic but you have to resort to have SQL Server Browser running on the 
server and specifying a connection using the odbc connectionstring 
notation (mssql://{Driver={SQL 
Server};Server=hostname\instancename;..}), that will trigger that new 
handshakeeverything works fine, I use it every day.

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
web2py-users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[web2py] Re: mssql connection URGENT!

2015-02-02 Thread Massimo Di Pierro
The problem is that since you did not specify a name for the .table files 
you get default (nobody does). default is a hash of the db uri so if you 
change it the .table files break. If this is just a change in the name but 
the tables are already in the database, the you should enable a 
fake_migration 
(http://www.web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#migrate--fake_migrate)
 
so that new .table files are created. If this is a new database, you need 
to enable migrations (I see they are disabled for you). Make sure you do 
not change the database schema until this is resolved else there is no way 
for me to tell in which state you db and your .table are.

Massimo

On Monday, 2 February 2015 08:29:23 UTC-6, Omi Chiba wrote:

 The below connection statement was working fine and the SQL Servers's 
 instance was HELPDESK/HELPDESK.

 dbh = DAL(mssql2://username:password@HELPDESK/HS2000CS, 
 migrate_enabled=False)

 Now, our vendor change the name of instance to  HELPDESK/HELPDESK_VM.

 I tried, 
 dbh = DAL(mssql2://username:password@[HELPDESK/HELPDESK_VM]/HS2000CS, 
 migrate_enabled=False)
 dbh = DAL(mssql2://username:password@10.30.6.222/HS2000CS, 
 migrate_enabled=False)

 SQL Server is in our local network and 10.30.6.222 is the local ip address.

 but both doesn't work.

 It's in production and I need to fix in a few hours. Please help!



-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
web2py-users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.