[dba-SQLServer] [AccessD]TransferringadatabasetoanotherSQLServer

Jim Lawrence accessd at shaw.ca
Mon Aug 28 19:23:19 CDT 2006


To whom it may concern:

This is a public forum. I could not just stand by while you dress-down a
fellow member, regardless the errors of their ways, at such length, so
stridently, on such a personal level and public manner. If you wished to so
educate someone please do it off-line.

Jim  

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett,
Andrew
Sent: Monday, August 28, 2006 4:16 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer]
[AccessD]TransferringadatabasetoanotherSQLServer

The ability to research, commit to, and undertake a reasonable level of
research yourself is a valuable skill in itself. Despite your belief that
you continually RTFM, a large majority of answers provided here contain a
link or reference to Books On Line or other easily accessible material
online.. Why is this do you think???

I vary rarely give 'step by step / line by line' response that you seem to
demand, in any of the forums I am a member of. > I'm more than willing to
point users in the right direction, provide reasoning & my experiences,
hoping that they will learn to help themselves (fishing rod?), thereby
developing the abilities to perhaps solve the problem for themselves (and
perhaps others) in the future.  

You've proved my point perfectly..  You asked the exact same question in the
past, didn't learn from it, and are now facing the consequences. 

If someone else wants to provide that level of help to you, then by all
means go ahead, but if you want a "DETAILED INSTRUCTIONS on how to
COMPLETELY implement something" then pick up a phone, dial a consultant and
pay them for it-> someone who will be able to commit the time required to
analyse / design / implement and troubleshoot if required.  As much as you'd
like to think you can get by with support of a community such as this, when
you're talking about Network config / RDBMS infrastructure / Security etc,
it is simply naïve to think that you will not encounter problems..  

I would assume anyone with the aforementioned research skills, after reading
my suggestion to turn off simple file sharing, would at least spend 5
minutes on google finding out how to do it and hopefully picking up a bit of
info on what it entails & impacts upon. Similarly, try searching google for
"SQL Server Login Failed Simple File Sharing" and I'm sure you'll get a
number of results -> not difficult or time consuming IMO..

If this simple change has stuffed up your network, then you must have other
issues or (again) not understand what you have configured in your network to
start with. (Could also be that your trying to run 'server-recommended'
software and systems on a home based operating system...Again not
recommended, and again I believed suggested in these forums in the past..)

If you're unwilling to commit time into understanding this then fine, pay
someone to do it for you.  If you are offended with this suggestion or not
willing or able to spend the money, then I'm sorry, but you've taken on the
wrong projects, which, if memory serves, was raised as a possibility in this
forum when you first indicated taking on this line of work.

Bit ironic to ignore that advice but then rely on the same source as a
primary means to support your business.. 



-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Tuesday, 29 August 2006 12:33 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer]
[AccessD]TransferringadatabasetoanotherSQLServer

Haslett, this is an ACCESS group / SQL Server group, Not a Network Admin
group. 

>Sorry if this sounds harsh but there are reasons that this stuff is 
>taught
in detailed courses -> it's just not something you can pick up and try to do
off the cuff without some experience or at least willingness to investigate
the documentation provided.

If that is the case, then throwing out advice like "turn off simple file
sharing" is inappropriate advice, at least without a "this will royally
screw up your private workgroup file sharing (and not even get you what you
are after)" warning.  Sorry if THAT sounds harsh, but I am NOT a Notwork
Admin (nor are many others on this list), and apparently my workgroup file
sharing IS SCREWED UP because I blithely followed "correct" advice.

Not only did it screw up my file sharing (which BTW is still not working)
but it did NOT provide sufficient assistance to get my the SQL Server
registration working.  

Is this mail list not supposed to be about coming here to ask advice from
people more experienced than myself?  Is the result of listening to such
advice SUPPOSED to be screwing up my workgroup / file sharing and NOT EVEN
GETTING what I was asking about answered?  

If that is the case I suppose I have very little use for this group!

And OBTW, I am willing to RTFM.  I have been reading the manual all of my
adult life!  SQL Server is not my strong suite to say the least, and
(apparently) security and SQL Server is not a trivial subject.  And having
RTFM, I am still without my file sharing.

But I do appreciate your understanding.  I would even bow in your general
direction but I don't know where you are.

Thanks very much for your (correct) advice, I can't begin to tell you how
much help it was.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett,
Andrew
Sent: Monday, August 28, 2006 10:24 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer]
[AccessD]TransferringadatabasetoanotherSQLServer

Perhaps the advice provided months (a year?) ago when I recall this same (or
similar) problem arose, recommending that this type of thing should not be
attempted without sufficient training / experience / professional
assistance, was good advice?

Simple file sharing is the reason you could not connect. Steps to disable it
were posted in a previous post.  Enabling it is as simple as checking the
box instead of unchecking it.. A 1 minute search on google will further
provide these details.

Furthermore, the documentation for SQL Server - Books On Line, by far the
best product documentation that MS has provided, will provide you with
plenty of easy to find material on configuring security in SQL Server, which
will detail the issues you are requesting on SQL / Windows Authentication. 

Sorry if this sounds harsh but there are reasons that this stuff is taught
in detailed courses -> it's just not something you can pick up and try to do
off the cuff without some experience or at least
willingness to investigate the documentation provided.   And when the
(correct) help we provide is thrown back at us with "you screwed my network"
then, with all respect -> good luck with it yourself..

 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Monday, 28 August 2006 10:30 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] [AccessD]
TransferringadatabasetoanotherSQLServer

>In yet another attempt to cater to the masses...

I AM the masses.

>You need to turn "Simple File Sharing" off, not turn "File Sharing"
off.

I have no idea how to turn "file sharing" on / off.  I have turned "simple
file sharing" off with the result that the poor huddled masses can no longer
see the files on the poor huddled masses other machines, which makes the
poor huddled masses most unhappy.  Furthermore,  in SQL Server EM with SFS
turned off, the other machines no longer even show up as available to
register a server on, which also makes the poor huddled masses most unhappy.

It seems that by following the simple edict "turn off SFS" the poor huddled
masses have royally screwed up the private little workgroup in the home
office, and can not seem to get it back.

Sigh.

DETAILED INSTRUCTIONS on how to COMPLETELY implement something are so much
appreciated.  The poor huddled masses are called the poor huddled masses
precisely because they have not spent the hundreds of hours required to
become OS administrators.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart
McLachlan
Sent: Monday, August 28, 2006 8:34 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] [AccessD] Transferring
adatabasetoanotherSQLServer

On 28 Aug 2006 at 8:16, JWColby wrote:

> This is a network in my home office.  Why do I need to turn Simple 
> File Sharing off, and if I need to do that, how do I replace it's
functionality?
> 
> With Simple File Sharing OFF my workstations can no longer see each 
> other and I get "no permission to use" error messages when trying to 
> browse for shares in Explorer.
> 
> Furthermore, with SFS off, the other machines do not show up when 
> browsing in EM for other servers.
> 

You need to turn "Simple File Sharing" off, not turn "File Sharing" off.

In yet another attempt to cater to the masses, MS introduced a new
simplified type of file sharing in XP as an alternative to the standard file
sharing that we have always used. They call this new system "Simple

File Sharing".    XP Home always uses Simple File Sharing.  XP Pro
defaults
to Simple File Sharing if you are using a peer to peer network (no domain
controller).

If you are configured to use Simple File Sharing, remote users always
authenticate using the Guest account and you run into the sort or problem
you are facing.

To switch to classic file sharing, 

1.	Double-click My Computer on the desktop.
2.	On the Tools menu, click Folder Options.
3.	Click the View tab, and then de-select "Use Simple File Sharing"


Now you can set proper permissions on your resources and authenticate using
accounts with appropriate permissions.

See http://support.microsoft.com/kb/304040/ for all the gory details

--
Stuart


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



IMPORTANT - PLEASE READ *** This email and any files transmitted with it are
confidential and may contain information protected by law from disclosure.
If you have received this message in error, please notify the sender
immediately and delete this email from your system. No warranty is given
that this email or files, if attached to this email, are free from computer
viruses or other defects. They are provided on the basis the user assumes
all responsibility for loss, damage or consequence resulting directly or
indirectly from their use, whether caused by the negligence of the sender or
not.
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



IMPORTANT - PLEASE READ *** This email and any files transmitted with it are
confidential and may contain information protected by law from disclosure.
If you have received this message in error, please notify the sender
immediately and delete this email from your system. No warranty is given
that this email or files, if attached to this email, are free from computer
viruses or other defects. They are provided on the basis the user assumes
all responsibility for loss, damage or consequence resulting directly or
indirectly from their use, whether caused by the negligence of the sender or
not.
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com





More information about the dba-SQLServer mailing list