New SQL Server Registration

Hello,
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>

New SQL Server Registration

Hello,
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:

> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create
a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>

New lines in textarea

I need to be able to strip out newline characters from data stored in a
textarea, but I've been unable to locate data so far that tells me how
newlines/carriage returns are stored in SQL Server. Any help on this
is greatly appreciated.CHAR(13)+CHAR(10)
http://www.aspfaq.com/2188
<Joiey.Seeley@.gmail.com> wrote in message
news:1131462555.249672.14910@.g47g2000cwa.googlegroups.com...
>I need to be able to strip out newline characters from data stored in a
> textarea, but I've been unable to locate data so far that tells me how
> newlines/carriage returns are stored in SQL Server. Any help on this
> is greatly appreciated.
>|||You can run the following statements to remove CRLFs from a column within a
table
update testtable set col1 = REPLACE ( col1 , char(10) , '' )
update testtable set col1 = REPLACE ( col1 , char(13) , '' )
testtable is your table and col1 is the column you want to do the replace on
.
Hope this helps
--
Adam J Warne, MCDBA
"Joiey.Seeley@.gmail.com" wrote:

> I need to be able to strip out newline characters from data stored in a
> textarea, but I've been unable to locate data so far that tells me how
> newlines/carriage returns are stored in SQL Server. Any help on this
> is greatly appreciated.
>|||I tried to use this method on a TEXT field using the following:
update support_incident set problem = REPLACE ( problem , char(10) , '' )
update support_incident set col1 = REPLACE ( problem , char(13) , '' )
Got this error message:
Server: Msg 8116, Level 16, State 1, Line 1
Argument data type text is invalid for argument 1 of replace function.
Server: Msg 8116, Level 16, State 1, Line 2
Argument data type text is invalid for argument 1 of replace function.
--
Ray
How do you remove the CRLFs from a text field?
"Adam Warne" wrote:
> You can run the following statements to remove CRLFs from a column within
a
> table
> update testtable set col1 = REPLACE ( col1 , char(10) , '' )
> update testtable set col1 = REPLACE ( col1 , char(13) , '' )
> testtable is your table and col1 is the column you want to do the replace
on.
> Hope this helps
> --
> Adam J Warne, MCDBA
>
> "Joiey.Seeley@.gmail.com" wrote:
>|||http://www.aspfaq.com/2445
"Ray" <ray.smith@.loislaw.com> wrote in message
news:E1FD569C-3F54-42FB-8B45-8C28B04883A5@.microsoft.com...
>I tried to use this method on a TEXT field using the following:
> update support_incident set problem = REPLACE ( problem , char(10) , '' )
> update support_incident set col1 = REPLACE ( problem , char(13) , '' )
> Got this error message:
> Server: Msg 8116, Level 16, State 1, Line 1
> Argument data type text is invalid for argument 1 of replace function.
> Server: Msg 8116, Level 16, State 1, Line 2
> Argument data type text is invalid for argument 1 of replace function.
> --
> Ray
> How do you remove the CRLFs from a text field?
> "Adam Warne" wrote:
>

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the job.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I fully agree with Tracy. If you, for some strange reason, don't want to do this, I believe the
limit is a bit higher at the TSQL level (i.e., the GUI is the limiting factor), so you could have
some more by using sp_add_jobstep.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45BA5D73.3080102@.realsqlguy.com...
> Joe K. wrote:
>> I have a SQL Server 2000 database, I created a new job but I am unable to copy the 200 lines of
>> code that I created into the command section of the job.
>> Is there away to expand the New Job Command section? I cannot use another job step to resolve
>> this issue because I have alot variables and a cursor used in this job.
>> This problem is resolve in SQL Server 2005.
>> Please help me resolve this problem for SQL Server 2000.
>> Thank You,
>>
> 200 lines of code in a single job step? That's just insane. Put that code into a stored
> procedure, and then use a single EXEC statement in the job step.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the job.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,
Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the jo
b.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the
job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I fully agree with Tracy. If you, for some strange reason, don't want to do
this, I believe the
limit is a bit higher at the TSQL level (i.e., the GUI is the limiting facto
r), so you could have
some more by using sp_add_jobstep.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45BA5D73.3080102@.realsqlguy.co
m...
> Joe K. wrote:
> 200 lines of code in a single job step? That's just insane. Put that c
ode into a stored
> procedure, and then use a single EXEC statement in the job step.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com