SQL Server not configured for data access

Question

I'm running a SQL Server 2005 database from a VB 6 Application. I connect to the database through an ODBC DSN.

I renamed the computer on which I'm running the default instance of SQL server from 'Software' to 'IT'. I then ran the sp_dropserver and sp_addserver stored procedures to rename the instance.

On restarting the SQL Server service, the server was able to pick up on the new SQL Server name.

After configuring the ODBC data source name to the new name, the connection was Ok. I'm able to run my application and read records through ADO record sets. However I'm unable to update any recordset using the .Update method. I get the following error instead ... SQL Server not configured for data access

How can I enable data access on the renamed server instance?

score 51 · Answer 1 · answered Mar 11 '09 at 15:30

51

How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server 2005

You should be able to run this but not against any linked server. It's not a linked server. It's local.

EXEC sp_serveroption 'YourServer', 'DATA ACCESS', TRUE

answered Mar 11 '09 at 15:30

gbn

422,506
82
585
676

1

Does doing this expose the server to SQL injection or other security issues? – Fandango68 Oct 04 '16 at 03:35
1

does not work if your stored procedure uses dynamic sql – Tone Škoda Feb 16 '17 at 09:23

score 5 · Answer 2 · edited Sep 22 '17 at 00:11

5

Just go to the linked server properties > Server options > Data access --> true

Works on SQL Server 2014.

Regards

edited Sep 22 '17 at 00:11

Redit0

370
1
14

answered Apr 15 '17 at 11:30

Ljuba Buinjac

61
1
4

Is "thrue" supposed to be "true" ? Perhaps edit the answer someone? – qxotk May 26 '17 at 13:48

score 3 · Answer 3 · edited Aug 22 '21 at 10:16

3

with this

use master
go

exec sp_serveroption 'server name', 'data access', 'true'
go

linked servers generated for replication still showing same error

edited Aug 22 '21 at 10:16

LowlyDBA - John M

191
7
15

answered Nov 15 '13 at 10:56

user2991005

33
3

score 3 · Answer 4 · answered Jun 04 '15 at 14:02

I just would like to add to the previous answers that, at least in my case here, I needed to enable data access in both places.

for instance:

there is server A and server B

On server A I have a linked server LB that links me from server A to server B

I need to execute the following:

-- on server A

exec sp_serveroption 'LB', 'data access', 'true'

-- on server B

exec sp_serveroption 'B', 'data access', 'true'

score 2 · Answer 5 · answered Oct 13 '15 at 11:54

2

I've just come across this error and found that it was caused by me trying to run OpenQuery against the local server (doh!). Changing the server name to that of an actual linked server resolved my issue.

answered Oct 13 '15 at 11:54

Neil P

2,920
5
33
64

A better fix would be not to use OpenQuery when you don't need to. – mrdenny Oct 29 '18 at 18:06

SQL Server not configured for data access

5 Answers5

Linked