I'm having trouble with the UDF's I had in SQL 2000 that were migrated to SQL 2005 under the SCALAR FUNCTION item. Before in 2000 you just created the UDF, named it and saved. IN SQL 2005 you create/modify and then have to save it as a .SQL file to a folder. First of all, what folder should it go to so that all can use and secondly, when I do this and run the functions it doesn't work... I need to modify the scalar function and
save it with out saving to a .SQL file. How do I do this or is this the new way to create/modify functions. Any help is much appreciated
thanksHuh? I don't know what you are talking about. I've created functions in 2005 using the same code as in 2000.
Here is an example of a scalar function I created in 2005:create function [dbo].[CleanText](@.TextString varchar(max))
returns varchar(max)
as
begin
return replace(@.TextString, char(14), '')
end|||Understood. But how do you save them, does it ask you to save them to a .SQL file? Can you tell me the steps to modifying an existing scalar and saving...
thx|||The code I gave you creates a UDF in the database. As with any code you edit in Management Studio (or the old Query Analyzer), when you exit the program it prompts you whether you want to save your code to a file. Whether you want a copy of the script on your hard drive is up to you, and has nothing to do with the operation of the database.
To edit a function, right click on the function in Management Studio and select Modify. When you are through editing the code, run the script to execute it.|||Here is what I'm doing.
Go to Management Studio
Select Database Engine
Select DB working with
Select Programmability
Select Functions/Scalar
Right pane select function
Modify function
Tab pops up in right pane named ...SQLquery4.SQL
Right click it asks to save I say Yes, goes to dialog asks for name
I then close. When I open the function again, change wasn't made.
What am I doing wrong.
thx|||Thank You Execute Is The Key|||...or just hit F5.
Showing posts with label migrated. Show all posts
Showing posts with label migrated. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
Need help
Hi,
We have publisher and remote distributor with lot of transactional and
merge publications. (SQL2K SP3)
Recently we migrated our publisher to a new machine.
Today I renamed my old publisher server and tried to disable subscribers on
it (because everything works on a new publisher already).
When I did that via EM, all my replication agents on a distributor failed
(probably the old publisher wrote somethig to the distributor).
Then I marked (enabled) all subscribers back on that server (old publisher).
After that all merge replications became good again. Buh the transactional
ones don't work.
I get an error "The remote procedure call failed and did not execute"
Need help.
Thanks
Hi,
How did you rename the old publihser from EM? I'm not familiar with that capability.
-Matt
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
We have publisher and remote distributor with lot of transactional and
merge publications. (SQL2K SP3)
Recently we migrated our publisher to a new machine.
Today I renamed my old publisher server and tried to disable subscribers on
it (because everything works on a new publisher already).
When I did that via EM, all my replication agents on a distributor failed
(probably the old publisher wrote somethig to the distributor).
Then I marked (enabled) all subscribers back on that server (old publisher).
After that all merge replications became good again. Buh the transactional
ones don't work.
I get an error "The remote procedure call failed and did not execute"
Need help.
Thanks
Hi,
How did you rename the old publihser from EM? I'm not familiar with that capability.
-Matt
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Labels:
andmerge,
database,
distributor,
microsoft,
migrated,
mysql,
oracle,
publications,
publisher,
remote,
server,
sp3,
sql,
sql2k,
transactional
Monday, February 20, 2012
Near keyword in Full Text Search SQL server 2005
We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors are
returning exactly the same results, this behavior did not occur in SQL 2000.
example:
select count(*) from table1 where contains(*,'foo near bar') = 2494
select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
I have tried all of the syntax options I could find and am also able to
provide examples where foo and bar are quite far apart (~3000 characters) far
more than 50 words I've seen quoted for 2005. Appreciate if anyone has any
ideas on why. Do I need to change some setting in the SQL Server?
ThanksI reported this as a bug to Microsoft some time ago, and I was told that
this behavior is by design due to a customer request. Here is my original
post.
http://groups.google.com/group/microsoft.public.sqlserver.fulltext/msg/252dd1d3d6fedaa0?dmode=source
--
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
"so3" <so3@.discussions.microsoft.com> wrote in message
news:31E328D2-CB77-47A1-9B19-A319DBE29320@.microsoft.com...
> We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors
> are
> returning exactly the same results, this behavior did not occur in SQL
> 2000.
> example:
> select count(*) from table1 where contains(*,'foo near bar') = 2494
> select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
> I have tried all of the syntax options I could find and am also able to
> provide examples where foo and bar are quite far apart (~3000 characters)
> far
> more than 50 words I've seen quoted for 2005. Appreciate if anyone has
> any
> ideas on why. Do I need to change some setting in the SQL Server?
> Thanks
returning exactly the same results, this behavior did not occur in SQL 2000.
example:
select count(*) from table1 where contains(*,'foo near bar') = 2494
select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
I have tried all of the syntax options I could find and am also able to
provide examples where foo and bar are quite far apart (~3000 characters) far
more than 50 words I've seen quoted for 2005. Appreciate if anyone has any
ideas on why. Do I need to change some setting in the SQL Server?
ThanksI reported this as a bug to Microsoft some time ago, and I was told that
this behavior is by design due to a customer request. Here is my original
post.
http://groups.google.com/group/microsoft.public.sqlserver.fulltext/msg/252dd1d3d6fedaa0?dmode=source
--
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
"so3" <so3@.discussions.microsoft.com> wrote in message
news:31E328D2-CB77-47A1-9B19-A319DBE29320@.microsoft.com...
> We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors
> are
> returning exactly the same results, this behavior did not occur in SQL
> 2000.
> example:
> select count(*) from table1 where contains(*,'foo near bar') = 2494
> select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
> I have tried all of the syntax options I could find and am also able to
> provide examples where foo and bar are quite far apart (~3000 characters)
> far
> more than 50 words I've seen quoted for 2005. Appreciate if anyone has
> any
> ideas on why. Do I need to change some setting in the SQL Server?
> Thanks
Near keyword in Full Text Search SQL server 2005
We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors are
returning exactly the same results, this behavior did not occur in SQL 2000.
example:
select count(*) from table1 where contains(*,'foo near bar') = 2494
select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
I have tried all of the syntax options I could find and am also able to
provide examples where foo and bar are quite far apart (~3000 characters) fa
r
more than 50 words I've seen quoted for 2005. Appreciate if anyone has any
ideas on why. Do I need to change some setting in the SQL Server?
ThanksI reported this as a bug to Microsoft some time ago, and I was told that
this behavior is by design due to a customer request. Here is my original
post.
http://groups.google.com/group/micr...a0?dmode=source
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
"so3" <so3@.discussions.microsoft.com> wrote in message
news:31E328D2-CB77-47A1-9B19-A319DBE29320@.microsoft.com...
> We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors
> are
> returning exactly the same results, this behavior did not occur in SQL
> 2000.
> example:
> select count(*) from table1 where contains(*,'foo near bar') = 2494
> select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
> I have tried all of the syntax options I could find and am also able to
> provide examples where foo and bar are quite far apart (~3000 characters)
> far
> more than 50 words I've seen quoted for 2005. Appreciate if anyone has
> any
> ideas on why. Do I need to change some setting in the SQL Server?
> Thanks|||I reported this as a bug to Microsoft some time ago, and I was told that
this behavior is by design due to a customer request. Here is my original
post.
http://groups.google.com/group/micr...a0?dmode=source
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
"so3" <so3@.discussions.microsoft.com> wrote in message
news:31E328D2-CB77-47A1-9B19-A319DBE29320@.microsoft.com...
> We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors
> are
> returning exactly the same results, this behavior did not occur in SQL
> 2000.
> example:
> select count(*) from table1 where contains(*,'foo near bar') = 2494
> select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
> I have tried all of the syntax options I could find and am also able to
> provide examples where foo and bar are quite far apart (~3000 characters)
> far
> more than 50 words I've seen quoted for 2005. Appreciate if anyone has
> any
> ideas on why. Do I need to change some setting in the SQL Server?
> Thanks
returning exactly the same results, this behavior did not occur in SQL 2000.
example:
select count(*) from table1 where contains(*,'foo near bar') = 2494
select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
I have tried all of the syntax options I could find and am also able to
provide examples where foo and bar are quite far apart (~3000 characters) fa
r
more than 50 words I've seen quoted for 2005. Appreciate if anyone has any
ideas on why. Do I need to change some setting in the SQL Server?
ThanksI reported this as a bug to Microsoft some time ago, and I was told that
this behavior is by design due to a customer request. Here is my original
post.
http://groups.google.com/group/micr...a0?dmode=source
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
"so3" <so3@.discussions.microsoft.com> wrote in message
news:31E328D2-CB77-47A1-9B19-A319DBE29320@.microsoft.com...
> We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors
> are
> returning exactly the same results, this behavior did not occur in SQL
> 2000.
> example:
> select count(*) from table1 where contains(*,'foo near bar') = 2494
> select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
> I have tried all of the syntax options I could find and am also able to
> provide examples where foo and bar are quite far apart (~3000 characters)
> far
> more than 50 words I've seen quoted for 2005. Appreciate if anyone has
> any
> ideas on why. Do I need to change some setting in the SQL Server?
> Thanks|||I reported this as a bug to Microsoft some time ago, and I was told that
this behavior is by design due to a customer request. Here is my original
post.
http://groups.google.com/group/micr...a0?dmode=source
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
"so3" <so3@.discussions.microsoft.com> wrote in message
news:31E328D2-CB77-47A1-9B19-A319DBE29320@.microsoft.com...
> We've migrated to SQL 2005 and we are seeing that AND and NEAR opertors
> are
> returning exactly the same results, this behavior did not occur in SQL
> 2000.
> example:
> select count(*) from table1 where contains(*,'foo near bar') = 2494
> select count(*) from table1 where contains(*,'"foo" and "bar"') = 2494
> I have tried all of the syntax options I could find and am also able to
> provide examples where foo and bar are quite far apart (~3000 characters)
> far
> more than 50 words I've seen quoted for 2005. Appreciate if anyone has
> any
> ideas on why. Do I need to change some setting in the SQL Server?
> Thanks
Subscribe to:
Posts (Atom)