db restoration via shared folder

I was reading the article on the subject above at the
http://examnotes.net/arch/178/2002/3/329543
The question here is:-
Testing was done and I was able to restore db using EM on
a Standard Edition (SP3) and mapped drive to another
server. Unlike I was unable to do that from a Enterprise
Edtion (SP3). Why is that so?
Thanks.So, you made certain that the SQL Server service has permissions on the
share and it still didn't work? What error message did you get?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"NG" <angiecmf@.hotmail.com> wrote in message
news:1101001c40fc1$4ab1af40$a501280a@.phx
.gbl...
> I was reading the article on the subject above at the
> http://examnotes.net/arch/178/2002/3/329543
> The question here is:-
> Testing was done and I was able to restore db using EM on
> a Standard Edition (SP3) and mapped drive to another
> server. Unlike I was unable to do that from a Enterprise
> Edtion (SP3). Why is that so?
> Thanks.|||Let me rephrase my question here, Sorry if my explaination
was not clear earlier.
Based on the article, I was able to backup/restore db
without any problem in MSSQL standard/enterprise edition.
The point here is the article stated that backup/restore
can't be done using Enterprise Manager. But I was able to
backup/restore db using Enterprise Manager in Standard
Edition but NOT Enterprise Edition. I was able to see the
mapped drive in the Standard Edition. Why I unable to
view the mapped drive in Enterprise Edition using the
Enterprise Manager? Is this a special feature in Standard
Edition or other setting need to be done here in order to
do so in the Enterprise Edition? Currently I am using
MSSQL 7 with sp(3) on NT4 (sp6).
Your help is much appreciated.

>--Original Message--
>So, you made certain that the SQL Server service has
permissions on the
>share and it still didn't work? What error message did
you get?
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"NG" <angiecmf@.hotmail.com> wrote in message
> news:1101001c40fc1$4ab1af40$a501280a@.phx
.gbl...
on
Enterprise
>
>.
>|||> Based on the article, I was able to backup/restore db
> without any problem in MSSQL standard/enterprise edition.
I assume that you used Query Analyzer for this, is that what you mean?

> The point here is the article stated that backup/restore
> can't be done using Enterprise Manager. But I was able to
> backup/restore db using Enterprise Manager in Standard
> Edition but NOT Enterprise Edition. I was able to see the
> mapped drive in the Standard Edition. Why I unable to
> view the mapped drive in Enterprise Edition using the
> Enterprise Manager? Is this a special feature in Standard
> Edition or other setting need to be done here in order to
> do so in the Enterprise Edition?
I won't read the article, but just be aware that it might be incorrect. Back
to the problem. Here's what I think is going on:
On one installation, the service account is the same as the one you are
logged in as. Hence, the mapped drives are the same. On the other, you are
using different accounts. The key point here is that mapped drives are per
user. And typically, you are not logged in using the same account as the SQL
Server service account. So what you perceive as a mapped drive is different
to what SQL Server does.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"NG" <angiecmf@.hotmail.com> wrote in message
news:11e7e01c4107a$848e7680$a101280a@.phx
.gbl...
> Let me rephrase my question here, Sorry if my explaination
> was not clear earlier.
> Based on the article, I was able to backup/restore db
> without any problem in MSSQL standard/enterprise edition.
> The point here is the article stated that backup/restore
> can't be done using Enterprise Manager. But I was able to
> backup/restore db using Enterprise Manager in Standard
> Edition but NOT Enterprise Edition. I was able to see the
> mapped drive in the Standard Edition. Why I unable to
> view the mapped drive in Enterprise Edition using the
> Enterprise Manager? Is this a special feature in Standard
> Edition or other setting need to be done here in order to
> do so in the Enterprise Edition? Currently I am using
> MSSQL 7 with sp(3) on NT4 (sp6).
> Your help is much appreciated.
>
> permissions on the
> you get?
> on
> Enterprise

Db Maint SMTP Alerter Question

I'm in the process of installing and configuring alerts using the
subject tool on our sql server 2000 instances but I've noticed a problem
with the tool and single-quotes. It seems any alert which returns a
single-quoted value in the message text generates incorrect code when
trying to execute xp_smtp_sendmail. For instance, as a test I created
an alert on error 208, Invalid object name '%.*ls'. Here is the code
that is created by Db SMTP Alerter:
EXEC master..xp_smtp_sendmail
@.FROM = 'eat@.joes.com'
,@.FROM_NAME = 'eat'
,@.priority = 'NORMAL'
,@.server = 'smtp.server.com'
,@.port = 25
,@.TO = 'eat@.joes.com'
,@.subject = 'Db Maint alerter: ''Test Alert'' occurred on \\SERVER.'
,@.message = 'SQL Server error text:
====================== Error: 208, Severity: 16, State: 1
Invalid object name 'TestObject'.
'
In order for the code to execute correctly, the 'TestObject' in @.message
should be ''TestObject''. That is, there should be double
single-quotes, not simply single-quotes. The ''Test Alert'' in @.subject
is correct, but throwing an apostrophe into the alert name will also
screw things up (ie ''Test'd Alert'' . Has anyone else using Db Maint
SMTP Alerter encounter this issue? The alert name issue is easy to
avoid, but there are several alerts I'd like to use that return
single-quoted values.I just checked the source code, and I do have a REPLACE for the message text. Perhaps you are using
an older version? Try downloading it from http://www.karaszi.com/SQLServer/util_smtp_alerter.asp and
see if that fixes it. If not, send me an e-mail and I can let you have the source code for fixing (I
don't have the resources to convert to FX 2.0, debug etc etc, I'm afraid).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DotComDBA" <noreply@.nospam.com> wrote in message news:O9VBgmLwGHA.5044@.TK2MSFTNGP05.phx.gbl...
> I'm in the process of installing and configuring alerts using the subject tool on our sql server
> 2000 instances but I've noticed a problem with the tool and single-quotes. It seems any alert
> which returns a single-quoted value in the message text generates incorrect code when trying to
> execute xp_smtp_sendmail. For instance, as a test I created an alert on error 208, Invalid object
> name '%.*ls'. Here is the code that is created by Db SMTP Alerter:
> EXEC master..xp_smtp_sendmail
> @.FROM = 'eat@.joes.com'
> ,@.FROM_NAME = 'eat'
> ,@.priority = 'NORMAL'
> ,@.server = 'smtp.server.com'
> ,@.port = 25
> ,@.TO = 'eat@.joes.com'
> ,@.subject = 'Db Maint alerter: ''Test Alert'' occurred on \\SERVER.'
> ,@.message = 'SQL Server error text:
> ======================> Error: 208, Severity: 16, State: 1
> Invalid object name 'TestObject'.
> '
> In order for the code to execute correctly, the 'TestObject' in @.message should be ''TestObject''.
> That is, there should be double single-quotes, not simply single-quotes. The ''Test Alert'' in
> @.subject is correct, but throwing an apostrophe into the alert name will also screw things up (ie
> ''Test'd Alert'' . Has anyone else using Db Maint SMTP Alerter encounter this issue? The alert
> name issue is easy to avoid, but there are several alerts I'd like to use that return
> single-quoted values.|||Tibor Karaszi wrote:
> I just checked the source code, and I do have a REPLACE for the message
> text. Perhaps you are using an older version? Try downloading it from
> http://www.karaszi.com/SQLServer/util_smtp_alerter.asp and see if that
> fixes it. If not, send me an e-mail and I can let you have the source
> code for fixing (I don't have the resources to convert to FX 2.0, debug
> etc etc, I'm afraid).
>
The current version works! Looks like I was using an older version
(downloaded from the dbmaint.com page). Thanks, Tibor!|||Glad it works. :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"DotComDBA" <noreply@.nospam.com> wrote in message news:uz6oioVwGHA.2232@.TK2MSFTNGP05.phx.gbl...
> Tibor Karaszi wrote:
>> I just checked the source code, and I do have a REPLACE for the message
>> text. Perhaps you are using an older version? Try downloading it from
>> http://www.karaszi.com/SQLServer/util_smtp_alerter.asp and see if that
>> fixes it. If not, send me an e-mail and I can let you have the source
>> code for fixing (I don't have the resources to convert to FX 2.0, debug
>> etc etc, I'm afraid).
> The current version works! Looks like I was using an older version
> (downloaded from the dbmaint.com page). Thanks, Tibor!