Hi - I want to change the precision/scale on a decimal datatype on a field
which is in a replicated table (merge). I tried to alter the field on the
publisher but I receive a message saying that I can't do this due to the
table being a replicated table.
Anyone know tips on how to do this (without removing replication). Thanks.
Hi Dave,
unfortunately you can't do this in merge.
Have a look at part (b) in this article for a workaround :
http://www.replicationanswers.com/AddColumn.asp
Alternatively you'll have to reinitialize in the case of merge.
Incidentally, this is no longer an issue in SQL Server 2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul.
I'll consider re-initialising as I don't have that much data yet and just
conducting tests now anyway. Do I have to pretty much drop replication, do
the changes and start again with merge replication set up?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:e5dKgDhrFHA.1132@.TK2MSFTNGP10.phx.gbl...
> Hi Dave,
> unfortunately you can't do this in merge.
> Have a look at part (b) in this article for a workaround :
> http://www.replicationanswers.com/AddColumn.asp
> Alternatively you'll have to reinitialize in the case of merge.
> Incidentally, this is no longer an issue in SQL Server 2005.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Dave - you don't need to drop replication as such - just the merge
publication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Showing posts with label precision. Show all posts
Showing posts with label precision. Show all posts
Tuesday, March 20, 2012
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
>> >> >>
>> >> >>
>> >>
>> >>
>>
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
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...
>
|||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...
>
|||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...
>
|||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.
================================================== ====
--[vbcol=seagreen]
<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>[vbcol=seagreen]
higher level, run the scripts[vbcol=seagreen]
to is.[vbcol=seagreen]
properly[vbcol=seagreen]
replace to remove the non-65[vbcol=seagreen]
makeing the[vbcol=seagreen]
available in 6.5. COLLATE is new for[vbcol=seagreen]
to change the[vbcol=seagreen]
recrete of the[vbcol=seagreen]
one column in[vbcol=seagreen]
"incorrect syntax[vbcol=seagreen]
since SQL made[vbcol=seagreen]
save for higher[vbcol=seagreen]
concerning Views,[vbcol=seagreen]
another like[vbcol=seagreen]
but I just[vbcol=seagreen]
appreciated.[vbcol=seagreen]
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...
>
|||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...
>
|||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...
>
|||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.
================================================== ====
--[vbcol=seagreen]
<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>[vbcol=seagreen]
higher level, run the scripts[vbcol=seagreen]
to is.[vbcol=seagreen]
properly[vbcol=seagreen]
replace to remove the non-65[vbcol=seagreen]
makeing the[vbcol=seagreen]
available in 6.5. COLLATE is new for[vbcol=seagreen]
to change the[vbcol=seagreen]
recrete of the[vbcol=seagreen]
one column in[vbcol=seagreen]
"incorrect syntax[vbcol=seagreen]
since SQL made[vbcol=seagreen]
save for higher[vbcol=seagreen]
concerning Views,[vbcol=seagreen]
another like[vbcol=seagreen]
but I just[vbcol=seagreen]
appreciated.[vbcol=seagreen]
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 mad
e
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 th
e
> precision of one column in a table. I scrioted the drop and recrete of th
e
> 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 synt
ax
> near Collate" when test script. Any idea why I would get this since SQL m
ade
> the script for me? If I'm recreating the table like it was save for highe
r
> 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 lik
e
> 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...
>|||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...[vbcol=seagreen]
> 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:
>|||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...
>|||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...[vbcol=seagreen]
>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:
>|||ok thanks
"Tibor Karaszi" wrote:
> If you don't feel confident doing it, I'd recommend upping it to the highe
r 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...
>|||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.
========================================
==============
--[vbcol=seagreen]
<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>[vbcol=seagreen]
higher level, run the scripts[vbcol=seagreen]
to is.[vbcol=seagreen]
properly[vbcol=seagreen]
replace to remove the non-65[vbcol=seagreen]
makeing the[vbcol=seagreen]
available in 6.5. COLLATE is new for[vbcol=seagreen]
to change the[vbcol=seagreen]
recrete of the[vbcol=seagreen]
one column in[vbcol=seagreen]
"incorrect syntax[vbcol=seagreen]
since SQL made[vbcol=seagreen]
save for higher[vbcol=seagreen]
concerning Views,[vbcol=seagreen]
another like[vbcol=seagreen]
but I just[vbcol=seagreen]
appreciated.[vbcol=seagreen]
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 mad
e
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 th
e
> precision of one column in a table. I scrioted the drop and recrete of th
e
> 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 synt
ax
> near Collate" when test script. Any idea why I would get this since SQL m
ade
> the script for me? If I'm recreating the table like it was save for highe
r
> 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 lik
e
> 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...
>|||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...[vbcol=seagreen]
> 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:
>|||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...
>|||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...[vbcol=seagreen]
>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:
>|||ok thanks
"Tibor Karaszi" wrote:
> If you don't feel confident doing it, I'd recommend upping it to the highe
r 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...
>|||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.
========================================
==============
--[vbcol=seagreen]
<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>[vbcol=seagreen]
higher level, run the scripts[vbcol=seagreen]
to is.[vbcol=seagreen]
properly[vbcol=seagreen]
replace to remove the non-65[vbcol=seagreen]
makeing the[vbcol=seagreen]
available in 6.5. COLLATE is new for[vbcol=seagreen]
to change the[vbcol=seagreen]
recrete of the[vbcol=seagreen]
one column in[vbcol=seagreen]
"incorrect syntax[vbcol=seagreen]
since SQL made[vbcol=seagreen]
save for higher[vbcol=seagreen]
concerning Views,[vbcol=seagreen]
another like[vbcol=seagreen]
but I just[vbcol=seagreen]
appreciated.[vbcol=seagreen]
Subscribe to:
Posts (Atom)