Data File in a Different machine on the network.

Hi All,

I have a requirement to create the database with data and log files in
a different machine on the network.

Googling, I got a link which said Mapped drives do not work but UNC paths
work. However in my case, both are failing.

Any advices or links on net will be highly useful.

Thanks and Regards,
Chandra MohanDon't do this. It's not supported by Microsoft, you will lose all the
benefits of a client-server database and you risk corrupting your data.

Read this article:

http://www.mssqlserver.com/faq/gene...tworkdrives.asp

--
David Portas
----
Please reply only to the newsgroup
--|||bschandramohan@.yahoo.com (Chandra Mohan) wrote in message news:<bb0ef6.0309282105.59f0d698@.posting.google.com>...
> Hi All,
> I have a requirement to create the database with data and log files in
> a different machine on the network.
> Googling, I got a link which said Mapped drives do not work but UNC paths
> work. However in my case, both are failing.
> Any advices or links on net will be highly useful.
> Thanks and Regards,
> Chandra Mohan

Check this KB article:

http://support.microsoft.com/defaul...1&Product=sql2k

You can put database files on network drives by setting trace flag
1807, but it is not supported unless the files are on a NAS which is
specifically certified for SQL Server. Often, the NAS will make the
network drive appear like a local one, so you won't need to set the
trace flag on anyway.

Putting a database on a normal UNC share is a very bad idea - you
won't be able to guarantee data integrity and performance will suffer.

Simon|||David Portas (REMOVE_BEFORE_REPLYING_dportas@.acm.org) writes:
> Don't do this. It's not supported by Microsoft, you will lose all the
> benefits of a client-server database and you risk corrupting your data.

I agree that putting a database on a network drive is an extremely bad
idea, but I don't see where the client-server issue comes in. You can
still connect a lots of clients to that database, as if the database
had been a drive local to the database server. (Well, lots and lots.
If there are lots, corruption might appear within the hour.)

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||What I had in mind was that you lose the performance advantage (compared to
a desktop database running on a network) of server-based processing. And you
sacrifice much of the resilience of transaction management and logging.

--
David Portas
----
Please reply only to the newsgroup
--

"Erland Sommarskog" <sommar@.algonet.se> wrote in message
news:Xns9405EBB63563DYazorman@.127.0.0.1...
> David Portas (REMOVE_BEFORE_REPLYING_dportas@.acm.org) writes:
> > Don't do this. It's not supported by Microsoft, you will lose all the
> > benefits of a client-server database and you risk corrupting your data.
> I agree that putting a database on a network drive is an extremely bad
> idea, but I don't see where the client-server issue comes in. You can
> still connect a lots of clients to that database, as if the database
> had been a drive local to the database server. (Well, lots and lots.
> If there are lots, corruption might appear within the hour.)
>
> --
> Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||David Portas (REMOVE_BEFORE_REPLYING_dportas@.acm.org) writes:
> What I had in mind was that you lose the performance advantage (compared
> to a desktop database running on a network) of server-based processing.
> And you sacrifice much of the resilience of transaction management and
> logging.

You mean that rather running client on machine A and server on machine B,
we're running both server and client on A, and only have the database files
on B.

Yes, this is killing the client-server concept. (Ever heard of Visual
SourceSafe? That's an example of this architecture.)

I don't know why people want to put databases on network devices, but
my assumption is that the most common reason is simply space constraint
on the server, so they try to rent space somewhere else in the network.
In this case, I guess clients still connect from somewhere else.

But rather than renting the space, it's better to rent the entire disk
and move into cabinet. Or see your local hardware dealer...

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Data Directory In Network location?

Is it possible to set DATADIR=\\<company_network_somedirectory>\? When I
try it, set-up seems to fail.
Also, if I were to create a new database on a default instance of MSDE, I am
not able to pick mapped network directories.
Appreciate any insight.
Thanks,
Sha.
hi Sha,
"Sha S." <shajihans@.ttnus.com> ha scritto nel messaggio
news:OajGz8D7EHA.3836@.tk2msftngp13.phx.gbl
> Is it possible to set DATADIR=\\<company_network_somedirectory>\?
> When I try it, set-up seems to fail.
>
it is possible, using a trace flag, but strongly not suggested... SQL Server
requires a strong, reliant and trusted, verified path (and enough permission
must be granted to the Windows account running it's services) in order
perform (possibly as fast as possible) disk IO operations...
as Network share usually are not that secure and robust, nor fast, it is
strongly advised only to use "local" storag subsystem and not remote...
as regard the setup.exe parameter, I actually do not know if it's possible
to specify remote paths...
please keep you data on your local disk(s) :D

> Also, if I were to create a new database on a default instance of
> MSDE, I am not able to pick mapped network directories.
>
again, enough permission(s) [on the network shares] must be granted to the
Windows account running MSDE SQL Server and SQL Server Agent services..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you, Andrea, for your reply. I shall follow it.
Andrea Montanari wrote:
> hi Sha,
> "Sha S." <shajihans@.ttnus.com> ha scritto nel messaggio
> news:OajGz8D7EHA.3836@.tk2msftngp13.phx.gbl
>
> it is possible, using a trace flag, but strongly not suggested... SQL Server
> requires a strong, reliant and trusted, verified path (and enough permission
> must be granted to the Windows account running it's services) in order
> perform (possibly as fast as possible) disk IO operations...
> as Network share usually are not that secure and robust, nor fast, it is
> strongly advised only to use "local" storag subsystem and not remote...
> as regard the setup.exe parameter, I actually do not know if it's possible
> to specify remote paths...
> please keep you data on your local disk(s) :D
>
>
> again, enough permission(s) [on the network shares] must be granted to the
> Windows account running MSDE SQL Server and SQL Server Agent services..
>
|||hi Sha,
"Sha S." <pilgrim216@.gmail.com> ha scritto nel messaggio
news:e8MrtIP7EHA.3616@.TK2MSFTNGP11.phx.gbl
> Thank you, Andrea, for your reply. I shall follow it.
>
:D
just a consideratio I had after posting... for sure it's not possible to
specify remote folders for <DATA_DIR> parameter as you can not install MSDE
specifying the trace flag required for that kind of feature
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Data diiferentator tools

Hi All,
We have a kiosk application which will be distributed across the states
and connected to network on a cellular broadband connection. Kiosks
transmit records to our central server on a periodic basis.
We use a 3rd party vendor database in kiosks which needs to be updated
once a month. Vendor is not ready to give us a differential database so
we have to write our own utility to do this.
Are there any 3rd party tools available to this or any other
suggestions will be greatly appreciated.
Regards,
SobhanRed-Gate SQL Data Compare (www.red-gate.com)
Amos.
<Sobhan.Vezzu@.gmail.com> wrote in message
news:1150928122.648282.308070@.p79g2000cwp.googlegroups.com...
> Hi All,
> We have a kiosk application which will be distributed across the states
> and connected to network on a cellular broadband connection. Kiosks
> transmit records to our central server on a periodic basis.
> We use a 3rd party vendor database in kiosks which needs to be updated
> once a month. Vendor is not ready to give us a differential database so
> we have to write our own utility to do this.
> Are there any 3rd party tools available to this or any other
> suggestions will be greatly appreciated.
> Regards,
> Sobhan
>|||Red-Gate SQL Data Compare (www.red-gate.com)
Amos.
<Sobhan.Vezzu@.gmail.com> wrote in message
news:1150928122.648282.308070@.p79g2000cwp.googlegroups.com...
> Hi All,
> We have a kiosk application which will be distributed across the states
> and connected to network on a cellular broadband connection. Kiosks
> transmit records to our central server on a periodic basis.
> We use a 3rd party vendor database in kiosks which needs to be updated
> once a month. Vendor is not ready to give us a differential database so
> we have to write our own utility to do this.
> Are there any 3rd party tools available to this or any other
> suggestions will be greatly appreciated.
> Regards,
> Sobhan
>

Data diiferentator tools

Hi All,
We have a kiosk application which will be distributed across the states
and connected to network on a cellular broadband connection. Kiosks
transmit records to our central server on a periodic basis.
We use a 3rd party vendor database in kiosks which needs to be updated
once a month. Vendor is not ready to give us a differential database so
we have to write our own utility to do this.
Are there any 3rd party tools available to this or any other
suggestions will be greatly appreciated.
Regards,
SobhanRed-Gate SQL Data Compare (www.red-gate.com)
Amos.
<Sobhan.Vezzu@.gmail.com> wrote in message
news:1150928122.648282.308070@.p79g2000cwp.googlegroups.com...
> Hi All,
> We have a kiosk application which will be distributed across the states
> and connected to network on a cellular broadband connection. Kiosks
> transmit records to our central server on a periodic basis.
> We use a 3rd party vendor database in kiosks which needs to be updated
> once a month. Vendor is not ready to give us a differential database so
> we have to write our own utility to do this.
> Are there any 3rd party tools available to this or any other
> suggestions will be greatly appreciated.
> Regards,
> Sobhan
>

DATA ACCESS

The network admins did some OS security patches (and who
knows what else) and today we're getting the following
error on a few established processes:
Microsoft OLE DB Provider for SQL Server -2147217900
Server 'SERVER123' is not configured for DATA ACCESS.
We believe this is a cross server issue. Anyway, this
error msg looks familiar, but I can't quite place it.
Any help would be much appreciated.
Joe,
Try..
exec sp_serveroption SERVER123, 'data access', 'true'
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>
|||Hi,
Execute the below procedure with correct linked server name.
sp_serveroption 'Linked_server_name','data access',true
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>
|||Before I run this, I've got a question:
1. I've already got a link server set up. Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?

>--Original Message--
>Joe,
>Try..
>exec sp_serveroption SERVER123, 'data access', 'true'
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
>
>.
>
|||Before I run this, I've got a few questions:
1. I've already got a linked server set up and it seems
to be working for reads at least (but the developers are
claiming it's not working for updates). Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?

>--Original Message--
>Hi,
>Execute the below procedure with correct linked server
name.
>sp_serveroption 'Linked_server_name','data access',true
>
>Thanks
>Hari
>MCDBA
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
>
>.
>
|||Hi,
1. I've already got a link server set up. Does this just "enable" that
linked server?
Enables and disables a linked server for distributed query access.
2. If I am running this on serverA, do I put in 'serverB' for the first
argument, i.e. the linked server that I am trying to connect to?
You have to put SERVERB (Which is the remote server)
3. How could this get set to false? I certainly didn't do it! Have you
ever seen MS installs hose this up?
No Idea
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx.gbl...[vbcol=seagreen]
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
> message
|||Joe,
#1.Correct. 'True' enables the linked server for data access.
#2.Yes.
#3.How it was set to false, I dont know.May be, one of those patches did
that.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx.gbl...[vbcol=seagreen]
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
> message

DATA ACCESS

The network admins did some OS security patches (and who
knows what else) and today we're getting the following
error on a few established processes:
Microsoft OLE DB Provider for SQL Server -2147217900
Server 'SERVER123' is not configured for DATA ACCESS.
We believe this is a cross server issue. Anyway, this
error msg looks familiar, but I can't quite place it.
Any help would be much appreciated.Joe,
Try..
exec sp_serveroption SERVER123, 'data access', 'true'
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>|||Hi,
Execute the below procedure with correct linked server name.
sp_serveroption 'Linked_server_name','data access',true
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>|||Before I run this, I've got a question:
1. I've already got a link server set up. Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?
>--Original Message--
>Joe,
>Try..
>exec sp_serveroption SERVER123, 'data access', 'true'
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
>> The network admins did some OS security patches (and who
>> knows what else) and today we're getting the following
>> error on a few established processes:
>> Microsoft OLE DB Provider for SQL Server -2147217900
>> Server 'SERVER123' is not configured for DATA ACCESS.
>> We believe this is a cross server issue. Anyway, this
>> error msg looks familiar, but I can't quite place it.
>> Any help would be much appreciated.
>
>.
>|||Before I run this, I've got a few questions:
1. I've already got a linked server set up and it seems
to be working for reads at least (but the developers are
claiming it's not working for updates). Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?
>--Original Message--
>Hi,
>Execute the below procedure with correct linked server
name.
>sp_serveroption 'Linked_server_name','data access',true
>
>Thanks
>Hari
>MCDBA
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
>> The network admins did some OS security patches (and who
>> knows what else) and today we're getting the following
>> error on a few established processes:
>> Microsoft OLE DB Provider for SQL Server -2147217900
>> Server 'SERVER123' is not configured for DATA ACCESS.
>> We believe this is a cross server issue. Anyway, this
>> error msg looks familiar, but I can't quite place it.
>> Any help would be much appreciated.
>
>.
>|||Hi,
1. I've already got a link server set up. Does this just "enable" that
linked server?
Enables and disables a linked server for distributed query access.
2. If I am running this on serverA, do I put in 'serverB' for the first
argument, i.e. the linked server that I am trying to connect to?
You have to put SERVERB (Which is the remote server)
3. How could this get set to false? I certainly didn't do it! Have you
ever seen MS installs hose this up?
No Idea
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx.gbl...
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
> >--Original Message--
> >Joe,
> >
> >Try..
> >
> >exec sp_serveroption SERVER123, 'data access', 'true'
> >
> >--
> >Dinesh
> >SQL Server MVP
> >--
> >--
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> >> The network admins did some OS security patches (and who
> >> knows what else) and today we're getting the following
> >> error on a few established processes:
> >>
> >> Microsoft OLE DB Provider for SQL Server -2147217900
> >> Server 'SERVER123' is not configured for DATA ACCESS.
> >>
> >> We believe this is a cross server issue. Anyway, this
> >> error msg looks familiar, but I can't quite place it.
> >>
> >> Any help would be much appreciated.
> >>
> >
> >
> >.
> >|||Joe,
#1.Correct. 'True' enables the linked server for data access.
#2.Yes.
#3.How it was set to false, I dont know.May be, one of those patches did
that.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx.gbl...
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
> >--Original Message--
> >Joe,
> >
> >Try..
> >
> >exec sp_serveroption SERVER123, 'data access', 'true'
> >
> >--
> >Dinesh
> >SQL Server MVP
> >--
> >--
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> >> The network admins did some OS security patches (and who
> >> knows what else) and today we're getting the following
> >> error on a few established processes:
> >>
> >> Microsoft OLE DB Provider for SQL Server -2147217900
> >> Server 'SERVER123' is not configured for DATA ACCESS.
> >>
> >> We believe this is a cross server issue. Anyway, this
> >> error msg looks familiar, but I can't quite place it.
> >>
> >> Any help would be much appreciated.
> >>
> >
> >
> >.
> >

DATA ACCESS

The network admins did some OS security patches (and who
knows what else) and today we're getting the following
error on a few established processes:
Microsoft OLE DB Provider for SQL Server -2147217900
Server 'SERVER123' is not configured for DATA ACCESS.
We believe this is a cross server issue. Anyway, this
error msg looks familiar, but I can't quite place it.
Any help would be much appreciated.Joe,
Try..
exec sp_serveroption SERVER123, 'data access', 'true'
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx
.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>|||Hi,
Execute the below procedure with correct linked server name.
sp_serveroption 'Linked_server_name','data access',true
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx
.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>|||Before I run this, I've got a question:
1. I've already got a link server set up. Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?

>--Original Message--
>Joe,
>Try..
>exec sp_serveroption SERVER123, 'data access', 'true'
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
> news:1d0e801c42308$ddd0b690$a401280a@.phx
.gbl...
>
>.
>|||Before I run this, I've got a few questions:
1. I've already got a linked server set up and it seems
to be working for reads at least (but the developers are
claiming it's not working for updates). Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?

>--Original Message--
>Hi,
>Execute the below procedure with correct linked server
name.
>sp_serveroption 'Linked_server_name','data access',true
>
>Thanks
>Hari
>MCDBA
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
> news:1d0e801c42308$ddd0b690$a401280a@.phx
.gbl...
>
>.
>|||Hi,
1. I've already got a link server set up. Does this just "enable" that
linked server?
Enables and disables a linked server for distributed query access.
2. If I am running this on serverA, do I put in 'serverB' for the first
argument, i.e. the linked server that I am trying to connect to?
You have to put SERVERB (Which is the remote server)
3. How could this get set to false? I certainly didn't do it! Have you
ever seen MS installs hose this up?
No Idea
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx
.gbl...[vbcol=seagreen]
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
>
> message|||Joe,
#1.Correct. 'True' enables the linked server for data access.
#2.Yes.
#3.How it was set to false, I dont know.May be, one of those patches did
that.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx
.gbl...[vbcol=seagreen]
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
>
> message

Daily Check List

I need to create daily check list for SQL 2000. Here is what I have done:

1. Check the connectivity of each server over the network. (Ping/open Enterprise Manager and proof connection)
2. Check whether the services are running for each server. (Green light)
3. Check the scheduled tasks on the production servers are running normally. Enterprise Manager of each server or your email (Set up SQL Mail to notify you).
4. Check the hard disk space available on the SQL Servers.
5. Check all the database and transaction log space on each server. If the database or transaction log space runs out, the transactions will fail.
6. Check NT event Logs for any error messages.
7. Check SQL Error Logs for any errors occurring within SQL Server.

My question is: any other tips & ideas for every day routine?

Thank in advanced!

You've got a great start here. The log checks are an important step that many shops miss. On a daily basis, you also want to check your backups, and the status of replication and clustering if you have that installed as well. You'll pick some of that up in the logs, but you may want to check them independently as well. At my shop we also include a check on the running processes to make sure we don't have any run away queries, but that all depends on the size of your shop and the number of applications you have running.

You may want to incorporate all of these checks into a single place. The two processes I've seen are to write a set of scripts to gather all the information into a monitoring database, or to purchase a software package that will do the same thing for you.

Buck