restore db from device in sql2005

Need to restore the db from network location.
After I click restore from device. The select path box is grayed out. I
could not type the network path.
(I know i could restore it in query analyzer by using restore code.)
Any ideas?
ThanksDid you press the ... button to the right of that text box?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mecn" <mecn2002@.yahoo.com> wrote in message news:ud2imO78GHA.4224@.TK2MSFTNGP02.phx.gbl...
> Need to restore the db from network location.
> After I click restore from device. The select path box is grayed out. I
> could not type the network path.
> (I know i could restore it in query analyzer by using restore code.)
> Any ideas?
> Thanks
>|||I did, Just let you select local divers only
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23mgSe1B9GHA.3916@.TK2MSFTNGP04.phx.gbl...
> Did you press the ... button to the right of that text box?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ud2imO78GHA.4224@.TK2MSFTNGP02.phx.gbl...
>> Need to restore the db from network location.
>> After I click restore from device. The select path box is grayed out. I
>> could not type the network path.
>> (I know i could restore it in query analyzer by using restore code.)
>> Any ideas?
>> Thanks|||mecn wrote:
> I did, Just let you select local divers only
>
Correct, you can't point/click to a network path, but you can TYPE the
path into the filename field on that same window...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The problem is I could not. The box is grayed out.
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
>> I did, Just let you select local divers only
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I couldn't type. Is it sort of permission issue?
Thanks
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
>> I did, Just let you select local divers only
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||sorry. you are saying that I could type the network path in to the file name
box?
i.e. \\network\servover\dir\abc.bak?
Thanks
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
>> I did, Just let you select local divers only
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I don't think taht you could type the path and file name into filename box.
Filename box is only for file name like abc.bak. right?!
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
>> I did, Just let you select local divers only
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I am sorry, you are right!!!! I could type the network path into file name
box and it works--THANK YOU VERY MUCH!!!@.!!
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
>> I did, Just let you select local divers only
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||mecn wrote:
> I am sorry, you are right!!!! I could type the network path into file name
> box and it works--THANK YOU VERY MUCH!!!@.!!
>
Great... Now that you've accomplished that, can you explain why this
was easier than just issuing the RESTORE DATABASE command in a query window?
Tracy McKibben
MCDBA
http://www.realsqlguy.com

restore db from device in sql2005

Need to restore the db from network location.
After I click restore from device. The select path box is grayed out. I
could not type the network path.
(I know i could restore it in query analyzer by using restore code.)
Any ideas?
Thanks
Did you press the ... button to the right of that text box?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mecn" <mecn2002@.yahoo.com> wrote in message news:ud2imO78GHA.4224@.TK2MSFTNGP02.phx.gbl...
> Need to restore the db from network location.
> After I click restore from device. The select path box is grayed out. I
> could not type the network path.
> (I know i could restore it in query analyzer by using restore code.)
> Any ideas?
> Thanks
>
|||I did, Just let you select local divers only
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23mgSe1B9GHA.3916@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Did you press the ... button to the right of that text box?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ud2imO78GHA.4224@.TK2MSFTNGP02.phx.gbl...
|||mecn wrote:
> I did, Just let you select local divers only
>
Correct, you can't point/click to a network path, but you can TYPE the
path into the filename field on that same window...
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||The problem is I could not. The box is grayed out.
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||I couldn't type. Is it sort of permission issue?
Thanks
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||sorry. you are saying that I could type the network path in to the file name
box?
i.e. \\network\servover\dir\abc.bak?
Thanks
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||I don't think taht you could type the path and file name into filename box.
Filename box is only for file name like abc.bak. right?!
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||I am sorry, you are right!!!! I could type the network path into file name
box and it works--THANK YOU VERY MUCH!!!@.!!
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||mecn wrote:
> I am sorry, you are right!!!! I could type the network path into file name
> box and it works--THANK YOU VERY MUCH!!!@.!!
>
Great... Now that you've accomplished that, can you explain why this
was easier than just issuing the RESTORE DATABASE command in a query window?
Tracy McKibben
MCDBA
http://www.realsqlguy.com

restore db from device in sql2005

Need to restore the db from network location.
After I click restore from device. The select path box is grayed out. I
could not type the network path.
(I know i could restore it in query analyzer by using restore code.)
Any ideas?
ThanksDid you press the ... button to the right of that text box?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mecn" <mecn2002@.yahoo.com> wrote in message news:ud2imO78GHA.4224@.TK2MSFTNGP02.phx.gbl...[v
bcol=seagreen]
> Need to restore the db from network location.
> After I click restore from device. The select path box is grayed out. I
> could not type the network path.
> (I know i could restore it in query analyzer by using restore code.)
> Any ideas?
> Thanks
>[/vbcol]|||I did, Just let you select local divers only
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23mgSe1B9GHA.3916@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Did you press the ... button to the right of that text box?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ud2imO78GHA.4224@.TK2MSFTNGP02.phx.gbl...|||mecn wrote:
> I did, Just let you select local divers only
>
Correct, you can't point/click to a network path, but you can TYPE the
path into the filename field on that same window...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The problem is I could not. The box is grayed out.
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I couldn't type. Is it sort of permission issue?
Thanks
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||sorry. you are saying that I could type the network path in to the file name
box?
i.e. \\network\servover\dir\abc.bak?
Thanks
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I don't think taht you could type the path and file name into filename box.
Filename box is only for file name like abc.bak. right?!
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I am sorry, you are right!!!! I could type the network path into file name
box and it works--THANK YOU VERY MUCH!!!@.!!
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4538D8BB.7050509@.realsqlguy.com...
> mecn wrote:
> Correct, you can't point/click to a network path, but you can TYPE the
> path into the filename field on that same window...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||mecn wrote:
> I am sorry, you are right!!!! I could type the network path into file name
> box and it works--THANK YOU VERY MUCH!!!@.!!
>
Great... Now that you've accomplished that, can you explain why this
was easier than just issuing the RESTORE DATABASE command in a query window?
Tracy McKibben
MCDBA
http://www.realsqlguy.comsql

Restore database from Yukon June CTP to September CTP

Hello:

I am trying to restore a database that was created with the June CTP version of Yukon to another box that has the September CTP installed. However, I am getting the following error:

-
"The database was backed up on a server running version 9.00.0852. That version is incompatible with this server, which is running version 9.00.1314. Either restore the database on a server that supports the backup or use a backup that is compatible with this server.

RESTORE DATABASE is terminating abnormally, (Microsoft SQL Server, Error: 3169)"
-

Shouldn't the September CTP be backward compatible with the June CTP? Would appreciate it if someone has any ideas on how to resolve this. I have verified the compatibility level to be 90 on the September CTP.

Thanks!

If you haven't uninstalled June yet, this might work. A kludge to be sure, and not for large databases.

Solution? Import the database to access. Save the create scripts to a file.

Then recreate the schema in Sept and use the Access Upsize Wizard to load the data.

Not ideal. However, it should work.

sql

Restore backup on different machine

We are moving backups from being written on a local box, to writing tham on a
NAS and making a daily copy to a report server. So, to start, I made a manual
copy of the backup files to the NAS and then wen't to restore tham.
What I get is an error message that includes the path name from the machine
where the backup was made as well as the path name for the log file.
Duh!
I can see that I need to add the 'WITH MOVE' parameters to the restore
command, but I can't get them to work. This is probably because I flat-out
don't understand what is happening. Once I say where the full backup is, why
does it care about the path is was backed up to? Why does it care about
restoring a log file I didn't ask for?
Once I change the backup path on the production machine to the NAS (so that
the paths are the same, will this issue just go away?> I can see that I need to add the 'WITH MOVE' parameters to the restore
> command, but I can't get them to work. This is probably because I flat-out
> don't understand what is happening. Once I say where the full backup is,
> why
> does it care about the path is was backed up to?
Because when it restores the database, it needs to create an MDF and LDF
file of the same size for the database to be restored correctly and usable.
> Why does it care about
> restoring a log file I didn't ask for?
When you restore a database, you get the data file(s) and the log file(s).
This is not negotiable.
> Once I change the backup path on the production machine to the NAS (so
> that
> the paths are the same, will this issue just go away?
That depends, if you mean that you intend to restore to the exact same
location as an existing data/log file location, then no, that won't work.

Restore backup on different machine

We are moving backups from being written on a local box, to writing tham on a
NAS and making a daily copy to a report server. So, to start, I made a manual
copy of the backup files to the NAS and then wen't to restore tham.
What I get is an error message that includes the path name from the machine
where the backup was made as well as the path name for the log file.
Duh!
I can see that I need to add the 'WITH MOVE' parameters to the restore
command, but I can't get them to work. This is probably because I flat-out
don't understand what is happening. Once I say where the full backup is, why
does it care about the path is was backed up to? Why does it care about
restoring a log file I didn't ask for?
Once I change the backup path on the production machine to the NAS (so that
the paths are the same, will this issue just go away?
> I can see that I need to add the 'WITH MOVE' parameters to the restore
> command, but I can't get them to work. This is probably because I flat-out
> don't understand what is happening. Once I say where the full backup is,
> why
> does it care about the path is was backed up to?
Because when it restores the database, it needs to create an MDF and LDF
file of the same size for the database to be restored correctly and usable.

> Why does it care about
> restoring a log file I didn't ask for?
When you restore a database, you get the data file(s) and the log file(s).
This is not negotiable.

> Once I change the backup path on the production machine to the NAS (so
> that
> the paths are the same, will this issue just go away?
That depends, if you mean that you intend to restore to the exact same
location as an existing data/log file location, then no, that won't work.

Restore backup on different machine

We are moving backups from being written on a local box, to writing tham on
a
NAS and making a daily copy to a report server. So, to start, I made a manua
l
copy of the backup files to the NAS and then wen't to restore tham.
What I get is an error message that includes the path name from the machine
where the backup was made as well as the path name for the log file.
Duh!
I can see that I need to add the 'WITH MOVE' parameters to the restore
command, but I can't get them to work. This is probably because I flat-out
don't understand what is happening. Once I say where the full backup is, why
does it care about the path is was backed up to? Why does it care about
restoring a log file I didn't ask for?
Once I change the backup path on the production machine to the NAS (so that
the paths are the same, will this issue just go away?> I can see that I need to add the 'WITH MOVE' parameters to the restore
> command, but I can't get them to work. This is probably because I flat-out
> don't understand what is happening. Once I say where the full backup is,
> why
> does it care about the path is was backed up to?
Because when it restores the database, it needs to create an MDF and LDF
file of the same size for the database to be restored correctly and usable.

> Why does it care about
> restoring a log file I didn't ask for?
When you restore a database, you get the data file(s) and the log file(s).
This is not negotiable.

> Once I change the backup path on the production machine to the NAS (so
> that
> the paths are the same, will this issue just go away?
That depends, if you mean that you intend to restore to the exact same
location as an existing data/log file location, then no, that won't work.

restore a replicated db to a sql server with no replication

Hi,
I want to take my replicated db SQL 7 and put a data only version of
it on to a dev box.
I remember doing this with no problems in the past, but I did it
yesterday and it took forever with lots of fiddling about. The
restore in EM never actually completed.
I am now trying to run my code on this db and I am getting the
following error:
e.g. in Query analyser I ran:
update users set usr_password = 'password'
error:
Server: Msg 18750, Level 16, State 4, Procedure
upd_DA46F6B9F9D348FE9419EB7A8FCCECFD, Line 51
INITCOLVS: The parameter 'nickname' is invalid.
Server: Msg 3621, Level 16, State 1, Procedure
upd_DA46F6B9F9D348FE9419EB7A8FCCECFD, Line 51
The statement has been terminated.
The statement has been terminated.
Is there a way I can back up the db from my production server and not
include any of the replication info so it can operate cleanly on my
dev server?
Thanks in advance.
Install replication, enable the database for replication. Restore the
database using the keep_replication switch. Then drop the publications.
Otherwise run this script.
http://groups.google.com/groups?selm...&output=gplain
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Duncan" <duncan.loxton@.gmail.com> wrote in message
news:7315f62a.0411221556.509f8fcb@.posting.google.c om...
> Hi,
> I want to take my replicated db SQL 7 and put a data only version of
> it on to a dev box.
> I remember doing this with no problems in the past, but I did it
> yesterday and it took forever with lots of fiddling about. The
> restore in EM never actually completed.
> I am now trying to run my code on this db and I am getting the
> following error:
> e.g. in Query analyser I ran:
> update users set usr_password = 'password'
> error:
> Server: Msg 18750, Level 16, State 4, Procedure
> upd_DA46F6B9F9D348FE9419EB7A8FCCECFD, Line 51
> INITCOLVS: The parameter 'nickname' is invalid.
> Server: Msg 3621, Level 16, State 1, Procedure
> upd_DA46F6B9F9D348FE9419EB7A8FCCECFD, Line 51
> The statement has been terminated.
> The statement has been terminated.
> Is there a way I can back up the db from my production server and not
> include any of the replication info so it can operate cleanly on my
> dev server?
> Thanks in advance.
|||SQL Server 7.0 (I am assuming you are restoring to a SQL Server 7.0 server)
does not have a KEEP_REPLICATION option for the restore command. You can
try running sp_removedbreplication in the databse. However, this may not
remove everything. The error is mostly caused by a trigger on the table you
are trying to update. If so you can drop the trigger in Enterprise Manager.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Correct - I am trying to restore to a SQL 7 server.
I ran the script and sp_removedbreplication. The script reported the
following error (amongst others:
dropping conflict_tables conflict_MPlus Live_Exchange
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near 'Live_Exchange'.
dropping rowguid constraints conflict_MPlus Live_Clients
Server: Msg 156, Level 15, State 1, Line 2
Incorrect syntax near the keyword 'DROP'.
dropping rowguid columns conflict_MPlus Live_ListingLibraryType
Alter Table conflict_MPlus Live_ListingLibraryType
drop column rowguid
Server: Msg 156, Level 15, State 1, Line 2
Incorrect syntax near the keyword 'drop'.
and the sp_removedbreplication completed without error.
Using my example from before I am now encountering the following error
when running update users set usr_password = 'password'
Server: Msg 208, Level 16, State 1, Procedure
upd_DA46F6B9F9D348FE9419EB7A8FCCECFD, Line 16
Invalid object name 'dbo.sysmergearticles'.
So it appears the objects are not there, although it thinks that they
are.
There must be a better way to get a backup of a replicated db and
restore it with no replication.....
Any other feedback I might try? Thanks for your help.
|||Right - I have dropped the triggers on a couple of tables and things are
looking up!
I dont want to have to go through 500 tables and drop 3 triggers on each one
manually. How can I get rid of them programatically?
|||Thanks for the clarification Rand! I missed the SQL 7.0 part.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:8QUe5SX0EHA.3436@.cpmsftngxa10.phx.gbl...
> SQL Server 7.0 (I am assuming you are restoring to a SQL Server 7.0
> server)
> does not have a KEEP_REPLICATION option for the restore command. You can
> try running sp_removedbreplication in the databse. However, this may not
> remove everything. The error is mostly caused by a trigger on the table
> you
> are trying to update. If so you can drop the trigger in Enterprise
> Manager.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||try this:
http://groups.google.com/groups?selm...&output=gplain
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Duncan" <duncan.loxton@.gmail.com> wrote in message
news:30htnvF30vspdU1@.uni-berlin.de...
> Right - I have dropped the triggers on a couple of tables and things are
> looking up!
> I dont want to have to go through 500 tables and drop 3 triggers on each
> one manually. How can I get rid of them programatically?
>
|||try this script. Be careful about running it as it will destroy any active
subscriptions or publications you may have in this database.
http://groups.google.com/groups?selm...&output=gplain
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Duncan" <duncan.loxton@.gmail.com> wrote in message
news:30htnvF30vspdU1@.uni-berlin.de...
> Right - I have dropped the triggers on a couple of tables and things are
> looking up!
> I dont want to have to go through 500 tables and drop 3 triggers on each
> one manually. How can I get rid of them programatically?
>
|||Hilary,
Thanks for this scipt - this is all a bit out of my league now. However I
think that the replication has been removed, its just the triggers on the
individual table I need to root out.
I tried it but here is a portion of the output:
Server: Msg 208, Level 16, State 1, Line 3
Invalid object name 'syspublications'.
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'sysmergepublications'.
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'sysmergesubscriptions'.
Server: Msg 208, Level 16, State 1, Line 1
~~~~~~~~~~~~
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near 'Live_MyProspectiveTenants'.
dropping conflict_tables conflict_MPlus Live_object
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near 'Live_object'.
dropping conflict_tables conflict_MPlus Live_ListingCommissionSplit
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near 'Live_ListingCommissionSplit'.
dropping conflict_tables conflict_MPlus Live_Age
Server: Msg 170, Level 15, State 1, Line 1
~~~~~~~~~
drop column rowguid
Server: Msg 156, Level 15, State 1, Line 2
Incorrect syntax near the keyword 'drop'.
dropping rowguid columns conflict_MPlus Live_ClientOpenDay
Alter Table conflict_MPlus Live_ClientOpenDay
drop column rowguid
Server: Msg 156, Level 15, State 1, Line 2
Incorrect syntax near the keyword 'drop'.
dropping rowguid columns conflict_MPlus Live_ClientPartner
Alter Table conflict_MPlus Live_ClientPartner
drop column rowguid