Newbie Question - Service Manager / Win 2003

Hi,

I'm running a Microsoft Windows 2003 Server computer, which is using a MS SQL server to feed our office application, OfficeTalk.

Due to the extreme size of the database, we have decided to install an external 1TB drive, and move the database to it.

The difficult bit we're finding is how to make it so that the service loads the new data source.

In other words, how do you use Service Manager to parse an argument to dbsvr.exe in order to change the database location?

Regards,
Matthew.Hi Mathew and welcome to TSDN MSSQL forum,

If you have an agreed maintenance slot where you can take the MSSQL server down, I would suggest do the following:

Back everything up
using enterprise manager detach on the database you want to move
copy the database to the new location
using enterprise manager attach the database by browsing to the new location.

If you get problems, backout by detaching the database in the new location and attach the old one.

Suggest you also try it out on a test DB, northwinds etc before you go for it for real..

Regards Purple

Newbie Question

Hello,
A very simple question:
What happens when two people work at the same time in the same record?
The Last win or the first?It depends on the configuration of your database, what your
application/component is doing in background, what you have
done before starting with the update ...
Normaly you use "optimistic locking", which means you do not
lock the record when you read it or when you start to change it.
The record will only be locked for the short time of writing the
new data in the database.
Now when somebody has changed the same record there could
be two options:
a) your database/component checks that the record was changed
in the meantime and gives an error
b) your database/component only checks if one of the fields you
have changed where changed by another user.
For example: your record holds person number and name
you read the record and change the number, in the meantime
somebody has changed the name. When you write your change
into the database so it only checks if number is like before. This is
because the other user only changed the name. Your update now
only changes the number and when you read the record again you
will see your new number and the new name.
But there are a lot more possibilities, you should read a good book
about transactions and locking mechanism and do tests, test, tests, ...
Another way would be "pessimistic locking" where you read a record
again with locking if the state goes to editing or to lock when you are
reading the record and if locking is okay you can be sure that your
changes can be written and nobody else can change something in the
meantime. But the bad thing is that the record stays still locked if
somebody started editing and then goes to luch before saving the
changes.

bye,
Helmut|||Thanks Helmut
for this full Description.
I will test some scenarios and think I take the last option with the locked records.
Bye Martin

newbie IIS & MS SQL connection problem ;-(

Have successfully installed MS SQL on my Win XP Pro machine, created tables,
and a dsn, which is working fine in Dreamweaver. So far so good.

When I run the page on IIS I get the following:-

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database
requested in login 'MenuPlanner'. Login fails.

I think it's permissions - anyone got any clues as to where to look?

TIA

GrantBuzby wrote:
> Have successfully installed MS SQL on my Win XP Pro machine, created
tables,
> and a dsn, which is working fine in Dreamweaver. So far so good.
> When I run the page on IIS I get the following:-
> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database
> requested in login 'MenuPlanner'. Login fails.
> I think it's permissions - anyone got any clues as to where to look?

You could see if the login MenuPlanner has got permissions to the
database you are logging in to. That would be a start.

--
David Rowland
For a good user and performance monitor, check DBMonitor
http://dbmonitor.tripod.com

> TIA
> Grant|||"dbmonitor" <dbmonitor_support@.hotmail.com> wrote in message
news:1107519068.678569.226760@.o13g2000cwo.googlegr oups.com...
> Buzby wrote:
>> Have successfully installed MS SQL on my Win XP Pro machine, created
> tables,
>> and a dsn, which is working fine in Dreamweaver. So far so good.
>>
>> When I run the page on IIS I get the following:-
>>
>> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
>> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database
>> requested in login 'MenuPlanner'. Login fails.
>>
>> I think it's permissions - anyone got any clues as to where to look?
> You could see if the login MenuPlanner has got permissions to the
> database you are logging in to. That would be a start.

This is what has got me - permissions are set up. I've created a dsn, which
I can run queries in Dreamweaver and filter results just fine. I'm having
trouble when running the page on my webserver (IIS which is working fine)

Stumped ;-(|||Buzby wrote:
> "dbmonitor" <dbmonitor_support@.hotmail.com> wrote in message
> news:1107519068.678569.226760@.o13g2000cwo.googlegr oups.com...
> > Buzby wrote:
> >> Have successfully installed MS SQL on my Win XP Pro machine,
created
> > tables,
> >> and a dsn, which is working fine in Dreamweaver. So far so good.
> >>
> >> When I run the page on IIS I get the following:-
> >>
> >> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> >> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
database
> >> requested in login 'MenuPlanner'. Login fails.
> >>
> >> I think it's permissions - anyone got any clues as to where to
look?
> > You could see if the login MenuPlanner has got permissions to the
> > database you are logging in to. That would be a start.
> This is what has got me - permissions are set up. I've created a dsn,
which
> I can run queries in Dreamweaver and filter results just fine. I'm
having
> trouble when running the page on my webserver (IIS which is working
fine)
> Stumped ;-(

Is MenuPlanner the database name or the login name?

If it is the database name, are you connecting to the database via a
userid/password or are you connecting with Windows interactive UserID?
--
David Rowland
For a good user and performance monitor, check DBMonitor
http://dbmonitor.tripod.com|||Buzby (gb@.pumpupthe.net) writes:
> Have successfully installed MS SQL on my Win XP Pro machine, created
> tables, and a dsn, which is working fine in Dreamweaver. So far so
> good.
> When I run the page on IIS I get the following:-
> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database
> requested in login 'MenuPlanner'. Login fails.
> I think it's permissions - anyone got any clues as to where to look?

Sounds like the login has a default db which does not exist, or the login
does have access to. Use sp_helplogins to check, use sp_defaultdb to change.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||On 2/4/05 5:37 PM, in article Xns95F3F003A2514Yazorman@.127.0.0.1, "Erland
Sommarskog" <esquel@.sommarskog.se> wrote:

> Buzby (gb@.pumpupthe.net) writes:
>> Have successfully installed MS SQL on my Win XP Pro machine, created
>> tables, and a dsn, which is working fine in Dreamweaver. So far so
>> good.
>>
>> When I run the page on IIS I get the following:-
>>
>> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
>> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database
>> requested in login 'MenuPlanner'. Login fails.
>>
>> I think it's permissions - anyone got any clues as to where to look?
> Sounds like the login has a default db which does not exist, or the login
> does have access to. Use sp_helplogins to check, use sp_defaultdb to change.

Yea, but a DSN is being used so we have to believe that MenuPlanner is the
name of the DSN Connection. I am assuming that the DSN was created on the
IIS server and connects successfully when you "test connection" in the ODBC
dialog.

I highly recommend using a DSN-less connection in your ASP pages. There is
lots of documentation on ADODB.

If you need some sample connection strings let me know.|||Gregory Dean (gdean@.datapex.com) writes:
> On 2/4/05 5:37 PM, in article Xns95F3F003A2514Yazorman@.127.0.0.1, "Erland
> Sommarskog" <esquel@.sommarskog.se> wrote:
>> Buzby (gb@.pumpupthe.net) writes:
>>> Have successfully installed MS SQL on my Win XP Pro machine, created
>>> tables, and a dsn, which is working fine in Dreamweaver. So far so
>>> good.
>>>
>>> When I run the page on IIS I get the following:-
>>>
>>> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
>>> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database
>>> requested in login 'MenuPlanner'. Login fails.
>>>
>>> I think it's permissions - anyone got any clues as to where to look?
>>
>> Sounds like the login has a default db which does not exist, or the
>> login does have access to. Use sp_helplogins to check, use sp_defaultdb
>> to change.
> Yea, but a DSN is being used so we have to believe that MenuPlanner is
> the name of the DSN Connection. I am assuming that the DSN was created
> on the IIS server and connects successfully when you "test connection"
> in the ODBC dialog.

Not sure what you mean, but since SQL Server does not know what a DSN
is, MenuPlanner cannot be the name of the DNS. But it can be the
login name specified in the DSN.

> I highly recommend using a DSN-less connection in your ASP pages.

I echo that. DSN is a concept that I never understood the point with.
An extra layer that only causes hassle.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks one and all - it turned out it was an IIS permissions issue - however
I've taken on board what you have suggested and dsn less is the way we are
going!

Cheers

Buzby