emails reside in Inbox?

Hi,
I'm working on MS SqL 2K
and I have installed MS Outlook.
I've configured the SQL Mail and SQL Agent Mail.
when I use the xp_sendmail, the emails reside in the Inbox of the Outlook
and are not sent to the right recipients, so I should re-send them from
Outlook.
I'm missing something for sure, what is it?
thanks in advance.
jouj
Hi
Your emails should be sent, but at a guess your are using Outlook 2002 or
later in which case it has to be running on the server see
http://support.microsoft.com/default...b;en-us;263556
The easiest solution is to install Outlook 2000 or use xpsmtp
http://www.sqldev.net/xp/xpsmtp.htm
John
"jouj" <jouj@.discussions.microsoft.com> wrote in message
news:89B5CE19-71C3-41B4-B846-9CF844AAF58A@.microsoft.com...
> Hi,
> I'm working on MS SqL 2K
> and I have installed MS Outlook.
> I've configured the SQL Mail and SQL Agent Mail.
> when I use the xp_sendmail, the emails reside in the Inbox of the Outlook
> and are not sent to the right recipients, so I should re-send them from
> Outlook.
> I'm missing something for sure, what is it?
> thanks in advance.
> jouj
>

EM Crashes when I go to Database-> Properties

Ive got SQL 2005 Beta 2 installed along with my SQL 2K on my XP PC
Now when I go to SQL 2K EM .. And then right click on database and select
properties.. it crashes.. Have any of you observed that ? Let me know how I
can fix it.. I even tried rebooting and it doesnt help
ThanksHassan,
If the database in question is one of the SQL Server 2005 databases, you are
probably out of luck. Some pre-2005 tools will simply not work with SQL Se
rver 2005 because they can't support features that didn't exist when they we
re developed. If EM is broken when used with SQL Server 2000 databases, see
if this advice from Microsoft about a different EM problem helps.
Like the rest of the current version of SQL Express this is a pre-release ve
rsion, the permissions problem is a bug which we have resolved in the B2 bui
ld of SQL Server 2005. If you need to use EM before we update SQLDMO and Exp
ress, then go to the version of SQLDMO.dll thats in SQL Server 2000 director
y and execute regsvr32 sqldmo.dll. This should enable EM to work as it was b
efore against SQL Server 2000 but neither EM nor DMO will work against SQL E
xpress in this case.
If things like this didn't happen, it wouldn't be beta software...
Steve Kass
Drew University
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:OqF$jH6hEHA.1656@.TK2MSFTNGP09.phx.gbl
..
> Ive got SQL 2005 Beta 2 installed along with my SQL 2K on my XP PC
>
> Now when I go to SQL 2K EM .. And then right click on database and select
> properties.. it crashes.. Have any of you observed that ? Let me know how
I
> can fix it.. I even tried rebooting and it doesnt help
>
> Thanks
>
>

EM Crashes when I go to Database-> Properties

Ive got SQL 2005 Beta 2 installed along with my SQL 2K on my XP PC
Now when I go to SQL 2K EM .. And then right click on database and select
properties.. it crashes.. Have any of you observed that ? Let me know how I
can fix it.. I even tried rebooting and it doesnt help
Thanks
Hassan,
If the database in question is one of the SQL Server 2005 databases, you are probably out of luck. Some pre-2005 tools will simply not work with SQL Server 2005 because they can't support features that didn't exist when they were developed. If EM is broken when used with SQL Server 2000 databases, see if this advice from Microsoft about a different EM problem helps.
Like the rest of the current version of SQL Express this is a pre-release version, the permissions problem is a bug which we have resolved in the B2 build of SQL Server 2005. If you need to use EM before we update SQLDMO and Express, then go to the version of SQLDMO.dll thats in SQL Server 2000 directory and execute regsvr32 sqldmo.dll. This should enable EM to work as it was before against SQL Server 2000 but neither EM nor DMO will work against SQL Express in this case.
If things like this didn't happen, it wouldn't be beta software...
Steve Kass
Drew University
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:OqF$jH6hEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Ive got SQL 2005 Beta 2 installed along with my SQL 2K on my XP PC
> Now when I go to SQL 2K EM .. And then right click on database and select
> properties.. it crashes.. Have any of you observed that ? Let me know how I
> can fix it.. I even tried rebooting and it doesnt help
> Thanks
>

EM Crashes when I go to Database-> Properties

Ive got SQL 2005 Beta 2 installed along with my SQL 2K on my XP PC
Now when I go to SQL 2K EM .. And then right click on database and select
properties.. it crashes.. Have any of you observed that ? Let me know how I
can fix it.. I even tried rebooting and it doesnt help
ThanksThis is a multi-part message in MIME format.
--=_NextPart_000_02A4_01C4877F.250CD1D0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hassan,
If the database in question is one of the SQL Server 2005 databases, =you are probably out of luck. Some pre-2005 tools will simply not work =with SQL Server 2005 because they can't support features that didn't =exist when they were developed. If EM is broken when used with SQL =Server 2000 databases, see if this advice from Microsoft about a =different EM problem helps.
Like the rest of the current version of SQL Express this is a =pre-release version, the permissions problem is a bug which we have =resolved in the B2 build of SQL Server 2005. If you need to use EM =before we update SQLDMO and Express, then go to the version of =SQLDMO.dll thats in SQL Server 2000 directory and execute regsvr32 =sqldmo.dll. This should enable EM to work as it was before against SQL =Server 2000 but neither EM nor DMO will work against SQL Express in this =case. If things like this didn't happen, it wouldn't be beta software...
Steve Kass
Drew University
"Hassan" <fatima_ja@.hotmail.com> wrote in message =news:OqF$jH6hEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Ive got SQL 2005 Beta 2 installed along with my SQL 2K on my XP PC
> > Now when I go to SQL 2K EM .. And then right click on database and =select
> properties.. it crashes.. Have any of you observed that ? Let me know =how I
> can fix it.. I even tried rebooting and it doesnt help
> > Thanks
> >
--=_NextPart_000_02A4_01C4877F.250CD1D0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Hassan,
If the database in question is one of the SQL =Server 2005 databases, you are probably out of luck. Some pre-2005 tools =will simply not work with SQL Server 2005 because they can't support features =that didn't exist when they were developed. If EM is broken when used =with SQL Server 2000 databases, see if this advice from Microsoft about a =different EM problem helps.
Like the rest of the =current version of SQL Express this is a pre-release version, the permissions =problem is a bug which we have resolved in the B2 build of SQL Server 2005. If =you need to use EM before we update SQLDMO and Express, then go to the =version of SQLDMO.dll thats in SQL Server 2000 directory and execute regsvr32 =sqldmo.dll. This should enable EM to work as it was before against SQL Server 2000 =but neither EM nor DMO will work against SQL Express in this case. If things like this didn't happen, it wouldn't be =beta software...
Steve Kass
Drew University
"Hassan" wrote in =message news:OqF$jH6hEHA.1656@.TK2MSFTNGP09.phx.gbl...> Ive got SQL 2005 Beta 2 =installed along with my SQL 2K on my XP PC> > Now when I go to SQL 2K EM =.. And then right click on database and select> properties.. it =crashes.. Have any of you observed that ? Let me know how I> can fix it.. I even =tried rebooting and it doesnt help> > Thanks> >

---

--=_NextPart_000_02A4_01C4877F.250CD1D0--

Eliminating the expensive remote join

I've got a table (dexIndex) with 9 million rows in it. It's got an
identity column (index_id) and a column that's full-text indexed
(insureds_name) and a column that I want to filter on (agency_number).
When I query like this:
select * from decIndex where agency_number = '0349323' and
contains(insureds_name,'"SMITH"')
The execution plan involves a remote scan (98%) and a clustered index
seek (0%) which lead into a hash match/inner join (2%). The problem is
that the remote scan is returning 51,000 rows even though only 1 comes
out of the hash match/inner join. Thus, the query takes over a minute
on a built-to-the-hilt server.
Is there a way to have the FT engine only look through or return a
subset of the FT index, like only those rows which correspond to
agency_number = '0349323'?
I'd like to avoid adding agency_number to the FT index.
Thanks!
Regretably there is no way of doing this. One of the strategies of getting
around this problem is to partition your table according to the other
elements of you where clause. Another option is to build full text indexes
on indexed views in SQL 2005. Again the view would be of a section of your
table which would match your where conditions.
"Ryan Walberg [MCSD]" <generalpf@.nospam.yahoo.reallynospam.com> wrote in
message news:%233kbwJZJFHA.588@.TK2MSFTNGP15.phx.gbl...
> I've got a table (dexIndex) with 9 million rows in it. It's got an
> identity column (index_id) and a column that's full-text indexed
> (insureds_name) and a column that I want to filter on (agency_number).
> When I query like this:
> select * from decIndex where agency_number = '0349323' and
> contains(insureds_name,'"SMITH"')
> The execution plan involves a remote scan (98%) and a clustered index seek
> (0%) which lead into a hash match/inner join (2%). The problem is that
> the remote scan is returning 51,000 rows even though only 1 comes out of
> the hash match/inner join. Thus, the query takes over a minute on a
> built-to-the-hilt server.
> Is there a way to have the FT engine only look through or return a subset
> of the FT index, like only those rows which correspond to agency_number =
> '0349323'?
> I'd like to avoid adding agency_number to the FT index.
> Thanks!
|||Hilary Cotter wrote:
> Regretably there is no way of doing this. One of the strategies of getting
> around this problem is to partition your table according to the other
> elements of you where clause. Another option is to build full text indexes
> on indexed views in SQL 2005. Again the view would be of a section of your
> table which would match your where conditions.
I ended up clustering the index that corresponded to the unique column
for the full-text index and that sped it up a great deal.
Thanks,
Ryan

Editing table design

Is there anyway possible to edit table design with data already entered in the table.
If not, is there anyway I can cut and paste the info back in.
Ive tried importing to access and then back to SQL, however,
when i tried to view my table design in ASP.NET webmatrix, it gave me an error.Try the link below for ALTER Table in SQL Server. Run a search for same in SQL Server BOL(books online) to do the same in Enterprise Manager. Hope this helps.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_aa-az_3ied.asp