Thursday, March 29, 2012

Does SSAS allow implementation of SCD?

Can I implement a slowly changing dimension type 2 in SSAS. I am looking at creating an SSAS cube which can pull data directly from an operational OLTP database. The source database does not maitain history of changes for the dimensions, and I wanted to know if SSAS will help me keep that history by defining certain dimensions as a SCD. If so how do I define that rule. All tutorials I have read only skim on that topic and don't describe the steps/ways to define it in SSAS. Any help would be appreciated.

While you can use type 2 SCDs (and any other implementation of an SCD) in SSAS, it is not the thing that implements them.

You need to implement them in a Datamart/Datawarehouse and SSAS will then read them from there. What might be of interest to you is the Slowly Changing Dimension task in SSIS. It's not the quickest of components, but it does allow you to use a GUI to define the columns that you want to tracking history on.

Does SRS sql engine break things that used to work?

I've noticed that when I take stable SQL 2000 engines that are at SP3A where
the sqlservr executable is at build 8.00.760 and install SRS I get a new
build of the sql engine.
SQLServr.EXE build is 8.00.859 in SRS and things that used to work don't.
For example, stored procedure debug doesn't work at all on an SRS SQL Server.
I know I have seen a few other things that are now broke.
Does anyone know of any hotfixes that repair features that SRS breaks?RS doesn't do anything to the SQL Engine. If you are talkin about the 859
hotfix that we require in certain situations, there is a newer hotfix that
resolves the problem. You need to request it from product support. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;831997.
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:22305D8C-975B-4283-BC11-8264CDDEEB1E@.microsoft.com...
> I've noticed that when I take stable SQL 2000 engines that are at SP3A
> where
> the sqlservr executable is at build 8.00.760 and install SRS I get a new
> build of the sql engine.
> SQLServr.EXE build is 8.00.859 in SRS and things that used to work don't.
> For example, stored procedure debug doesn't work at all on an SRS SQL
> Server.
> I know I have seen a few other things that are now broke.
> Does anyone know of any hotfixes that repair features that SRS breaks?|||Thank-you for the quick reponse Brian.
I think maybe I wasn't too clear on my question.
If I install SQL Server 2000 Standard and then take it up to SP3A the build
level of my SQL engine is 760.
However, if I then apply SQL Reporting Services on top of this installation
my SQL engine gets taken up to build 859. Maybe this is not directly related
to SRS, but it certainly takes place upon installation of SRS.
At that point I no longer have the capability to debug stored procs (I
believe thru the sp_dbidbg xp).
So the downside is that I have to make a choice between having SRS and then
losing the capability of stored proc debug or not having SRS.
If there is a hotfix that addresses that I would love to have it.
thanks,
dan
"Brian Welcker [MS]" wrote:
> RS doesn't do anything to the SQL Engine. If you are talkin about the 859
> hotfix that we require in certain situations, there is a newer hotfix that
> resolves the problem. You need to request it from product support. See
> http://support.microsoft.com/default.aspx?scid=kb;en-us;831997.
>
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:22305D8C-975B-4283-BC11-8264CDDEEB1E@.microsoft.com...
> > I've noticed that when I take stable SQL 2000 engines that are at SP3A
> > where
> > the sqlservr executable is at build 8.00.760 and install SRS I get a new
> > build of the sql engine.
> >
> > SQLServr.EXE build is 8.00.859 in SRS and things that used to work don't.
> >
> > For example, stored procedure debug doesn't work at all on an SRS SQL
> > Server.
> >
> > I know I have seen a few other things that are now broke.
> >
> > Does anyone know of any hotfixes that repair features that SRS breaks?
>
>|||The RS setup proces does not touch the version of the SQL engine. We really
don't. We recommend a specific SQL engine hotfix during the installation
process that does do this. You would need to call product support for the
hotfix. I don't think it is generally downloadable.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:DA304849-A7E9-4A92-A39D-5E338227EF52@.microsoft.com...
> Thank-you for the quick reponse Brian.
> I think maybe I wasn't too clear on my question.
> If I install SQL Server 2000 Standard and then take it up to SP3A the
> build
> level of my SQL engine is 760.
> However, if I then apply SQL Reporting Services on top of this
> installation
> my SQL engine gets taken up to build 859. Maybe this is not directly
> related
> to SRS, but it certainly takes place upon installation of SRS.
> At that point I no longer have the capability to debug stored procs (I
> believe thru the sp_dbidbg xp).
> So the downside is that I have to make a choice between having SRS and
> then
> losing the capability of stored proc debug or not having SRS.
> If there is a hotfix that addresses that I would love to have it.
> thanks,
> dan
>
> "Brian Welcker [MS]" wrote:
>> RS doesn't do anything to the SQL Engine. If you are talkin about the 859
>> hotfix that we require in certain situations, there is a newer hotfix
>> that
>> resolves the problem. You need to request it from product support. See
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;831997.
>>
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Dan" <Dan@.discussions.microsoft.com> wrote in message
>> news:22305D8C-975B-4283-BC11-8264CDDEEB1E@.microsoft.com...
>> > I've noticed that when I take stable SQL 2000 engines that are at SP3A
>> > where
>> > the sqlservr executable is at build 8.00.760 and install SRS I get a
>> > new
>> > build of the sql engine.
>> >
>> > SQLServr.EXE build is 8.00.859 in SRS and things that used to work
>> > don't.
>> >
>> > For example, stored procedure debug doesn't work at all on an SRS SQL
>> > Server.
>> >
>> > I know I have seen a few other things that are now broke.
>> >
>> > Does anyone know of any hotfixes that repair features that SRS breaks?
>>sql

Does SQLSERVER support fuzzy text searching(like the function of agrep).

Does SQLSERVER support fuzzy text searching(like the function of agrep).
For example, given the input keyword [homogenos] and similarity
parameter [2 characters], the function will find out valid result from
datasource by either replacing,inserting or deleting upto two different
characters from word [homogenos].
Both homogenooos(homogeno[+oo]s) and homogeos(homoge[-n]os are valid
result.
thx.No, not directly. You need to build a function that does Levenstein Edit
distance. You will find an implementation of this in the Fuzzy functions
which ship with SSIS in SQL 2005.
You can also use the expansion options in the thesaurus capabilities in
FullText search so a search on homogenos could be expanded to search on
homogenos homogenoos, homogeneous or homogeos, but you have to know in
advance what all the expansions might be and hard code them into your
thesaurus file.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"zlf" <zlfcn@.hotmail.com> wrote in message
news:uGyRG55YGHA.4944@.TK2MSFTNGP02.phx.gbl...
> Does SQLSERVER support fuzzy text searching(like the function of agrep).
> For example, given the input keyword [homogenos] and similarity
> parameter [2 characters], the function will find out valid result from
> datasource by either replacing,inserting or deleting upto two different
> characters from word [homogenos].
> Both homogenooos(homogeno[+oo]s) and homogeos(homoge[-n]os are valid
> result.
> thx.
>

Does SQLSERVER support fuzzy text searching(like the function of a

functions are
SOUNDEX
DIFFERENCE
For freetext, try contains clause,
check CONTAINS in BOL
I hope this was what u were asking forThank you for your reply.
However, as I know, CONTAINS does not support the kind of fuzzy searching
described in my post.
And it is very likely that it does support it and I do not know how to use
it.
Can u show my a sample? Thank you again.
-- Original Message --
From: "Omnibuzz" <Omnibuzz@.discussions.microsoft.com>
Newsgroups: microsoft.public.sqlserver.programming
Sent: Wednesday, April 19, 2006 7:00 PM
Subject: RE: Does SQLSERVER support fuzzy text searching(like the function
of a
"Omnibuzz" <Omnibuzz@.discussions.microsoft.com> д?:43C1F9E4-4CA3-478D-9064-82AA8D
9DA35D@.microsoft.com...
> functions are
> SOUNDEX
> DIFFERENCE
> For freetext, try contains clause,
> check CONTAINS in BOL
> I hope this was what u were asking for|||Thank you for your reply.
However, as I know, CONTAINS does not support the kind of fuzzy searching
described in my post.
And it is very likely that it does support it and I do not know how to use
it.
Can u show my a sample? Thank you again.
-- Original Message --
From: "Omnibuzz" <Omnibuzz@.discussions.microsoft.com>
Newsgroups: microsoft.public.sqlserver.programming
Sent: Wednesday, April 19, 2006 7:00 PM
Subject: RE: Does SQLSERVER support fuzzy text searching(like the function
of a
"Omnibuzz" <Omnibuzz@.discussions.microsoft.com> д?:43C1F9E4-4CA3-478D-9064-82AA8D
9DA35D@.microsoft.com...
> functions are
> SOUNDEX
> DIFFERENCE
> For freetext, try contains clause,
> check CONTAINS in BOL
> I hope this was what u were asking for

does sqlserver install auto w/Small Bus Srv 2003

Does SQL server install automatically with SBS?
I did an install last night for a client, not at server
at this time.
Did this install auto?I do not believe that it is part of the automated setup.
Rand
This posting is provided "as is" with no warranties and confers no rights.

does sqlserver install auto w/Small Bus Srv 2003

Does SQL server install automatically with SBS?
I did an install last night for a client, not at server
at this time.
Did this install auto?I do not believe that it is part of the automated setup.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Does SQLMail require a mail account on the Exchange Server?

I just read that if you use an exchange server...the account that you
start SQL with needs a mail on the exchange box.

Is this true?

I know I didn't need an account when I've set it up before...but I
might have been using a POP3 server.

I have Outlook 2003 installed on the server. Windows 2003 Enterprise.

Thanks.Hi

If you are using SQL Mail you will need a MAPI profile, and if you are
connectng to an exchange server you will need an account on that server. You
could connect to a POP3 server or alternatively you could check out
http://www.sqldev.net/xp/xpsmtp.htm.

For more information check out
http://msdn.microsoft.com/library/d...erverE-mail.asp
http://support.microsoft.com/kb/281293
http://support.microsoft.com/kb/263556/
You may want to use an older version of Outlook, if you are POP3.

John

<mchi55@.yahoo.comwrote in message
news:1157150726.360290.48890@.i42g2000cwa.googlegro ups.com...

Quote:

Originally Posted by

>I just read that if you use an exchange server...the account that you
start SQL with needs a mail on the exchange box.
>
Is this true?
>
I know I didn't need an account when I've set it up before...but I
might have been using a POP3 server.
>
I have Outlook 2003 installed on the server. Windows 2003 Enterprise.
>
Thanks.
>

sql