Wednesday, June 6, 2012

[sharepointdiscussions] Digest Number 4458

Messages In This Digest (6 Messages)

Messages

1a.

SQL Backup

Posted by: "onewisegeek" 1wisegeek@gmail.com   onewisegeek

Tue Jun 5, 2012 5:03 am (PDT)



We are evaluating a new backup method (the name is common with an old muscle car and a sport fish).

I received an error when configuring the SQL backup (SQL 2008):
one or more user databases are not using the full recovery model

Is there any advantage to do so?
Is there any gotcha's?

ALTER DATABASE databaseName
SET RECOVERY Simple | Full | Bulk_logged

1b.

Re: SQL Backup

Posted by: "pstork@att.net" pstork@att.net   pstorkoh

Tue Jun 5, 2012 5:44 am (PDT)



The difference between running SQL at Full or Simple depends on your service
levels.  If you are running the databases at Simple then you will only be able
to recover back to the point where your last backup was taken.  If you are at
Full and the Transaction log file isn't corrupt (like a disk crashing) then you
can recover back to the point of time when the system failed by restoring your
backup and replaying the transaction logs.  Most databases in SharePoint default
to FULL, but there are some that only run in Simple.  The following article
describes all the SharePoint databases and their default settings.

http://technet.microsoft.com/en-us/library/cc678868.aspx

If you don't require point of time disaster recovery then running the databases
at Simple is perfectly acceptable.
 Paul Papanek Stork

________________________________
From: onewisegeek <1wisegeek@gmail.com>
To: sharepointdiscussions@yahoogroups.com
Sent: Tue, June 5, 2012 8:03:31 AM
Subject: [sharepointdiscussions] SQL Backup

 
We are evaluating a new backup method (the name is common with an old muscle car
and a sport fish).

I received an error when configuring the SQL backup (SQL 2008):
one or more user databases are not using the full recovery model

Is there any advantage to do so?
Is there any gotcha's?

ALTER DATABASE databaseName
SET RECOVERY Simple | Full | Bulk_logged

[Non-text portions of this message have been removed]

2a.

FQDN in an email that refers to a created document

Posted by: "dfife_01" david@fife.cc   dfife_01

Tue Jun 5, 2012 6:55 am (PDT)



Greetings,

I am using a workflow to process a time off request. The issue I am having is in the email notification created by the workflow when the request is created, there is a click able link that refers back to the created time off request. The command I am using in the workflow is "[%Workflow Context:Current Item URL%]". The problem is the URL points to the computer name ( http://compname/request.doc instead of http://www.sharepointsite.com/request.doc), not the FQDN of the SharePoint site. This works fine if you are within the local network, but obviously not if you are outside the local network.

Any suggestions?

2b.

Re: FQDN in an email that refers to a created document

Posted by: "pstork@att.net" pstork@att.net   pstorkoh

Tue Jun 5, 2012 7:11 am (PDT)



I suspect that the servername is the default Zone AAM and the FQDN is in a
different Zone.  Make sure the default Zone AAM is the FQDN and move the
servername entry to a different zone.  The workflow is automatically picking up
the default Zone address.
 Paul Papanek Stork

________________________________
From: dfife_01 <david@fife.cc>
To: sharepointdiscussions@yahoogroups.com
Sent: Tue, June 5, 2012 9:55:43 AM
Subject: [sharepointdiscussions] FQDN in an email that refers to a created
document

 
Greetings,

I am using a workflow to process a time off request. The issue I am having is in
the email notification created by the workflow when the request is created,
there is a click able link that refers back to the created time off request. The
command I am using in the workflow is "[%Workflow Context:Current Item URL%]".
The problem is the URL points to the computer name ( http://compname/request.doc
instead of http://www.sharepointsite.com/request.doc), not the FQDN of the
SharePoint site. This works fine if you are within the local network, but
obviously not if you are outside the local network.

Any suggestions?

[Non-text portions of this message have been removed]

2c.

Re: FQDN in an email that refers to a created document

Posted by: "dfife_01" david@fife.cc   dfife_01

Tue Jun 5, 2012 8:12 am (PDT)



Thanks for the help. You are correct. However, anytime I try to make changes to AAM I get an error say I can't delete this entry. I have tried using the edit public URL function.

--- In sharepointdiscussions@yahoogroups.com, pstork@... wrote:
>
> I suspect that the servername is the default Zone AAM and the FQDN is in a
> different Zone.  Make sure the default Zone AAM is the FQDN and move the
> servername entry to a different zone.  The workflow is automatically picking up
> the default Zone address.
>  Paul Papanek Stork
>
>
>
>
>
> ________________________________
> From: dfife_01 <david@...>
> To: sharepointdiscussions@yahoogroups.com
> Sent: Tue, June 5, 2012 9:55:43 AM
> Subject: [sharepointdiscussions] FQDN in an email that refers to a created
> document
>
>  
> Greetings,
>
> I am using a workflow to process a time off request. The issue I am having is in
> the email notification created by the workflow when the request is created,
> there is a click able link that refers back to the created time off request. The
> command I am using in the workflow is "[%Workflow Context:Current Item URL%]".
> The problem is the URL points to the computer name ( http://compname/request.doc
> instead of http://www.sharepointsite.com/request.doc), not the FQDN of the
> SharePoint site. This works fine if you are within the local network, but
> obviously not if you are outside the local network.
>
>
> Any suggestions?
>
>
>
>
> [Non-text portions of this message have been removed]
>

2d.

Re: FQDN in an email that refers to a created document

Posted by: "dfife_01" david@fife.cc   dfife_01

Tue Jun 5, 2012 8:12 am (PDT)




When I try to make changes to AAM I get this error:

You must specify the default zone URL for all Web applications. To delete the Alternate URL Collection, remove the public URLs in all other zones, and then remove the default zone URL.

Suggestions?

--- In sharepointdiscussions@yahoogroups.com, pstork@... wrote:
>
> I suspect that the servername is the default Zone AAM and the FQDN is in a
> different Zone.  Make sure the default Zone AAM is the FQDN and move the
> servername entry to a different zone.  The workflow is automatically picking up
> the default Zone address.
>  Paul Papanek Stork
>
>
>
>
>
> ________________________________
> From: dfife_01 <david@...>
> To: sharepointdiscussions@yahoogroups.com
> Sent: Tue, June 5, 2012 9:55:43 AM
> Subject: [sharepointdiscussions] FQDN in an email that refers to a created
> document
>
>  
> Greetings,
>
> I am using a workflow to process a time off request. The issue I am having is in
> the email notification created by the workflow when the request is created,
> there is a click able link that refers back to the created time off request. The
> command I am using in the workflow is "[%Workflow Context:Current Item URL%]".
> The problem is the URL points to the computer name ( http://compname/request.doc
> instead of http://www.sharepointsite.com/request.doc), not the FQDN of the
> SharePoint site. This works fine if you are within the local network, but
> obviously not if you are outside the local network.
>
>
> Any suggestions?
>
>
>
>
> [Non-text portions of this message have been removed]
>

Recent Activity
Visit Your Group
Find helpful tips

for Moderators

on the Yahoo!

Groups team blog.

Yahoo! Groups

Dog Zone

Connect w/others

who love dogs.

New business?

Get new customers.

List your web site

in Yahoo! Search.

Need to Reply?

Click one of the "Reply" links to respond to a specific message in the Daily Digest.

Create New Topic | Visit Your Group on the Web

No comments: