i have two server connected to internet S1 and S2 (connection between both is only internet too).
I need write trigger on S1 which send update or another command to S2. Is it possible, and how (without using .NET methods only by using Transact SQL)?
- When I disable "allow remote connections to this server" from server properties>connection page, I can still remotely connect to the server from SSMS...so what is the impact of enable/disabling it?
- what is the impact of changing the remote query timeout (on the same page) from default value?
We have a database on a 2005 box, which we need to keep in sync with one on a 2014 box (until we can turn off the one on 2005). The 2005 database is still being updated with changes that must be applied to the 2014 database, given the nature of the data (medical documents) we need to ensure updates are applied to the 2014 database in very near real time (these changes are - for example - statuses, not the documents themselves).
Cunning plan #1, ulgy - not at all a fan of triggers - but use an after update trigger to run a sp on the remote box via a linked server in this format, with a SQL Server login for the linked server with permissions to EXEC the remote proc.
CREATE TRIGGER [dbo].[SourceUpdate] ON [dbo].[SourceTable] AFTER UPDATE AS SET XACT_ABORT ON; SET NOCOUNT ON; IF UPDATE(ColumnName)
[Code] ....
However, while the sp can be run against the linked server as a standalone query OK, when running it in a trigger it's throwing
OLE DB provider "SQLNCLI" for linked server "WIBBLE" returned message "The transaction manager has disabled its support for remote/network transactions.".
Msg 7391, Level 16, State 2, Procedure TheAfterUpdateTrigger, Line 19
The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "WIBBLE" was unable to begin a distributed transaction.
Whether it actually possible to call a proc on a remote box via a trigger and if so what additional hoops need to be jumped through (like I said, it'll run OK called via SSMS)?
I'm new to SQL. I have a scenario, Where customer want to move all the jobs from original SQL server to some remote SQL server and want to trigger jobs on remote server to do its work on original server.
Msg 7399, Level 16, State 1, Procedure tr_cpD, Line 14
The OLE DB provider "SQLNCLI" for linked server "S2" reported an error. The provider did not give any information about the error.
Msg 7312, Level 16, State 1, Procedure tr_cpD, Line 14
Invalid use of schema or catalog for OLE DB provider "SQLNCLI" for linked server "S2". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.
I have two different SQL 2008 servers, I don't have permission to create a linked server in any of them. i created a trigger on server1.table1 to insert the same record to the remote server server2.table1 using OPENROWSET
i created a stored procedure to insert this record, and i have no issue when i execute the stored procedure. it insert the recored into the remote server.
The problem is when i call the stored procedure from trigger, i get an error message.
Stored Procedure: USE [DB1] GO SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON
[Code] ....
When i try to insert a new description value in the table i got the following error message:
No row was updated the data in row 1 was not committed Error source .Net SqlClient Data provider. Error Message: the operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "The partner transaction manager has disabled its support for remote/network transaction.".
correct the errors entry or press ESC to cancel the change(s).
I'm using SQL Server to store session state. The Sql Server is on the local network but not on the web server. I use impersonation and use account credentials for the ASPNET worker process:
I've checked and given the user i'm impersonating the ability to do everything. I've granted access on all necessary files, added them to the DB and made the user a db_owner of the ASPState table. I can log in to a machine as the user, then access sql server using the windows authentication. I granted 'act as part of the operating system', 'access this computer from a network', 'log on as a service', 'log on as a batch job' on both the remote computer hosting sql server and the web server.
The strange thing is i installed the asp session state tables on my development machine, using the same configuration file to run everything, and was able to add an object to session state without any problem. But when i specify the remote server, i'm denied.
i use that to connect to the remote SQL server, which has status of port 1433 at "Stealth"... do i need to open the port complete, if yes how i do that ?
I want to access the other server from my Enterprise Manager by using <server_name>.<db_name>.<tab_name>.<procedure>/table_name.
Pls. let me know the steps I have to take I have added two remote logins in both the server. I also gave trusted right by using sp_remoteoption procedure and still I get the message 'the object <server_name> not accessible>
Please reply at the earliest, as I am right noe accessing the other servers data by bcp-out and bcpin into this server.............
I am trying to access SQL server remotely (over the internet). I would like to use query analyser as my front end tool. Can anyone point out the procedure to do the same. I have the IP address and the host string.
My ISP provide MS SQL Server. I can create my database name, dbusername and dbpassword through control panel and then I can access the database in ASP using this connection string "Provider=SQLOLEDB;UID=dbusername; PWD=dbpasword".
Before, I could also use my enterprise manager to create a new sql server registration using my web url, dbusername and dbpassword. But now it seems that my ISP blocks the port or something and ask me do everything through the control panel.
Does anyone have some idea to connect to a remote server thorough enterprise manager based on the infromation I have?
Does anyone know of a good place to find instructions on how to set up remote access to my SQL Server. I have been unsuccessful finding anything on this topic.
I'm writing a piece of software that is designed to access data from SQL server. The office's server has SQL server version 7 installed. The software works perfectly when running on a computer on the network in the office. I however am trying to work out how to use use the software from my home computer and connect to the SQL server database remotely. I've never done this before and I'm finding it hard to find the right information.
Firstly, is it easy to do this? What do I need to do with the server in the office to allow this to work? Do I need any extra hardware/software? How will my software connect to SQL server? Is it as simple as changing the connection string to something like the server's ip address and sql server name?
I'm writing the software in Visual Studio 2005 professional and programming in VB.
I am trying to read the databases attached to the Sql Server 2005.... my code works fine for Sql Server 2000 but when i try it with Sql Server 2005 it gives me error that "Under Current Settings SQL Server 2005 does not allow remote connections".
Can anybody tell me where to change these settings... i tried my best to find it but :(....
If possible to connect our remote server from my end ?.what r the possiblities is there.tell me some ideas,i already tried it to register our remote server database thru ODBC but it not connected properly but i ve tried in our intranet/network it's working fine.
I was just trying out Microsoft SQL Server 2000. I created a sample application which reads in 2 values from a textbox and writes it into a databse. This application works fine on my computer and the values are written to the database (In the connection string, I give my IP address as the datasource so that anyone on the internet can hit this database). However, when I copy this application to another computer and try to run it, it gives me an error "SQL Server does not exist or access is denied." I know this is a minor problem with some setting, but I haven't been able to find the solution on the internet. Can someone whose worked with Microsoft SQL Server 2000 please help me out.
I have a website which runs off a Access database which I am currentlyconverting to sql server database. I would like to still use my accessfront end for reporting and queries..I created an odbc connection on my computer to the remote sql serverand created a link in access to my sql server tables. All my report andQueries run fine I just have one problem it keeps on prompting me forther password of the remote sqlserver database. I check the odbcconnection and I see the password is not saved in there even though Iput it in. Is there a way I can have the password saved. I do not wantkeep on having to enter the password.
i need to upload time tracker in a static ip which doesnt have sql server, after the installation there in static ip, i receive the following error while trying to access
Named Pipes Provider, error: 40 - Could not open a connection to SQL Remote Server 2005
if i can somehow load/copy a sql directory with mdf etc on pcs shipped to our customers with our app, but sql isnt installed/running on the shipped pc, can our customers' sql instances running on their existing machines "see/use" our shipped database, assuming the hard drive on the shipped pc can be made to look like a mapped/remote drive? We wonder about 2000 and 2005.
In order to fix a web application bug the developer told me to to edit a stored procedure on my hosted SQL 2005 server. The hosting company's support say I should be able to do this using SQL Server Management Studio Express. I installed SSMSE, but it seems to want to only want to connect to a local server. Can I use this utility for remote DB management, or is there something else I need instead?
Sorry if this has probably been answered before, but...
I have a sql server 2005 behind SonicWall (not familiar with this firewall). How do I access this server over the internet? how do I grant access to it? I have an available IP address, where should I put it?
What steps do I need to follow? I am new to all of this. I have set the server to allow remote connections I have selected TCP/IP as the preferred mode of connection.
I am currently using a Microsoft Access (MDB) for my application. But I am looking at allowing other users on the network access the same database -- I know a Microsoft Access database is not the best solutuon for this enviroment.
I'd like to use SQL Server 2005 Express in this case. I am very fimilular with SQL Server 2000 Std/Ent editions. My question is, can I use the free SQL Server 2005 Express edition and allow remote users to connect to that database? Or is it supposed to only be used as a local database accessed by only the machine it's installed on?
When i connect the SQL server Remote Connection Through LAN that time it working fine but i switch over to wifi connection that time it is not working, and also the system not find SQL server Instance Name..
I am a VB6 programmer and I'm really new to SQL Express, I have always used ACCESS because it was so easy to deploy. I've now written a VB6 program which uses SQL Express and I want to know how to deploy it. Basically my PC will host the SQL database as it has SQL Express loaded onto it. I now want to install my EXE onto other Client's PC and have them read/write to the database on my machine.
Besides the EXE program, what software do I need to load onto the Client's PC so they can access my SQLExpress database...? (eg: Net Framework, SQLExpress, etc).
Also, if my machine is called ABC123, in my connectionstring do I just put in
ABC123sqlexpress as the datasource..?. Will this be enough for the other PCs to connect to mine ?
I'm writing a C# application which connects to a local SQL database for data access. The application connects to SQL Server through windows authentication, but opens up the port and sqlbrowser to others on the network wanting to access the database through SQL Server authentication, and also allows remote users to connect to this server remotely if they have the login and password (and because the port is already open)
I understand this is not secure and open to attack, and am unsure of how to secure these processes without blocking these three types of access, from A.) the local user, B.) the network user and C.) the remote user across the net.
Have researched this a fair bit, but get somewhat lost amongst all the jargon.
I am making a WPF app, and I want to use SQL Server Compact 4.0 for database management, but it doesn't support Remote data access, on the other hand SQL Server Compact 3.5 does support it but I can't use it in WPF ( I've installed it but can't add it in my project, it's not there in the templates). So is there any alternatives, for a light DBMS, that are not installed separately?
I am using XP_CMDSHELL to run 2 Windows commands (from a SQL 2005 SP2 server) that access files on a remote server (called webserver). The two commands are:
1. cscript.exe \webserverwwwrootEur_SaveProductImages.vbs 2. dir \webserverwwwroot Up until very recently this worked fine. Now I am getting Access Is Denied errors:
For #1: Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. CScript Error: Loading script "\webserverwwwrootEur_SaveProductImages.vbs" failed (Access is denied. ).
For #2: Access is denied.
This happens if the above commands are run through a job, or directly with Query Analyzer as SA.
I understand that XP_CMDSHELL commands are run in the security context of the SQL Server startup account. The SQL Server startup account is called SQLServer and this account exists on both webserver and the database server. On both servers the username & password are identical and the user is in the local Administrators group. The two servers are in a workgroup.
Things I have tried (with no effect):
1. Restarted the servers 2. Deleted and recreated the SQLServer login on both servers 3. Changed the startup account for SQL Server through the SQL Server Configuration Manager to another account and back to SQLServer.
The most revealing tests are these:
1. If I log into the database server myself using the SQLServer account I can run the above commands in a Command Prompt with no problem
2. I installed SQL 2005 Express SP2 on webserver using the same startup account (SQLServer). If I run the same XP_CMDSHELL commands as above but accessing files on the database server, the commands work! So, an XP_CMDSHELL command run under SQL Express using the local SQLServer account to access a remote server works, but an XP_CMDSHELL command run under SQL Server using a local SQLServer account (that is supposedly identical to the same named account on the other server) does not work !!?!?!?
It is almost as if XP_CMDSHELL commands run under SQL Server are NOT using the SQLServer startup account, but using some other weaker account. How can I tell if this is true?
How can I get this back working (as it was a week ago). The only thing I can think that happened on the servers to cause this is the installation of Windows Updates.
I have two win2003 servers. One is IIS and the another is SQL server. Ican use MyConnection=newSqlConnection("server=SQLServerName;database=myDBName;UID=sa;PWD= mypwd")to access my data. But I can not use MyConnection=newSqlConnection("server=SQLServerName;database=myDBName;IntegratedSecurity=SSPI") to access it. If I put both IIS and SQL Server in onemachine, I can do anything. How can I do something to allow trustedauthority work ?Thanks