Dear all,
I have a problem right now. We got a production server running. Now we want
to setup an another identical database at a remote office. The problem is
that replication can't be done between the two offices. To make sure the
remote office will have as much data as the production server. What shall I
do?
Help!!!!Hi
backup/restore commands. (see in BOL)
"big tony" <bigtony@.discussions.microsoft.com> wrote in message
news:C9CD538F-05AD-4CE4-8A87-45EAFEAEE024@.microsoft.com...
> Dear all,
> I have a problem right now. We got a production server running. Now we
want
> to setup an another identical database at a remote office. The problem is
> that replication can't be done between the two offices. To make sure the
> remote office will have as much data as the production server. What shall
I
> do?
> Help!!!!
Showing posts with label office. Show all posts
Showing posts with label office. Show all posts
Wednesday, March 28, 2012
help on SQL server backup!
Dear all,
I have a problem right now. We got a production server running. Now we want
to setup an another identical database at a remote office. The problem is
that replication can't be done between the two offices. To make sure the
remote office will have as much data as the production server. What shall I
do?
Help!!!!Hi
backup/restore commands. (see in BOL)
"big tony" <bigtony@.discussions.microsoft.com> wrote in message
news:C9CD538F-05AD-4CE4-8A87-45EAFEAEE024@.microsoft.com...
> Dear all,
> I have a problem right now. We got a production server running. Now we
want
> to setup an another identical database at a remote office. The problem is
> that replication can't be done between the two offices. To make sure the
> remote office will have as much data as the production server. What shall
I
> do?
> Help!!!!
I have a problem right now. We got a production server running. Now we want
to setup an another identical database at a remote office. The problem is
that replication can't be done between the two offices. To make sure the
remote office will have as much data as the production server. What shall I
do?
Help!!!!Hi
backup/restore commands. (see in BOL)
"big tony" <bigtony@.discussions.microsoft.com> wrote in message
news:C9CD538F-05AD-4CE4-8A87-45EAFEAEE024@.microsoft.com...
> Dear all,
> I have a problem right now. We got a production server running. Now we
want
> to setup an another identical database at a remote office. The problem is
> that replication can't be done between the two offices. To make sure the
> remote office will have as much data as the production server. What shall
I
> do?
> Help!!!!
help on SQL server backup!
Dear all,
I have a problem right now. We got a production server running. Now we want
to setup an another identical database at a remote office. The problem is
that replication can't be done between the two offices. To make sure the
remote office will have as much data as the production server. What shall I
do?
Help!!!!
Hi
backup/restore commands. (see in BOL)
"big tony" <bigtony@.discussions.microsoft.com> wrote in message
news:C9CD538F-05AD-4CE4-8A87-45EAFEAEE024@.microsoft.com...
> Dear all,
> I have a problem right now. We got a production server running. Now we
want
> to setup an another identical database at a remote office. The problem is
> that replication can't be done between the two offices. To make sure the
> remote office will have as much data as the production server. What shall
I
> do?
> Help!!!!
sql
I have a problem right now. We got a production server running. Now we want
to setup an another identical database at a remote office. The problem is
that replication can't be done between the two offices. To make sure the
remote office will have as much data as the production server. What shall I
do?
Help!!!!
Hi
backup/restore commands. (see in BOL)
"big tony" <bigtony@.discussions.microsoft.com> wrote in message
news:C9CD538F-05AD-4CE4-8A87-45EAFEAEE024@.microsoft.com...
> Dear all,
> I have a problem right now. We got a production server running. Now we
want
> to setup an another identical database at a remote office. The problem is
> that replication can't be done between the two offices. To make sure the
> remote office will have as much data as the production server. What shall
I
> do?
> Help!!!!
sql
Friday, March 9, 2012
Help Needed Configuring ODBC
In the Office we have a Win2000 Server running MS SQL Server 2000. I know
the servers external IP address (xxx.xxx.xxx.xxx) and we have a sub-domain
set up (subname.mycompserver.com). I have a login and password into the
server as well as the SQL login and password. The firewall is open on port
1433. From my office PC, I can access SQL, using ODBC, with Access or my
Perl programs.
At home, I'm running WinXP Pro. Although it shouldn't have been necessary,
I installed MS SQL Server client. I connect to the Internet using a Comcast
cable modem and do not have a static IP address. Whenever I try to set up
ODBC to access my office's SQL server using ODBC Data Source Administrator
/ Add SQL Server, it fails with the following error message:
Connection Failed
SQL State: '01000'
SQL Server Error: 10060
[Microsoft][ODBC Server Driver][TCP/IP Sockets]Connection Open (Connect())
Connection Failed:
SQL State: '08001'
SQL Server Error: 17
[Microsoft][ODBC Server Driver][TCP/IP Sockets]SQL Server does not exist or
access denied.
Is it possible to establish this ODBC connection into SQL and, if so, what
am I doing wrong. Thanks.
Fred
Hello Fred,
The only thing I can think is that firewall at your work is blocking 1433. The Connect() message means that a TCP/IP
socket was not created. From your office's server machine go to http://aboutmyip.com and see if port is open.
Fred Goldberg wrote:
> In the Office we have a Win2000 Server running MS SQL Server 2000. I know
> the servers external IP address (xxx.xxx.xxx.xxx) and we have a sub-domain
> set up (subname.mycompserver.com). I have a login and password into the
> server as well as the SQL login and password. The firewall is open on port
> 1433. From my office PC, I can access SQL, using ODBC, with Access or my
> Perl programs.
> At home, I'm running WinXP Pro. Although it shouldn't have been necessary,
> I installed MS SQL Server client. I connect to the Internet using a Comcast
> cable modem and do not have a static IP address. Whenever I try to set up
> ODBC to access my office's SQL server using ODBC Data Source Administrator
> / Add SQL Server, it fails with the following error message:
> Connection Failed
> SQL State: '01000'
> SQL Server Error: 10060
> [Microsoft][ODBC Server Driver][TCP/IP Sockets]Connection Open (Connect())
> Connection Failed:
> SQL State: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC Server Driver][TCP/IP Sockets]SQL Server does not exist or
> access denied.
> Is it possible to establish this ODBC connection into SQL and, if so, what
> am I doing wrong. Thanks.
> Fred
|||I truly appreciated your prompt reply to my question. Your answer
implies that this is doable.
I connected to our server using Remote Desktop, brought up IE and ran
http://aboutmyip.com. And, as you expected, Port 1433 is closed. My MIS
guys swore they opened it for me.
I'll have to get the port opened and try again. Thanks so much.
Fred
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
the servers external IP address (xxx.xxx.xxx.xxx) and we have a sub-domain
set up (subname.mycompserver.com). I have a login and password into the
server as well as the SQL login and password. The firewall is open on port
1433. From my office PC, I can access SQL, using ODBC, with Access or my
Perl programs.
At home, I'm running WinXP Pro. Although it shouldn't have been necessary,
I installed MS SQL Server client. I connect to the Internet using a Comcast
cable modem and do not have a static IP address. Whenever I try to set up
ODBC to access my office's SQL server using ODBC Data Source Administrator
/ Add SQL Server, it fails with the following error message:
Connection Failed
SQL State: '01000'
SQL Server Error: 10060
[Microsoft][ODBC Server Driver][TCP/IP Sockets]Connection Open (Connect())
Connection Failed:
SQL State: '08001'
SQL Server Error: 17
[Microsoft][ODBC Server Driver][TCP/IP Sockets]SQL Server does not exist or
access denied.
Is it possible to establish this ODBC connection into SQL and, if so, what
am I doing wrong. Thanks.
Fred
Hello Fred,
The only thing I can think is that firewall at your work is blocking 1433. The Connect() message means that a TCP/IP
socket was not created. From your office's server machine go to http://aboutmyip.com and see if port is open.
Fred Goldberg wrote:
> In the Office we have a Win2000 Server running MS SQL Server 2000. I know
> the servers external IP address (xxx.xxx.xxx.xxx) and we have a sub-domain
> set up (subname.mycompserver.com). I have a login and password into the
> server as well as the SQL login and password. The firewall is open on port
> 1433. From my office PC, I can access SQL, using ODBC, with Access or my
> Perl programs.
> At home, I'm running WinXP Pro. Although it shouldn't have been necessary,
> I installed MS SQL Server client. I connect to the Internet using a Comcast
> cable modem and do not have a static IP address. Whenever I try to set up
> ODBC to access my office's SQL server using ODBC Data Source Administrator
> / Add SQL Server, it fails with the following error message:
> Connection Failed
> SQL State: '01000'
> SQL Server Error: 10060
> [Microsoft][ODBC Server Driver][TCP/IP Sockets]Connection Open (Connect())
> Connection Failed:
> SQL State: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC Server Driver][TCP/IP Sockets]SQL Server does not exist or
> access denied.
> Is it possible to establish this ODBC connection into SQL and, if so, what
> am I doing wrong. Thanks.
> Fred
|||I truly appreciated your prompt reply to my question. Your answer
implies that this is doable.
I connected to our server using Remote Desktop, brought up IE and ran
http://aboutmyip.com. And, as you expected, Port 1433 is closed. My MIS
guys swore they opened it for me.
I'll have to get the port opened and try again. Thanks so much.
Fred
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Sunday, February 19, 2012
help me gauge the effort in my first db setup
Hello there... Happy New Year!
A client of mine, a group of 4 doctors, are interested in implementing a small office network in which they will switch to a digital filing system. I have recommended a Microsoft Server 2003 system, therefore the patient information will be stored in the SQL server.
I have never administered, administrated?? (see, I really need help here!) a database, but have built small databases from scratch in C and with Access, so I feel confident that I could set up a system for them. I need to have some kind of estimate, both a fee and implementation schedule. Can you help me get a handle on the scope of this?
Many thanks,
BrynYou Access experience will give you a leg up on the learning curve for developing a SQL Server database, but you will still have a lot to learn about administration. Security (which I think would be important for a doctors office) is much different, but is also much better and much simpler in SQL server than in Access. You will also need to write your SQL queries, so I hope that you are somewhat fluent in that and have occasionally looked at the SQL code that Access creates. Be aware that there are some subtle differences between SQL Server SQL and MS Access SQL.
Your best for a small application like this is to create it as an MS Access ADP project. This will allow you to use Access as an efficient interface to SQL Server. This is not the best solution for large applications, but for what you are describing it should be fine. If they want to scale it up in the future, they can drop the Access interface and still retain the SQL Server database with a new interface.
I can't, of course, give you an estimate on how long it will take you to complete it. Personally, since you are learning on the job, I think you should quote them based on how long it would take to develop the database in MS Access and consider any additional time as training and career development.
blindman|||You have many client tools in sql server that you need to research:
Enterprise Manager - This is a gui interface to manage your sql server instances.
Query Analyzer - Interface to run/test transact-sql statements.
BOL - Books Online - This is the online reference guide to sql server - You will use this frequently as you work with sql server. (Almost) Any question you have, go here first.
Profiler - captures events from sql server - allowing you to debug/analyze a problem/performance.
For books, look for books by Ken Henderson, Mark Spenik and Staneks pocket admin.
A client of mine, a group of 4 doctors, are interested in implementing a small office network in which they will switch to a digital filing system. I have recommended a Microsoft Server 2003 system, therefore the patient information will be stored in the SQL server.
I have never administered, administrated?? (see, I really need help here!) a database, but have built small databases from scratch in C and with Access, so I feel confident that I could set up a system for them. I need to have some kind of estimate, both a fee and implementation schedule. Can you help me get a handle on the scope of this?
Many thanks,
BrynYou Access experience will give you a leg up on the learning curve for developing a SQL Server database, but you will still have a lot to learn about administration. Security (which I think would be important for a doctors office) is much different, but is also much better and much simpler in SQL server than in Access. You will also need to write your SQL queries, so I hope that you are somewhat fluent in that and have occasionally looked at the SQL code that Access creates. Be aware that there are some subtle differences between SQL Server SQL and MS Access SQL.
Your best for a small application like this is to create it as an MS Access ADP project. This will allow you to use Access as an efficient interface to SQL Server. This is not the best solution for large applications, but for what you are describing it should be fine. If they want to scale it up in the future, they can drop the Access interface and still retain the SQL Server database with a new interface.
I can't, of course, give you an estimate on how long it will take you to complete it. Personally, since you are learning on the job, I think you should quote them based on how long it would take to develop the database in MS Access and consider any additional time as training and career development.
blindman|||You have many client tools in sql server that you need to research:
Enterprise Manager - This is a gui interface to manage your sql server instances.
Query Analyzer - Interface to run/test transact-sql statements.
BOL - Books Online - This is the online reference guide to sql server - You will use this frequently as you work with sql server. (Almost) Any question you have, go here first.
Profiler - captures events from sql server - allowing you to debug/analyze a problem/performance.
For books, look for books by Ken Henderson, Mark Spenik and Staneks pocket admin.
Subscribe to:
Posts (Atom)