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]