change MSDB owner: drop

Showing posts with label drop. Show all posts

Thursday, March 8, 2012

Change the size of drop down parameter box

Im trying to make it so my drop down box on the parameter for my report
automatically fits or at least I can specify the size. Im using ssrs 2005
and there is a sroll bar on on both sides. I would like to increase the size
so I dont have these but dont know how to. PLEASE HELP!!!!On Jun 28, 12:04 pm, OWeston <OWes...@.discussions.microsoft.com>
wrote:
> Im trying to make it so my drop down box on the parameter for my report
> automatically fits or at least I can specify the size. Im using ssrs 2005
> and there is a sroll bar on on both sides. I would like to increase the size
> so I dont have these but dont know how to. PLEASE HELP!!!!
This is a pretty regular request on this news group. Currently, this
type of property cannot be controlled; but, hopefully it will be
available in the near future (perhaps w/SSRS 2008). Sorry that I could
not be of greater assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||Is there a fix/update for this yet?
"EMartinez" wrote:
> On Jun 28, 12:04 pm, OWeston <OWes...@.discussions.microsoft.com>
> wrote:
> > Im trying to make it so my drop down box on the parameter for my report
> > automatically fits or at least I can specify the size. Im using ssrs 2005
> > and there is a sroll bar on on both sides. I would like to increase the size
> > so I dont have these but dont know how to. PLEASE HELP!!!!
>
> This is a pretty regular request on this news group. Currently, this
> type of property cannot be controlled; but, hopefully it will be
> available in the near future (perhaps w/SSRS 2008). Sorry that I could
> not be of greater assistance.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Jul 10, 1:14 pm, JMD <J...@.discussions.microsoft.com> wrote:
> Is there a fix/update for this yet?
> "EMartinez" wrote:
> > On Jun 28, 12:04 pm, OWeston <OWes...@.discussions.microsoft.com>
> > wrote:
> > > Im trying to make it so my drop down box on the parameter for my report
> > > automatically fits or at least I can specify the size. Im using ssrs 2005
> > > and there is a sroll bar on on both sides. I would like to increase the size
> > > so I dont have these but dont know how to. PLEASE HELP!!!!
> > This is a pretty regular request on this news group. Currently, this
> > type of property cannot be controlled; but, hopefully it will be
> > available in the near future (perhaps w/SSRS 2008). Sorry that I could
> > not be of greater assistance.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
I've checked Microsoft.com and haven't found anything available yet.
Regards,
Enrique Martinez
Sr. Software Consultant

Wednesday, March 7, 2012

Change the name of the database from keyboard

When a new window opens in the Query Analyser allmost everytime I need to change the name of the Database from the drop down list.For that I have to click the drop down list in the bar and change.What is the short cut key for that?I mean how can I change the name of the database in the QA from the keyboard without using mouse?

SubhasishOriginally posted by subhasishray
When a new window opens in the Query Analyser allmost everytime I need to change the name of the Database from the drop down list.For that I have to click the drop down list in the bar and change.What is the short cut key for that?I mean how can I change the name of the database in the QA from the keyboard without using mouse?

Subhasish

Do mean change db using code or simply using the keyboard?

u can change the db simply using the keyboard by 'Ctrl-U' and then selecting the db using the up and down arrows.|||or try

use <database name>

Saturday, February 25, 2012

Change structure in Db

Hi.
How I can change a structure(add/drop columns or add st.
procedures) in databases which are involved in Merge
Replication process? I'm using SQL Server 2000.
Thank you.
use sp_repladdcolumn and sp_repldropcolumn

Thursday, February 16, 2012

change precision in a table column

Running SQL 2K sp3a, db is on compatibility level 65. I need to change the
precision of one column in a table. I scrioted the drop and recrete of the
table in EM. Made the change I needed to the precision on the one column in
the table then tested the script before running it. Got a "incorrect syntax
near Collate" when test script. Any idea why I would get this since SQL made
the script for me? If I'm recreating the table like it was save for higher
precision on one column is there anything I need to do concerning Views,
Triggers, keys, indexes, etc? I have the table data copied to another like
table in another db. I know this is probably basic type stuff but I just
know basic SQL suff and how to use EM. Any guideance would be appreciated.
ThanksSeems like EM scripting include some features which isn't available in 6.5. COLLATE is new for SQL
Server 2000.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
news:F2328B08-F6BD-4FB5-B6BF-181880000E78@.microsoft.com...
> Running SQL 2K sp3a, db is on compatibility level 65. I need to change the
> precision of one column in a table. I scrioted the drop and recrete of the
> table in EM. Made the change I needed to the precision on the one column in
> the table then tested the script before running it. Got a "incorrect syntax
> near Collate" when test script. Any idea why I would get this since SQL made
> the script for me? If I'm recreating the table like it was save for higher
> precision on one column is there anything I need to do concerning Views,
> Triggers, keys, indexes, etc? I have the table data copied to another like
> table in another db. I know this is probably basic type stuff but I just
> know basic SQL suff and how to use EM. Any guideance would be appreciated.
> Thanks|||is there any danger in changing the db compatibility to 80, makeing the
change to the table, then changing db back to 65?
"Tibor Karaszi" wrote:
> Seems like EM scripting include some features which isn't available in 6.5. COLLATE is new for SQL
> Server 2000.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
> news:F2328B08-F6BD-4FB5-B6BF-181880000E78@.microsoft.com...
> > Running SQL 2K sp3a, db is on compatibility level 65. I need to change the
> > precision of one column in a table. I scrioted the drop and recrete of the
> > table in EM. Made the change I needed to the precision on the one column in
> > the table then tested the script before running it. Got a "incorrect syntax
> > near Collate" when test script. Any idea why I would get this since SQL made
> > the script for me? If I'm recreating the table like it was save for higher
> > precision on one column is there anything I need to do concerning Views,
> > Triggers, keys, indexes, etc? I have the table data copied to another like
> > table in another db. I know this is probably basic type stuff but I just
> > know basic SQL suff and how to use EM. Any guideance would be appreciated.
> > Thanks
>|||That should be fine. But why not quite simply use some search and replace to remove the non-65
compatible stuff from the script?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
news:862BBD13-1138-4840-916F-2939861A0195@.microsoft.com...
> is there any danger in changing the db compatibility to 80, makeing the
> change to the table, then changing db back to 65?
> "Tibor Karaszi" wrote:
>> Seems like EM scripting include some features which isn't available in 6.5. COLLATE is new for
>> SQL
>> Server 2000.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
>> news:F2328B08-F6BD-4FB5-B6BF-181880000E78@.microsoft.com...
>> > Running SQL 2K sp3a, db is on compatibility level 65. I need to change the
>> > precision of one column in a table. I scrioted the drop and recrete of the
>> > table in EM. Made the change I needed to the precision on the one column in
>> > the table then tested the script before running it. Got a "incorrect syntax
>> > near Collate" when test script. Any idea why I would get this since SQL made
>> > the script for me? If I'm recreating the table like it was save for higher
>> > precision on one column is there anything I need to do concerning Views,
>> > Triggers, keys, indexes, etc? I have the table data copied to another like
>> > table in another db. I know this is probably basic type stuff but I just
>> > know basic SQL suff and how to use EM. Any guideance would be appreciated.
>> > Thanks
>>|||I have no idea how to do that or even what that feature your refering to is.
If it removes it from script then how would I get table recreated properly
so it works with the application?
"Tibor Karaszi" wrote:
> That should be fine. But why not quite simply use some search and replace to remove the non-65
> compatible stuff from the script?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
> news:862BBD13-1138-4840-916F-2939861A0195@.microsoft.com...
> > is there any danger in changing the db compatibility to 80, makeing the
> > change to the table, then changing db back to 65?
> >
> > "Tibor Karaszi" wrote:
> >
> >> Seems like EM scripting include some features which isn't available in 6.5. COLLATE is new for
> >> SQL
> >> Server 2000.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
> >> news:F2328B08-F6BD-4FB5-B6BF-181880000E78@.microsoft.com...
> >> > Running SQL 2K sp3a, db is on compatibility level 65. I need to change the
> >> > precision of one column in a table. I scrioted the drop and recrete of the
> >> > table in EM. Made the change I needed to the precision on the one column in
> >> > the table then tested the script before running it. Got a "incorrect syntax
> >> > near Collate" when test script. Any idea why I would get this since SQL made
> >> > the script for me? If I'm recreating the table like it was save for higher
> >> > precision on one column is there anything I need to do concerning Views,
> >> > Triggers, keys, indexes, etc? I have the table data copied to another like
> >> > table in another db. I know this is probably basic type stuff but I just
> >> > know basic SQL suff and how to use EM. Any guideance would be appreciated.
> >> > Thanks
> >>
> >>
>|||If you don't feel confident doing it, I'd recommend upping it to the higher level, run the scripts
and then lowering compat level again.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
news:CDA93918-06F0-4D01-AE9D-AC1376E79D93@.microsoft.com...
>I have no idea how to do that or even what that feature your refering to is.
> If it removes it from script then how would I get table recreated properly
> so it works with the application?
> "Tibor Karaszi" wrote:
>> That should be fine. But why not quite simply use some search and replace to remove the non-65
>> compatible stuff from the script?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
>> news:862BBD13-1138-4840-916F-2939861A0195@.microsoft.com...
>> > is there any danger in changing the db compatibility to 80, makeing the
>> > change to the table, then changing db back to 65?
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> Seems like EM scripting include some features which isn't available in 6.5. COLLATE is new for
>> >> SQL
>> >> Server 2000.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >>
>> >>
>> >> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
>> >> news:F2328B08-F6BD-4FB5-B6BF-181880000E78@.microsoft.com...
>> >> > Running SQL 2K sp3a, db is on compatibility level 65. I need to change the
>> >> > precision of one column in a table. I scrioted the drop and recrete of the
>> >> > table in EM. Made the change I needed to the precision on the one column in
>> >> > the table then tested the script before running it. Got a "incorrect syntax
>> >> > near Collate" when test script. Any idea why I would get this since SQL made
>> >> > the script for me? If I'm recreating the table like it was save for higher
>> >> > precision on one column is there anything I need to do concerning Views,
>> >> > Triggers, keys, indexes, etc? I have the table data copied to another like
>> >> > table in another db. I know this is probably basic type stuff but I just
>> >> > know basic SQL suff and how to use EM. Any guideance would be appreciated.
>> >> > Thanks
>> >>
>> >>
>>|||ok thanks
"Tibor Karaszi" wrote:
> If you don't feel confident doing it, I'd recommend upping it to the higher level, run the scripts
> and then lowering compat level again.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
> news:CDA93918-06F0-4D01-AE9D-AC1376E79D93@.microsoft.com...
> >I have no idea how to do that or even what that feature your refering to is.
> > If it removes it from script then how would I get table recreated properly
> > so it works with the application?
> >
> > "Tibor Karaszi" wrote:
> >
> >> That should be fine. But why not quite simply use some search and replace to remove the non-65
> >> compatible stuff from the script?
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
> >> news:862BBD13-1138-4840-916F-2939861A0195@.microsoft.com...
> >> > is there any danger in changing the db compatibility to 80, makeing the
> >> > change to the table, then changing db back to 65?
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> >> Seems like EM scripting include some features which isn't available in 6.5. COLLATE is new for
> >> >> SQL
> >> >> Server 2000.
> >> >>
> >> >> --
> >> >> Tibor Karaszi, SQL Server MVP
> >> >> http://www.karaszi.com/sqlserver/default.asp
> >> >> http://www.solidqualitylearning.com/
> >> >>
> >> >>
> >> >> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
> >> >> news:F2328B08-F6BD-4FB5-B6BF-181880000E78@.microsoft.com...
> >> >> > Running SQL 2K sp3a, db is on compatibility level 65. I need to change the
> >> >> > precision of one column in a table. I scrioted the drop and recrete of the
> >> >> > table in EM. Made the change I needed to the precision on the one column in
> >> >> > the table then tested the script before running it. Got a "incorrect syntax
> >> >> > near Collate" when test script. Any idea why I would get this since SQL made
> >> >> > the script for me? If I'm recreating the table like it was save for higher
> >> >> > precision on one column is there anything I need to do concerning Views,
> >> >> > Triggers, keys, indexes, etc? I have the table data copied to another like
> >> >> > table in another db. I know this is probably basic type stuff but I just
> >> >> > know basic SQL suff and how to use EM. Any guideance would be appreciated.
> >> >> > Thanks
> >> >>
> >> >>
> >>
> >>
>|||Hi Brian,
Just jump in to check if Tibor 's suggestion helped you? Feel free to post
back if you still have any concerns.
Have a good day!
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================Get Secure! - www.microsoft.com/security
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================>>Thread-Topic: change precision in a table column
>>thread-index: AccKg2LRdt7Sq4j4TtuTHvjcqTsv3w==>>X-WBNR-Posting-Host: 162.42.230.150
>>From: =?Utf-8?B?QnJpYW4=?= <c49a36a4-2142028833@.news.postalias>
>>References: <F2328B08-F6BD-4FB5-B6BF-181880000E78@.microsoft.com>
<uGcHmolCHHA.4024@.TK2MSFTNGP04.phx.gbl>
<862BBD13-1138-4840-916F-2939861A0195@.microsoft.com>
<O4i5hPmCHHA.4312@.TK2MSFTNGP06.phx.gbl>
<CDA93918-06F0-4D01-AE9D-AC1376E79D93@.microsoft.com>
<OcTyaxnCHHA.472@.TK2MSFTNGP04.phx.gbl>
>>Subject: Re: change precision in a table column
>>Date: Fri, 17 Nov 2006 12:03:01 -0800
>>Lines: 66
>>Message-ID: <2F3DD1CA-6CDF-4816-A58E-9B557C3B0E6A@.microsoft.com>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>>Newsgroups: microsoft.public.sqlserver.server
>>Path: TK2MSFTNGXA01.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:451835
>>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>ok thanks
>>"Tibor Karaszi" wrote:
>> If you don't feel confident doing it, I'd recommend upping it to the
higher level, run the scripts
>> and then lowering compat level again.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
>> news:CDA93918-06F0-4D01-AE9D-AC1376E79D93@.microsoft.com...
>> >I have no idea how to do that or even what that feature your refering
to is.
>> > If it removes it from script then how would I get table recreated
properly
>> > so it works with the application?
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> That should be fine. But why not quite simply use some search and
replace to remove the non-65
>> >> compatible stuff from the script?
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >>
>> >>
>> >> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
>> >> news:862BBD13-1138-4840-916F-2939861A0195@.microsoft.com...
>> >> > is there any danger in changing the db compatibility to 80,
makeing the
>> >> > change to the table, then changing db back to 65?
>> >> >
>> >> > "Tibor Karaszi" wrote:
>> >> >
>> >> >> Seems like EM scripting include some features which isn't
available in 6.5. COLLATE is new for
>> >> >> SQL
>> >> >> Server 2000.
>> >> >>
>> >> >> --
>> >> >> Tibor Karaszi, SQL Server MVP
>> >> >> http://www.karaszi.com/sqlserver/default.asp
>> >> >> http://www.solidqualitylearning.com/
>> >> >>
>> >> >>
>> >> >> "Brian" <c49a36a4-2142028833@.news.postalias> wrote in message
>> >> >> news:F2328B08-F6BD-4FB5-B6BF-181880000E78@.microsoft.com...
>> >> >> > Running SQL 2K sp3a, db is on compatibility level 65. I need
to change the
>> >> >> > precision of one column in a table. I scrioted the drop and
recrete of the
>> >> >> > table in EM. Made the change I needed to the precision on the
one column in
>> >> >> > the table then tested the script before running it. Got a
"incorrect syntax
>> >> >> > near Collate" when test script. Any idea why I would get this
since SQL made
>> >> >> > the script for me? If I'm recreating the table like it was
save for higher
>> >> >> > precision on one column is there anything I need to do
concerning Views,
>> >> >> > Triggers, keys, indexes, etc? I have the table data copied to
another like
>> >> >> > table in another db. I know this is probably basic type stuff
but I just
>> >> >> > know basic SQL suff and how to use EM. Any guideance would be
appreciated.
>> >> >> > Thanks
>> >> >>
>> >> >>
>> >>
>> >>
>>

change precision in a table column

Tuesday, February 14, 2012

Change owner of User Defined Data Types

Please let me know if there is a method for changing the owner of existing User Defined Data Types. I cannot drop and recreate them as the datatypes are in use.
Thanks.Try, sp_changeobjectowner.
Refer to BOL for more information.|||sp_changeobjectowner cannot be used to change the owner of UDTs as it only works with tables, views, user-defined functions and stored procedures.|||Then only way is drop and recreate.|||As I stated in my original post, it is not possible to drop them as they are in use.|||Use specified SP to change owner for that table, which would be applied by default. Apart from this I have no other idea.

Sunday, February 12, 2012

Change of User Defined Datatype

I want to change the user defined data type from varchar(5000) to
varchar(8000). Do I need to drop all the objects referencing the udt
and re-create them?Hi
Yes, Currently UDT's can not be changed, so a drop and re-create is
required. To drop it. it has to be removed from all the objects that depend
on it.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fred" <fredericksiu@.hotmail.com> wrote in message
news:a5795dd.0411152215.17971860@.posting.google.com...
> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?|||Actually, instead of dropping the objects that reference it, you may change
the data type of the columns to the native data type and then change it
back..This is the primary reason I do not use UDTs...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Fred" <fredericksiu@.hotmail.com> wrote in message
news:a5795dd.0411152215.17971860@.posting.google.com...
> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?|||"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<#xLY9e9yEHA.1264@.TK2MSFTNGP12.phx.gbl>...
> Actually, instead of dropping the objects that reference it, you may change
> the data type of the columns to the native data type and then change it
> back..This is the primary reason I do not use UDTs...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Fred" <fredericksiu@.hotmail.com> wrote in message
> news:a5795dd.0411152215.17971860@.posting.google.com...
> > I want to change the user defined data type from varchar(5000) to
> > varchar(8000). Do I need to drop all the objects referencing the udt
> > and re-create them?
Thanks a lot.|||why not use a tool to do it instead of all that manual labour?
check out DB Ghost at www.dbghost.com
DB Ghostâ?¢ provides you with a fully automated BUILD, COMPARISON and
SYNCHRONIZATION capability for your SQL Server databases and is the only
product on the market that ensures database integrity as DB Ghostâ?¢ will build
your database directly from your source control system. No other product in
the world does this. No other product can build, compare and synchronize a
target database making it match the source scripts precisely, every single
time, not just sometimes, but every single time. Try and prove us wrong.
Something else that might grab your interest is that an incredible 94% of
our clients (94%!!!) previously purchased our competitors products and soon
found that in the real world, these products let them down time after time.
Don't make the same mistake - why would you buy from our competitors who, for
similar money, can only offer you tools that don't build, and only compare
and sometimes synchronize...food for thought?
"Fred" wrote:
> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?
>

Change of User Defined Datatype

I want to change the user defined data type from varchar(5000) to
varchar(8000). Do I need to drop all the objects referencing the udt
and re-create them?
Hi
Yes, Currently UDT's can not be changed, so a drop and re-create is
required. To drop it. it has to be removed from all the objects that depend
on it.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fred" <fredericksiu@.hotmail.com> wrote in message
news:a5795dd.0411152215.17971860@.posting.google.co m...
> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?
|||Actually, instead of dropping the objects that reference it, you may change
the data type of the columns to the native data type and then change it
back..This is the primary reason I do not use UDTs...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Fred" <fredericksiu@.hotmail.com> wrote in message
news:a5795dd.0411152215.17971860@.posting.google.co m...
> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?
|||"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<#xLY9e9yEHA.1264@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Actually, instead of dropping the objects that reference it, you may change
> the data type of the columns to the native data type and then change it
> back..This is the primary reason I do not use UDTs...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Fred" <fredericksiu@.hotmail.com> wrote in message
> news:a5795dd.0411152215.17971860@.posting.google.co m...
Thanks a lot.
|||why not use a tool to do it instead of all that manual labour?
check out DB Ghost at www.dbghost.com
DB Ghost? provides you with a fully automated BUILD, COMPARISON and
SYNCHRONIZATION capability for your SQL Server databases and is the only
product on the market that ensures database integrity as DB Ghost? will build
your database directly from your source control system. No other product in
the world does this. No other product can build, compare and synchronize a
target database making it match the source scripts precisely, every single
time, not just sometimes, but every single time. Try and prove us wrong.
Something else that might grab your interest is that an incredible 94% of
our clients (94%!!!) previously purchased our competitors products and soon
found that in the real world, these products let them down time after time.
Don't make the same mistake - why would you buy from our competitors who, for
similar money, can only offer you tools that don't build, and only compare
and sometimes synchronize...food for thought?
"Fred" wrote:

> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?
>

Change of User Defined Datatype

I want to change the user defined data type from varchar(5000) to
varchar(8000). Do I need to drop all the objects referencing the udt
and re-create them?Hi
Yes, Currently UDT's can not be changed, so a drop and re-create is
required. To drop it. it has to be removed from all the objects that depend
on it.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fred" <fredericksiu@.hotmail.com> wrote in message
news:a5795dd.0411152215.17971860@.posting.google.com...
> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?|||Actually, instead of dropping the objects that reference it, you may change
the data type of the columns to the native data type and then change it
back..This is the primary reason I do not use UDTs...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Fred" <fredericksiu@.hotmail.com> wrote in message
news:a5795dd.0411152215.17971860@.posting.google.com...
> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?|||"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<#xLY9e9yEHA.1264
@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Actually, instead of dropping the objects that reference it, you may chang
e
> the data type of the columns to the native data type and then change it
> back..This is the primary reason I do not use UDTs...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Fred" <fredericksiu@.hotmail.com> wrote in message
> news:a5795dd.0411152215.17971860@.posting.google.com...
Thanks a lot.|||why not use a tool to do it instead of all that manual labour?
check out DB Ghost at www.dbghost.com
DB Ghost? provides you with a fully automated BUILD, COMPARISON and
SYNCHRONIZATION capability for your SQL Server databases and is the only
product on the market that ensures database integrity as DB Ghost? will bu
ild
your database directly from your source control system. No other product in
the world does this. No other product can build, compare and synchronize a
target database making it match the source scripts precisely, every single
time, not just sometimes, but every single time. Try and prove us wrong.
Something else that might grab your interest is that an incredible 94% of
our clients (94%!!!) previously purchased our competitors products and soon
found that in the real world, these products let them down time after time.
Don't make the same mistake - why would you buy from our competitors who, fo
r
similar money, can only offer you tools that don't build, and only compare
and sometimes synchronize...food for thought?
"Fred" wrote:

> I want to change the user defined data type from varchar(5000) to
> varchar(8000). Do I need to drop all the objects referencing the udt
> and re-create them?
>

Thursday, March 8, 2012

Change the size of drop down parameter box

Wednesday, March 7, 2012

Change the name of the database from keyboard

Saturday, February 25, 2012

Change structure in Db

Thursday, February 16, 2012

change precision in a table column

change precision in a table column

change precision in a table column

Tuesday, February 14, 2012

Change owner of User Defined Data Types

Sunday, February 12, 2012

Change of User Defined Datatype

Change of User Defined Datatype

Change of User Defined Datatype

change MSDB owner

Blog Archive

About Me