scjp1.6,scwcd1.5:)!!!
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
scjp1.6,scwcd1.5:)!!!
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
scjp1.6,scwcd1.5:)!!!
Tim Holloway wrote:
One thing that's different about SQL server is that tcp/ip access to the database is turned off by default. Probably a response to the infamous "SQL Slammer" web attacks of several years back. So you (or the DBA) have to go into the SQL server control panel and enable it. Also, if the SQL server is a separate machine, you may have to open up firewall port 1433 tcp.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
scjp1.6,scwcd1.5:)!!!
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:There's not much more I can say, since I haven't done this for a while and I no longer remember all the details.
However, if the SQL Server is on a different machine, make sure that there are no firewalls blocking access of tcp port 1433 between DB client and DB server.
The SQL Server settings are tricky. I believe that you have to set options carefully or tcp connections will be listened for on a floating port ID instead of always at 1433. You may also have to set access permissions to allow the DB client machine to connect. However this part is stuff that I don't remember very well. All I do remember is that it's a real nuisance to set up.
scjp1.6,scwcd1.5:)!!!
sumedha rao wrote:
Tim Holloway wrote:There's not much more I can say, since I haven't done this for a while and I no longer remember all the details.
However, if the SQL Server is on a different machine, make sure that there are no firewalls blocking access of tcp port 1433 between DB client and DB server.
The SQL Server settings are tricky. I believe that you have to set options carefully or tcp connections will be listened for on a floating port ID instead of always at 1433. You may also have to set access permissions to allow the DB client machine to connect. However this part is stuff that I don't remember very well. All I do remember is that it's a real nuisance to set up.
what should the username and password be while specifying a new database connection??
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
scjp1.6,scwcd1.5:)!!!
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |