Hello all,
I was wondering if there is a way to move ODBC connections between SQL servers? We are replacing our current server with newer hardware, and I have pretty much everything figured out except this.
Thanks for any help and/or hints.You can either use Client Network Utility on the client to create an alias, or modify client's registry to forcew an alias, or create an alias in AD for the new server to be known under the old name, or rename the new server to the old name. Take a pick ;)|||I am afraid you lost me.
I am building out an entirely new server to move the databases to, but I also need to move over the ODBC connections listed in the control panel applet.|||Small bump...
Does anyone else have any ideas?|||This is one of those kind of things that cartographers of olde used to mark "Here be dragons"... They didn't know exactly what was there, but they were suspicious that it wasn't good!
The problem is that a machine's ODBC connections depend on drivers, which can depend on... You get the idea. The ODBC connections are pretty much the top layer in a house of cards.
The short answer is that there isn't a really safe and reliable way to move the ODBC connections. It can be done, but unless you know EXACTLY how both of the machines were built, it is probably just a receipe for a disaster. Your best bet is to recreate the ODBC connections manually on the new machine.
-PatP|||This is one of those kind of things that cartographers of olde used to mark "Here be dragons"... They didn't know exactly what was there, but they were suspicious that it wasn't good!
The problem is that a machine's ODBC connections depend on drivers, which can depend on... You get the idea. The ODBC connections are pretty much the top layer in a house of cards.
The short answer is that there isn't a really safe and reliable way to move the ODBC connections. It can be done, but unless you know EXACTLY how both of the machines were built, it is probably just a receipe for a disaster. Your best bet is to recreate the ODBC connections manually on the new machine.
-PatP
Bah! Humbug! Humbug I say! :D
Well, I was hoping to be lazy, but I guess it is not in the cards for me. :(
Thanks for the input folks.|||My initial understanding of your question was, that while moving the server to new HW, you wanted clients NOT to see the difference while retaining their ODBC connections. Now I see that you want to move ODBC Data Sources from your old server to the new one...Doh...You need to go to REGEDIT (be very carefull...oh well, you probably already know) and locate HKEY_LOCAL_MACHINE\SOFTWARE\ODBC. At this point you can either save the entire hive (highlight ODBC and use "Export Registry File..." from Registry menu) or each individual data source (they'll appear in the tree on the left pane as folders) using the same technique. Once the file(-s) is/are exported, you can copy it/them to the new machine and double-click on it/them.
But, as Pat said, watch out for dragons. I'd backup the registry on the target before doing all this, and make sure I can restore successfully. Better yet, test it on a throw-away PC (server or workstation, doesn't matter) and see if you get what you wanted. I've done it several times, but it's your turn now, not mine ;)|||My initial understanding of your question was, that while moving the server to new HW, you wanted clients NOT to see the difference while retaining their ODBC connections. Now I see that you want to move ODBC Data Sources from your old server to the new one...Doh...You need to go to REGEDIT (be very carefull...oh well, you probably already know) and locate HKEY_LOCAL_MACHINE\SOFTWARE\ODBC. At this point you can either save the entire hive (highlight ODBC and use "Export Registry File..." from Registry menu) or each individual data source (they'll appear in the tree on the left pane as folders) using the same technique. Once the file(-s) is/are exported, you can copy it/them to the new machine and double-click on it/them.
But, as Pat said, watch out for dragons. I'd backup the registry on the target before doing all this, and make sure I can restore successfully. Better yet, test it on a throw-away PC (server or workstation, doesn't matter) and see if you get what you wanted. I've done it several times, but it's your turn now, not mine ;)
Aye, I don't mind using my local workstation for the import test to avoid complications in the future.
I did, in fact, see those listings in the registry, my main worry about that was if it did, or did not, transfer security with the connections.|||It transfers EVERYTHING that contains in the registry hive that corresponds to each data source.|||The major problem with this is that some registry settings aren't recognized by earlier driver versions. This copys one part of the registry from one machine to another, without regard to whether the two machines are at the same release/patch levels.
It certainly can be done, but I'd only do this with two servers that I'd built up from bare hardware (so that I knew exactly what was on the machines in the way of ODBC drivers and other files that they rely upon), or if I could run the new one in parallel with the old one for at least 90 days to be sure I hadn't missed some small but crucial detail. I don't think that I'd be willing to risk doing this on a production machine, considering how little time it takes to build the ODBC connections and then I could safely forget about them!
-PatP|||Well, I will say that the OS, SQL and all the patch levels will be the same - corporate spec and all that... The main difference will be the hardware. They are both Compaq(HP) boxes, just one happens to be a nice 8 way machine with 10 gigs of RAM.
:drool:
Saturday, February 25, 2012
Moving Objects!
What is the best way to move objects from Dev to Prod. I usally use All Tasks/Generate SQL Script and then run this in query analyzer in Prod. However, If I am moving a couple of tables and they have foreign key constraints, that relationship is lost.
Even when moving one of those tables. How to solve this?
Thanks
probably the best way to do this is via Scripts, although you technicaly
could use DTS or something.
I'm not sure what you mean by losing relationships ....?
You have to script the Indexes, Constraints, Etc.
Explain a little better what you mean.
GAJ
|||I just noticed the scripting options which default to NOT script primary keys, foreign keys. So I'll make sure to check those in the future.
Thanks
"Jaxon" wrote:
> probably the best way to do this is via Scripts, although you technicaly
> could use DTS or something.
> I'm not sure what you mean by losing relationships ....?
> You have to script the Indexes, Constraints, Etc.
> Explain a little better what you mean.
>
> GAJ
>
>
Even when moving one of those tables. How to solve this?
Thanks
probably the best way to do this is via Scripts, although you technicaly
could use DTS or something.
I'm not sure what you mean by losing relationships ....?
You have to script the Indexes, Constraints, Etc.
Explain a little better what you mean.
GAJ
|||I just noticed the scripting options which default to NOT script primary keys, foreign keys. So I'll make sure to check those in the future.
Thanks
"Jaxon" wrote:
> probably the best way to do this is via Scripts, although you technicaly
> could use DTS or something.
> I'm not sure what you mean by losing relationships ....?
> You have to script the Indexes, Constraints, Etc.
> Explain a little better what you mean.
>
> GAJ
>
>
Moving Objects!
What is the best way to move objects from Dev to Prod. I usally use All Tas
ks/Generate SQL Script and then run this in query analyzer in Prod. However
, If I am moving a couple of tables and they have foreign key constraints, t
hat relationship is lost.
Even when moving one of those tables. How to solve this?
Thanksprobably the best way to do this is via Scripts, although you technicaly
could use DTS or something.
I'm not sure what you mean by losing relationships ....?
You have to script the Indexes, Constraints, Etc.
Explain a little better what you mean.
GAJ|||I just noticed the scripting options which default to NOT script primary key
s, foreign keys. So I'll make sure to check those in the future.
Thanks
"Jaxon" wrote:
> probably the best way to do this is via Scripts, although you technicaly
> could use DTS or something.
> I'm not sure what you mean by losing relationships ....?
> You have to script the Indexes, Constraints, Etc.
> Explain a little better what you mean.
>
> GAJ
>
>
ks/Generate SQL Script and then run this in query analyzer in Prod. However
, If I am moving a couple of tables and they have foreign key constraints, t
hat relationship is lost.
Even when moving one of those tables. How to solve this?
Thanksprobably the best way to do this is via Scripts, although you technicaly
could use DTS or something.
I'm not sure what you mean by losing relationships ....?
You have to script the Indexes, Constraints, Etc.
Explain a little better what you mean.
GAJ|||I just noticed the scripting options which default to NOT script primary key
s, foreign keys. So I'll make sure to check those in the future.
Thanks
"Jaxon" wrote:
> probably the best way to do this is via Scripts, although you technicaly
> could use DTS or something.
> I'm not sure what you mean by losing relationships ....?
> You have to script the Indexes, Constraints, Etc.
> Explain a little better what you mean.
>
> GAJ
>
>
Moving objects from Primary File Group using T-SQL
Hello All;
I am trying to spread database objects by moving certain tables and indexes
to file groups that I have created just for this purpose. Right now,
everything is in the PRIMARY file group, and I have created a secondary Data
filegroup and a third file group for indexes.
I see in BOL the syntax for moving an index (actaully dropping and
re-creating) but don't see how to move just a single table. I can't seem to
get the syntax correct.
ALTER TABLE <My Table>
DROP CONSTRAINT <My Constraint>
WITH (ONLINE = ON, MOVE TO <My File Group> )
That works, but only if I have something to drop. I don't want to drop the
PK Constraints, I want to move them to one file group and the table itself t
o
another.
Any suggestions would be appreciated.
--
Todd C(Re)Create a clustered index on the table of concern and specify the
filegroup then.
TheSQLGuru
President
Indicium Resources, Inc.
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
> Hello All;
> I am trying to spread database objects by moving certain tables and
> indexes
> to file groups that I have created just for this purpose. Right now,
> everything is in the PRIMARY file group, and I have created a secondary
> Data
> filegroup and a third file group for indexes.
> I see in BOL the syntax for moving an index (actaully dropping and
> re-creating) but don't see how to move just a single table. I can't seem
> to
> get the syntax correct.
> ALTER TABLE <My Table>
> DROP CONSTRAINT <My Constraint>
> WITH (ONLINE = ON, MOVE TO <My File Group> )
> That works, but only if I have something to drop. I don't want to drop the
> PK Constraints, I want to move them to one file group and the table itself
> to
> another.
> Any suggestions would be appreciated.
> --
> Todd C|||Todd, note that this moves the data, the clustered index and all
non-clustered indexes to the new filegroup. By definition, you cannot put
the clustered index on one filegroup, the data on another, and non-clustered
indexes on yet others...
Aaron Bertrand
SQL Server MVP
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
> (Re)Create a clustered index on the table of concern and specify the
> filegroup then.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
>|||Hello Aaron;
So a table's data and indexes must all be in the same filegroup?
Leaving Table Partitioning out of the discussuion, what is the best way to
increase performance on tables that are heavily used and heavily indexed?
Our databases have been relatively small up til now and I foresee that in
the near future I am going to need to look at tuning and performance issues.
What is the best approach?
Thanks in advance.
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Todd, note that this moves the data, the clustered index and all
> non-clustered indexes to the new filegroup. By definition, you cannot put
> the clustered index on one filegroup, the data on another, and non-cluster
ed
> indexes on yet others...
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
>
>|||> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
Are the performance problems on inserting, querying, something else? The
"best" approach is pretty subjective, and depends on a lot of factors,
including budget.
Aaron Bertrand
SQL Server MVP|||Inserting/querrying/updating...not sure where the load is coming from at thi
s
point. Currently running a tuning profile to analyze later.I just know that
this one database is the heaviest used (but not the biggest) on this one
server, and the one data drive is experiencing some heavy load.
Two new drives have been added (RAID, dedicated channels, etc) for me to
start spreading out the load. OK, So it looks like I'll be studying the blac
k
art of database performance tuning for a while...
Any good books or resources out there?
--
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Are the performance problems on inserting, querying, something else? The
> "best" approach is pretty subjective, and depends on a lot of factors,
> including budget.
> --
> Aaron Bertrand
> SQL Server MVP
>
>|||> So a table's data and indexes must all be in the same filegroup?
No. I don't think that was what Aaron's meant.
A table and it's *clustered index* need to be on the same file group because
the clustered index
*is* the table. But you can have non-clustered indexes on other filegroup(s)
.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:A83833FE-CCDE-47C4-AC4F-D0404CD12B8F@.microsoft.com...[vbcol=seagreen]
> Hello Aaron;
> So a table's data and indexes must all be in the same filegroup?
> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
> Our databases have been relatively small up til now and I foresee that in
> the near future I am going to need to look at tuning and performance issue
s.
> What is the best approach?
> Thanks in advance.
> --
> Todd C
> "Aaron Bertrand [SQL Server MVP]" wrote:
>|||Hello Tibor:
OK, I think I got it now. That makes more sense
Thanks
Todd C
I am trying to spread database objects by moving certain tables and indexes
to file groups that I have created just for this purpose. Right now,
everything is in the PRIMARY file group, and I have created a secondary Data
filegroup and a third file group for indexes.
I see in BOL the syntax for moving an index (actaully dropping and
re-creating) but don't see how to move just a single table. I can't seem to
get the syntax correct.
ALTER TABLE <My Table>
DROP CONSTRAINT <My Constraint>
WITH (ONLINE = ON, MOVE TO <My File Group> )
That works, but only if I have something to drop. I don't want to drop the
PK Constraints, I want to move them to one file group and the table itself t
o
another.
Any suggestions would be appreciated.
--
Todd C(Re)Create a clustered index on the table of concern and specify the
filegroup then.
TheSQLGuru
President
Indicium Resources, Inc.
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
> Hello All;
> I am trying to spread database objects by moving certain tables and
> indexes
> to file groups that I have created just for this purpose. Right now,
> everything is in the PRIMARY file group, and I have created a secondary
> Data
> filegroup and a third file group for indexes.
> I see in BOL the syntax for moving an index (actaully dropping and
> re-creating) but don't see how to move just a single table. I can't seem
> to
> get the syntax correct.
> ALTER TABLE <My Table>
> DROP CONSTRAINT <My Constraint>
> WITH (ONLINE = ON, MOVE TO <My File Group> )
> That works, but only if I have something to drop. I don't want to drop the
> PK Constraints, I want to move them to one file group and the table itself
> to
> another.
> Any suggestions would be appreciated.
> --
> Todd C|||Todd, note that this moves the data, the clustered index and all
non-clustered indexes to the new filegroup. By definition, you cannot put
the clustered index on one filegroup, the data on another, and non-clustered
indexes on yet others...
Aaron Bertrand
SQL Server MVP
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
> (Re)Create a clustered index on the table of concern and specify the
> filegroup then.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
>|||Hello Aaron;
So a table's data and indexes must all be in the same filegroup?
Leaving Table Partitioning out of the discussuion, what is the best way to
increase performance on tables that are heavily used and heavily indexed?
Our databases have been relatively small up til now and I foresee that in
the near future I am going to need to look at tuning and performance issues.
What is the best approach?
Thanks in advance.
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Todd, note that this moves the data, the clustered index and all
> non-clustered indexes to the new filegroup. By definition, you cannot put
> the clustered index on one filegroup, the data on another, and non-cluster
ed
> indexes on yet others...
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
>
>|||> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
Are the performance problems on inserting, querying, something else? The
"best" approach is pretty subjective, and depends on a lot of factors,
including budget.
Aaron Bertrand
SQL Server MVP|||Inserting/querrying/updating...not sure where the load is coming from at thi
s
point. Currently running a tuning profile to analyze later.I just know that
this one database is the heaviest used (but not the biggest) on this one
server, and the one data drive is experiencing some heavy load.
Two new drives have been added (RAID, dedicated channels, etc) for me to
start spreading out the load. OK, So it looks like I'll be studying the blac
k
art of database performance tuning for a while...
Any good books or resources out there?
--
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Are the performance problems on inserting, querying, something else? The
> "best" approach is pretty subjective, and depends on a lot of factors,
> including budget.
> --
> Aaron Bertrand
> SQL Server MVP
>
>|||> So a table's data and indexes must all be in the same filegroup?
No. I don't think that was what Aaron's meant.
A table and it's *clustered index* need to be on the same file group because
the clustered index
*is* the table. But you can have non-clustered indexes on other filegroup(s)
.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:A83833FE-CCDE-47C4-AC4F-D0404CD12B8F@.microsoft.com...[vbcol=seagreen]
> Hello Aaron;
> So a table's data and indexes must all be in the same filegroup?
> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
> Our databases have been relatively small up til now and I foresee that in
> the near future I am going to need to look at tuning and performance issue
s.
> What is the best approach?
> Thanks in advance.
> --
> Todd C
> "Aaron Bertrand [SQL Server MVP]" wrote:
>|||Hello Tibor:
OK, I think I got it now. That makes more sense
Thanks
Todd C
Moving objects from Primary File Group using T-SQL
Hello All;
I am trying to spread database objects by moving certain tables and indexes
to file groups that I have created just for this purpose. Right now,
everything is in the PRIMARY file group, and I have created a secondary Data
filegroup and a third file group for indexes.
I see in BOL the syntax for moving an index (actaully dropping and
re-creating) but don't see how to move just a single table. I can't seem to
get the syntax correct.
ALTER TABLE <My Table>
DROP CONSTRAINT <My Constraint>
WITH (ONLINE = ON, MOVE TO <My File Group>)
That works, but only if I have something to drop. I don't want to drop the
PK Constraints, I want to move them to one file group and the table itself to
another.
Any suggestions would be appreciated.
Todd C
(Re)Create a clustered index on the table of concern and specify the
filegroup then.
TheSQLGuru
President
Indicium Resources, Inc.
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
> Hello All;
> I am trying to spread database objects by moving certain tables and
> indexes
> to file groups that I have created just for this purpose. Right now,
> everything is in the PRIMARY file group, and I have created a secondary
> Data
> filegroup and a third file group for indexes.
> I see in BOL the syntax for moving an index (actaully dropping and
> re-creating) but don't see how to move just a single table. I can't seem
> to
> get the syntax correct.
> ALTER TABLE <My Table>
> DROP CONSTRAINT <My Constraint>
> WITH (ONLINE = ON, MOVE TO <My File Group>)
> That works, but only if I have something to drop. I don't want to drop the
> PK Constraints, I want to move them to one file group and the table itself
> to
> another.
> Any suggestions would be appreciated.
> --
> Todd C
|||Todd, note that this moves the data, the clustered index and all
non-clustered indexes to the new filegroup. By definition, you cannot put
the clustered index on one filegroup, the data on another, and non-clustered
indexes on yet others...
Aaron Bertrand
SQL Server MVP
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
> (Re)Create a clustered index on the table of concern and specify the
> filegroup then.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
>
|||Hello Aaron;
So a table's data and indexes must all be in the same filegroup?
Leaving Table Partitioning out of the discussuion, what is the best way to
increase performance on tables that are heavily used and heavily indexed?
Our databases have been relatively small up til now and I foresee that in
the near future I am going to need to look at tuning and performance issues.
What is the best approach?
Thanks in advance.
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Todd, note that this moves the data, the clustered index and all
> non-clustered indexes to the new filegroup. By definition, you cannot put
> the clustered index on one filegroup, the data on another, and non-clustered
> indexes on yet others...
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
>
>
|||> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
Are the performance problems on inserting, querying, something else? The
"best" approach is pretty subjective, and depends on a lot of factors,
including budget.
Aaron Bertrand
SQL Server MVP
|||Inserting/querrying/updating...not sure where the load is coming from at this
point. Currently running a tuning profile to analyze later.I just know that
this one database is the heaviest used (but not the biggest) on this one
server, and the one data drive is experiencing some heavy load.
Two new drives have been added (RAID, dedicated channels, etc) for me to
start spreading out the load. OK, So it looks like I'll be studying the black
art of database performance tuning for a while...
Any good books or resources out there?
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Are the performance problems on inserting, querying, something else? The
> "best" approach is pretty subjective, and depends on a lot of factors,
> including budget.
> --
> Aaron Bertrand
> SQL Server MVP
>
>
|||> So a table's data and indexes must all be in the same filegroup?
No. I don't think that was what Aaron's meant.
A table and it's *clustered index* need to be on the same file group because the clustered index
*is* the table. But you can have non-clustered indexes on other filegroup(s).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:A83833FE-CCDE-47C4-AC4F-D0404CD12B8F@.microsoft.com...[vbcol=seagreen]
> Hello Aaron;
> So a table's data and indexes must all be in the same filegroup?
> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
> Our databases have been relatively small up til now and I foresee that in
> the near future I am going to need to look at tuning and performance issues.
> What is the best approach?
> Thanks in advance.
> --
> Todd C
> "Aaron Bertrand [SQL Server MVP]" wrote:
|||Hello Tibor:
OK, I think I got it now. That makes more sense
Thanks
Todd C
I am trying to spread database objects by moving certain tables and indexes
to file groups that I have created just for this purpose. Right now,
everything is in the PRIMARY file group, and I have created a secondary Data
filegroup and a third file group for indexes.
I see in BOL the syntax for moving an index (actaully dropping and
re-creating) but don't see how to move just a single table. I can't seem to
get the syntax correct.
ALTER TABLE <My Table>
DROP CONSTRAINT <My Constraint>
WITH (ONLINE = ON, MOVE TO <My File Group>)
That works, but only if I have something to drop. I don't want to drop the
PK Constraints, I want to move them to one file group and the table itself to
another.
Any suggestions would be appreciated.
Todd C
(Re)Create a clustered index on the table of concern and specify the
filegroup then.
TheSQLGuru
President
Indicium Resources, Inc.
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
> Hello All;
> I am trying to spread database objects by moving certain tables and
> indexes
> to file groups that I have created just for this purpose. Right now,
> everything is in the PRIMARY file group, and I have created a secondary
> Data
> filegroup and a third file group for indexes.
> I see in BOL the syntax for moving an index (actaully dropping and
> re-creating) but don't see how to move just a single table. I can't seem
> to
> get the syntax correct.
> ALTER TABLE <My Table>
> DROP CONSTRAINT <My Constraint>
> WITH (ONLINE = ON, MOVE TO <My File Group>)
> That works, but only if I have something to drop. I don't want to drop the
> PK Constraints, I want to move them to one file group and the table itself
> to
> another.
> Any suggestions would be appreciated.
> --
> Todd C
|||Todd, note that this moves the data, the clustered index and all
non-clustered indexes to the new filegroup. By definition, you cannot put
the clustered index on one filegroup, the data on another, and non-clustered
indexes on yet others...
Aaron Bertrand
SQL Server MVP
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
> (Re)Create a clustered index on the table of concern and specify the
> filegroup then.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
>
|||Hello Aaron;
So a table's data and indexes must all be in the same filegroup?
Leaving Table Partitioning out of the discussuion, what is the best way to
increase performance on tables that are heavily used and heavily indexed?
Our databases have been relatively small up til now and I foresee that in
the near future I am going to need to look at tuning and performance issues.
What is the best approach?
Thanks in advance.
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Todd, note that this moves the data, the clustered index and all
> non-clustered indexes to the new filegroup. By definition, you cannot put
> the clustered index on one filegroup, the data on another, and non-clustered
> indexes on yet others...
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
>
>
|||> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
Are the performance problems on inserting, querying, something else? The
"best" approach is pretty subjective, and depends on a lot of factors,
including budget.
Aaron Bertrand
SQL Server MVP
|||Inserting/querrying/updating...not sure where the load is coming from at this
point. Currently running a tuning profile to analyze later.I just know that
this one database is the heaviest used (but not the biggest) on this one
server, and the one data drive is experiencing some heavy load.
Two new drives have been added (RAID, dedicated channels, etc) for me to
start spreading out the load. OK, So it looks like I'll be studying the black
art of database performance tuning for a while...
Any good books or resources out there?
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Are the performance problems on inserting, querying, something else? The
> "best" approach is pretty subjective, and depends on a lot of factors,
> including budget.
> --
> Aaron Bertrand
> SQL Server MVP
>
>
|||> So a table's data and indexes must all be in the same filegroup?
No. I don't think that was what Aaron's meant.
A table and it's *clustered index* need to be on the same file group because the clustered index
*is* the table. But you can have non-clustered indexes on other filegroup(s).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:A83833FE-CCDE-47C4-AC4F-D0404CD12B8F@.microsoft.com...[vbcol=seagreen]
> Hello Aaron;
> So a table's data and indexes must all be in the same filegroup?
> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
> Our databases have been relatively small up til now and I foresee that in
> the near future I am going to need to look at tuning and performance issues.
> What is the best approach?
> Thanks in advance.
> --
> Todd C
> "Aaron Bertrand [SQL Server MVP]" wrote:
|||Hello Tibor:
OK, I think I got it now. That makes more sense
Thanks
Todd C
Moving objects from Primary File Group using T-SQL
Hello All;
I am trying to spread database objects by moving certain tables and indexes
to file groups that I have created just for this purpose. Right now,
everything is in the PRIMARY file group, and I have created a secondary Data
filegroup and a third file group for indexes.
I see in BOL the syntax for moving an index (actaully dropping and
re-creating) but don't see how to move just a single table. I can't seem to
get the syntax correct.
ALTER TABLE <My Table>
DROP CONSTRAINT <My Constraint>
WITH (ONLINE = ON, MOVE TO <My File Group>)
That works, but only if I have something to drop. I don't want to drop the
PK Constraints, I want to move them to one file group and the table itself to
another.
Any suggestions would be appreciated.
--
Todd C(Re)Create a clustered index on the table of concern and specify the
filegroup then.
--
TheSQLGuru
President
Indicium Resources, Inc.
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
> Hello All;
> I am trying to spread database objects by moving certain tables and
> indexes
> to file groups that I have created just for this purpose. Right now,
> everything is in the PRIMARY file group, and I have created a secondary
> Data
> filegroup and a third file group for indexes.
> I see in BOL the syntax for moving an index (actaully dropping and
> re-creating) but don't see how to move just a single table. I can't seem
> to
> get the syntax correct.
> ALTER TABLE <My Table>
> DROP CONSTRAINT <My Constraint>
> WITH (ONLINE = ON, MOVE TO <My File Group>)
> That works, but only if I have something to drop. I don't want to drop the
> PK Constraints, I want to move them to one file group and the table itself
> to
> another.
> Any suggestions would be appreciated.
> --
> Todd C|||Todd, note that this moves the data, the clustered index and all
non-clustered indexes to the new filegroup. By definition, you cannot put
the clustered index on one filegroup, the data on another, and non-clustered
indexes on yet others...
--
Aaron Bertrand
SQL Server MVP
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
> (Re)Create a clustered index on the table of concern and specify the
> filegroup then.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
>> Hello All;
>> I am trying to spread database objects by moving certain tables and
>> indexes
>> to file groups that I have created just for this purpose. Right now,
>> everything is in the PRIMARY file group, and I have created a secondary
>> Data
>> filegroup and a third file group for indexes.
>> I see in BOL the syntax for moving an index (actaully dropping and
>> re-creating) but don't see how to move just a single table. I can't seem
>> to
>> get the syntax correct.
>> ALTER TABLE <My Table>
>> DROP CONSTRAINT <My Constraint>
>> WITH (ONLINE = ON, MOVE TO <My File Group>)
>> That works, but only if I have something to drop. I don't want to drop
>> the
>> PK Constraints, I want to move them to one file group and the table
>> itself to
>> another.
>> Any suggestions would be appreciated.
>> --
>> Todd C
>|||Hello Aaron;
So a table's data and indexes must all be in the same filegroup?
Leaving Table Partitioning out of the discussuion, what is the best way to
increase performance on tables that are heavily used and heavily indexed?
Our databases have been relatively small up til now and I foresee that in
the near future I am going to need to look at tuning and performance issues.
What is the best approach?
Thanks in advance.
--
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Todd, note that this moves the data, the clustered index and all
> non-clustered indexes to the new filegroup. By definition, you cannot put
> the clustered index on one filegroup, the data on another, and non-clustered
> indexes on yet others...
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
> > (Re)Create a clustered index on the table of concern and specify the
> > filegroup then.
> >
> > --
> > TheSQLGuru
> > President
> > Indicium Resources, Inc.
> >
> > "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> > news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
> >> Hello All;
> >> I am trying to spread database objects by moving certain tables and
> >> indexes
> >> to file groups that I have created just for this purpose. Right now,
> >> everything is in the PRIMARY file group, and I have created a secondary
> >> Data
> >> filegroup and a third file group for indexes.
> >>
> >> I see in BOL the syntax for moving an index (actaully dropping and
> >> re-creating) but don't see how to move just a single table. I can't seem
> >> to
> >> get the syntax correct.
> >>
> >> ALTER TABLE <My Table>
> >> DROP CONSTRAINT <My Constraint>
> >> WITH (ONLINE = ON, MOVE TO <My File Group>)
> >>
> >> That works, but only if I have something to drop. I don't want to drop
> >> the
> >> PK Constraints, I want to move them to one file group and the table
> >> itself to
> >> another.
> >>
> >> Any suggestions would be appreciated.
> >> --
> >> Todd C
> >
> >
>
>|||> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
Are the performance problems on inserting, querying, something else? The
"best" approach is pretty subjective, and depends on a lot of factors,
including budget.
--
Aaron Bertrand
SQL Server MVP|||Inserting/querrying/updating...not sure where the load is coming from at this
point. Currently running a tuning profile to analyze later.I just know that
this one database is the heaviest used (but not the biggest) on this one
server, and the one data drive is experiencing some heavy load.
Two new drives have been added (RAID, dedicated channels, etc) for me to
start spreading out the load. OK, So it looks like I'll be studying the black
art of database performance tuning for a while...
Any good books or resources out there?
--
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> > Leaving Table Partitioning out of the discussuion, what is the best way to
> > increase performance on tables that are heavily used and heavily indexed?
> Are the performance problems on inserting, querying, something else? The
> "best" approach is pretty subjective, and depends on a lot of factors,
> including budget.
> --
> Aaron Bertrand
> SQL Server MVP
>
>|||> So a table's data and indexes must all be in the same filegroup?
No. I don't think that was what Aaron's meant.
A table and it's *clustered index* need to be on the same file group because the clustered index
*is* the table. But you can have non-clustered indexes on other filegroup(s).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:A83833FE-CCDE-47C4-AC4F-D0404CD12B8F@.microsoft.com...
> Hello Aaron;
> So a table's data and indexes must all be in the same filegroup?
> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
> Our databases have been relatively small up til now and I foresee that in
> the near future I am going to need to look at tuning and performance issues.
> What is the best approach?
> Thanks in advance.
> --
> Todd C
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> Todd, note that this moves the data, the clustered index and all
>> non-clustered indexes to the new filegroup. By definition, you cannot put
>> the clustered index on one filegroup, the data on another, and non-clustered
>> indexes on yet others...
>> --
>> Aaron Bertrand
>> SQL Server MVP
>>
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
>> > (Re)Create a clustered index on the table of concern and specify the
>> > filegroup then.
>> >
>> > --
>> > TheSQLGuru
>> > President
>> > Indicium Resources, Inc.
>> >
>> > "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
>> > news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
>> >> Hello All;
>> >> I am trying to spread database objects by moving certain tables and
>> >> indexes
>> >> to file groups that I have created just for this purpose. Right now,
>> >> everything is in the PRIMARY file group, and I have created a secondary
>> >> Data
>> >> filegroup and a third file group for indexes.
>> >>
>> >> I see in BOL the syntax for moving an index (actaully dropping and
>> >> re-creating) but don't see how to move just a single table. I can't seem
>> >> to
>> >> get the syntax correct.
>> >>
>> >> ALTER TABLE <My Table>
>> >> DROP CONSTRAINT <My Constraint>
>> >> WITH (ONLINE = ON, MOVE TO <My File Group>)
>> >>
>> >> That works, but only if I have something to drop. I don't want to drop
>> >> the
>> >> PK Constraints, I want to move them to one file group and the table
>> >> itself to
>> >> another.
>> >>
>> >> Any suggestions would be appreciated.
>> >> --
>> >> Todd C
>> >
>> >
>>|||Hello Tibor:
OK, I think I got it now. That makes more sense
Thanks
Todd C
I am trying to spread database objects by moving certain tables and indexes
to file groups that I have created just for this purpose. Right now,
everything is in the PRIMARY file group, and I have created a secondary Data
filegroup and a third file group for indexes.
I see in BOL the syntax for moving an index (actaully dropping and
re-creating) but don't see how to move just a single table. I can't seem to
get the syntax correct.
ALTER TABLE <My Table>
DROP CONSTRAINT <My Constraint>
WITH (ONLINE = ON, MOVE TO <My File Group>)
That works, but only if I have something to drop. I don't want to drop the
PK Constraints, I want to move them to one file group and the table itself to
another.
Any suggestions would be appreciated.
--
Todd C(Re)Create a clustered index on the table of concern and specify the
filegroup then.
--
TheSQLGuru
President
Indicium Resources, Inc.
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
> Hello All;
> I am trying to spread database objects by moving certain tables and
> indexes
> to file groups that I have created just for this purpose. Right now,
> everything is in the PRIMARY file group, and I have created a secondary
> Data
> filegroup and a third file group for indexes.
> I see in BOL the syntax for moving an index (actaully dropping and
> re-creating) but don't see how to move just a single table. I can't seem
> to
> get the syntax correct.
> ALTER TABLE <My Table>
> DROP CONSTRAINT <My Constraint>
> WITH (ONLINE = ON, MOVE TO <My File Group>)
> That works, but only if I have something to drop. I don't want to drop the
> PK Constraints, I want to move them to one file group and the table itself
> to
> another.
> Any suggestions would be appreciated.
> --
> Todd C|||Todd, note that this moves the data, the clustered index and all
non-clustered indexes to the new filegroup. By definition, you cannot put
the clustered index on one filegroup, the data on another, and non-clustered
indexes on yet others...
--
Aaron Bertrand
SQL Server MVP
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
> (Re)Create a clustered index on the table of concern and specify the
> filegroup then.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
>> Hello All;
>> I am trying to spread database objects by moving certain tables and
>> indexes
>> to file groups that I have created just for this purpose. Right now,
>> everything is in the PRIMARY file group, and I have created a secondary
>> Data
>> filegroup and a third file group for indexes.
>> I see in BOL the syntax for moving an index (actaully dropping and
>> re-creating) but don't see how to move just a single table. I can't seem
>> to
>> get the syntax correct.
>> ALTER TABLE <My Table>
>> DROP CONSTRAINT <My Constraint>
>> WITH (ONLINE = ON, MOVE TO <My File Group>)
>> That works, but only if I have something to drop. I don't want to drop
>> the
>> PK Constraints, I want to move them to one file group and the table
>> itself to
>> another.
>> Any suggestions would be appreciated.
>> --
>> Todd C
>|||Hello Aaron;
So a table's data and indexes must all be in the same filegroup?
Leaving Table Partitioning out of the discussuion, what is the best way to
increase performance on tables that are heavily used and heavily indexed?
Our databases have been relatively small up til now and I foresee that in
the near future I am going to need to look at tuning and performance issues.
What is the best approach?
Thanks in advance.
--
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> Todd, note that this moves the data, the clustered index and all
> non-clustered indexes to the new filegroup. By definition, you cannot put
> the clustered index on one filegroup, the data on another, and non-clustered
> indexes on yet others...
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
> > (Re)Create a clustered index on the table of concern and specify the
> > filegroup then.
> >
> > --
> > TheSQLGuru
> > President
> > Indicium Resources, Inc.
> >
> > "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> > news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
> >> Hello All;
> >> I am trying to spread database objects by moving certain tables and
> >> indexes
> >> to file groups that I have created just for this purpose. Right now,
> >> everything is in the PRIMARY file group, and I have created a secondary
> >> Data
> >> filegroup and a third file group for indexes.
> >>
> >> I see in BOL the syntax for moving an index (actaully dropping and
> >> re-creating) but don't see how to move just a single table. I can't seem
> >> to
> >> get the syntax correct.
> >>
> >> ALTER TABLE <My Table>
> >> DROP CONSTRAINT <My Constraint>
> >> WITH (ONLINE = ON, MOVE TO <My File Group>)
> >>
> >> That works, but only if I have something to drop. I don't want to drop
> >> the
> >> PK Constraints, I want to move them to one file group and the table
> >> itself to
> >> another.
> >>
> >> Any suggestions would be appreciated.
> >> --
> >> Todd C
> >
> >
>
>|||> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
Are the performance problems on inserting, querying, something else? The
"best" approach is pretty subjective, and depends on a lot of factors,
including budget.
--
Aaron Bertrand
SQL Server MVP|||Inserting/querrying/updating...not sure where the load is coming from at this
point. Currently running a tuning profile to analyze later.I just know that
this one database is the heaviest used (but not the biggest) on this one
server, and the one data drive is experiencing some heavy load.
Two new drives have been added (RAID, dedicated channels, etc) for me to
start spreading out the load. OK, So it looks like I'll be studying the black
art of database performance tuning for a while...
Any good books or resources out there?
--
Todd C
"Aaron Bertrand [SQL Server MVP]" wrote:
> > Leaving Table Partitioning out of the discussuion, what is the best way to
> > increase performance on tables that are heavily used and heavily indexed?
> Are the performance problems on inserting, querying, something else? The
> "best" approach is pretty subjective, and depends on a lot of factors,
> including budget.
> --
> Aaron Bertrand
> SQL Server MVP
>
>|||> So a table's data and indexes must all be in the same filegroup?
No. I don't think that was what Aaron's meant.
A table and it's *clustered index* need to be on the same file group because the clustered index
*is* the table. But you can have non-clustered indexes on other filegroup(s).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:A83833FE-CCDE-47C4-AC4F-D0404CD12B8F@.microsoft.com...
> Hello Aaron;
> So a table's data and indexes must all be in the same filegroup?
> Leaving Table Partitioning out of the discussuion, what is the best way to
> increase performance on tables that are heavily used and heavily indexed?
> Our databases have been relatively small up til now and I foresee that in
> the near future I am going to need to look at tuning and performance issues.
> What is the best approach?
> Thanks in advance.
> --
> Todd C
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> Todd, note that this moves the data, the clustered index and all
>> non-clustered indexes to the new filegroup. By definition, you cannot put
>> the clustered index on one filegroup, the data on another, and non-clustered
>> indexes on yet others...
>> --
>> Aaron Bertrand
>> SQL Server MVP
>>
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:%2343LVMe3HHA.1212@.TK2MSFTNGP05.phx.gbl...
>> > (Re)Create a clustered index on the table of concern and specify the
>> > filegroup then.
>> >
>> > --
>> > TheSQLGuru
>> > President
>> > Indicium Resources, Inc.
>> >
>> > "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
>> > news:EBE06366-4135-4789-94AC-AF5F0886901E@.microsoft.com...
>> >> Hello All;
>> >> I am trying to spread database objects by moving certain tables and
>> >> indexes
>> >> to file groups that I have created just for this purpose. Right now,
>> >> everything is in the PRIMARY file group, and I have created a secondary
>> >> Data
>> >> filegroup and a third file group for indexes.
>> >>
>> >> I see in BOL the syntax for moving an index (actaully dropping and
>> >> re-creating) but don't see how to move just a single table. I can't seem
>> >> to
>> >> get the syntax correct.
>> >>
>> >> ALTER TABLE <My Table>
>> >> DROP CONSTRAINT <My Constraint>
>> >> WITH (ONLINE = ON, MOVE TO <My File Group>)
>> >>
>> >> That works, but only if I have something to drop. I don't want to drop
>> >> the
>> >> PK Constraints, I want to move them to one file group and the table
>> >> itself to
>> >> another.
>> >>
>> >> Any suggestions would be appreciated.
>> >> --
>> >> Todd C
>> >
>> >
>>|||Hello Tibor:
OK, I think I got it now. That makes more sense
Thanks
Todd C
Moving objects from one schema to another
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
MarkHello Mark,
MR> In SQL Server 2005 is there an easy way to move tables, SPs, views
MR> etc out of the default dbo schema and into a new schema?
MR> I can't find anything on Google or in BOL about this...
Have a look-see at ALTER SCHEMA.
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Thanks,
Kent Tegels
http://staff.develop.com/ktegels/|||Check out:
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Mark Rae" <mark@.markNOSPAMrae.com> wrote in message
news:eS8ZS8v5GHA.696@.TK2MSFTNGP06.phx.gbl...
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
Mark|||"Kent Tegels" <ktegels@.develop.com> wrote in message
news:b87ad7460258c8b4ee4d678a30@.news.microsoft.com...
> Have a look-see at ALTER SCHEMA.
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OJWsyEw5GHA.1012@.TK2MSFTNGP05.phx.gbl...
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
MarkHello Mark,
MR> In SQL Server 2005 is there an easy way to move tables, SPs, views
MR> etc out of the default dbo schema and into a new schema?
MR> I can't find anything on Google or in BOL about this...
Have a look-see at ALTER SCHEMA.
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Thanks,
Kent Tegels
http://staff.develop.com/ktegels/|||Check out:
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Mark Rae" <mark@.markNOSPAMrae.com> wrote in message
news:eS8ZS8v5GHA.696@.TK2MSFTNGP06.phx.gbl...
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
Mark|||"Kent Tegels" <ktegels@.develop.com> wrote in message
news:b87ad7460258c8b4ee4d678a30@.news.microsoft.com...
> Have a look-see at ALTER SCHEMA.
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OJWsyEw5GHA.1012@.TK2MSFTNGP05.phx.gbl...
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.
Moving objects from one schema to another
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
Mark
Hello Mark,
MR> In SQL Server 2005 is there an easy way to move tables, SPs, views
MR> etc out of the default dbo schema and into a new schema?
MR> I can't find anything on Google or in BOL about this...
Have a look-see at ALTER SCHEMA.
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Thanks,
Kent Tegels
http://staff.develop.com/ktegels/
|||Check out:
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Mark Rae" <mark@.markNOSPAMrae.com> wrote in message
news:eS8ZS8v5GHA.696@.TK2MSFTNGP06.phx.gbl...
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
Mark
|||"Kent Tegels" <ktegels@.develop.com> wrote in message
news:b87ad7460258c8b4ee4d678a30@.news.microsoft.com ...
> Have a look-see at ALTER SCHEMA.
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.
|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OJWsyEw5GHA.1012@.TK2MSFTNGP05.phx.gbl...
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
Mark
Hello Mark,
MR> In SQL Server 2005 is there an easy way to move tables, SPs, views
MR> etc out of the default dbo schema and into a new schema?
MR> I can't find anything on Google or in BOL about this...
Have a look-see at ALTER SCHEMA.
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Thanks,
Kent Tegels
http://staff.develop.com/ktegels/
|||Check out:
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Mark Rae" <mark@.markNOSPAMrae.com> wrote in message
news:eS8ZS8v5GHA.696@.TK2MSFTNGP06.phx.gbl...
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
Mark
|||"Kent Tegels" <ktegels@.develop.com> wrote in message
news:b87ad7460258c8b4ee4d678a30@.news.microsoft.com ...
> Have a look-see at ALTER SCHEMA.
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.
|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OJWsyEw5GHA.1012@.TK2MSFTNGP05.phx.gbl...
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.
Moving objects from one schema to another
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
MarkCheck out:
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Mark Rae" <mark@.markNOSPAMrae.com> wrote in message
news:eS8ZS8v5GHA.696@.TK2MSFTNGP06.phx.gbl...
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
Mark|||Hello Mark,
MR> In SQL Server 2005 is there an easy way to move tables, SPs, views
MR> etc out of the default dbo schema and into a new schema?
MR> I can't find anything on Google or in BOL about this...
Have a look-see at ALTER SCHEMA.
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Thanks,
Kent Tegels
http://staff.develop.com/ktegels/|||"Kent Tegels" <ktegels@.develop.com> wrote in message
news:b87ad7460258c8b4ee4d678a30@.news.microsoft.com...
> Have a look-see at ALTER SCHEMA.
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OJWsyEw5GHA.1012@.TK2MSFTNGP05.phx.gbl...
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
MarkCheck out:
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Mark Rae" <mark@.markNOSPAMrae.com> wrote in message
news:eS8ZS8v5GHA.696@.TK2MSFTNGP06.phx.gbl...
Hi,
In SQL Server 2005 is there an easy way to move tables, SPs, views etc out
of the default dbo schema and into a new schema?
I can't find anything on Google or in BOL about this...
Thanks,
Mark|||Hello Mark,
MR> In SQL Server 2005 is there an easy way to move tables, SPs, views
MR> etc out of the default dbo schema and into a new schema?
MR> I can't find anything on Google or in BOL about this...
Have a look-see at ALTER SCHEMA.
http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Thanks,
Kent Tegels
http://staff.develop.com/ktegels/|||"Kent Tegels" <ktegels@.develop.com> wrote in message
news:b87ad7460258c8b4ee4d678a30@.news.microsoft.com...
> Have a look-see at ALTER SCHEMA.
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OJWsyEw5GHA.1012@.TK2MSFTNGP05.phx.gbl...
> http://msdn2.microsoft.com/en-us/library/ms173423.aspx
Excellent! Thanks.
Moving objects from 1 SQL Server to another
Greetings one and all,
I hope some here can help me.
We are currently running SQL Server 2000 on 2 different servers. The first server was an upgrade from SQL 7 so the data, etc are in a directory named MSSQL7. The second sever is newer and larger (Disk and Memeory) and was a straight install, so the data is in MSSQL.
I am trying to move everything from the old server to the new one. The databases are easy as well as the users. I can not get my DTS packages, DB Maintenance, and SQL Server Agent jobs from the old one to the new one.
Any ideas?? We are running out of room on the old server and need to get this moved over asap.
I look forward to hearing from someone.
RayFor the SQL Server Agent jobs (and DB Maintenance as well, as they are all created as Jobs I believe) you can right click in the Enterprise Managers Management/Jobs Tree and select All Tasks/Generate SQL Script
Hope this helps.
Quote:
Originally Posted by rdfanta
Greetings one and all,
I hope some here can help me.
We are currently running SQL Server 2000 on 2 different servers. The first server was an upgrade from SQL 7 so the data, etc are in a directory named MSSQL7. The second sever is newer and larger (Disk and Memeory) and was a straight install, so the data is in MSSQL.
I am trying to move everything from the old server to the new one. The databases are easy as well as the users. I can not get my DTS packages, DB Maintenance, and SQL Server Agent jobs from the old one to the new one.
Any ideas?? We are running out of room on the old server and need to get this moved over asap.
I look forward to hearing from someone.
Ray
Thanks for the info. The only Item that gives me that option is the SQL Server Agent Jobs. But I get an error when trying to run the script because the DB Maintenance Job does not exist.
For the DTS Packages, I am trying to save them as Structured Storage files or Visual Basic files. But I have not figured out how to read them back in
Ray
Moving ntext to nvarchar(max)
I just move our SQL server to version 2005. In new version ntext field is deprecated and documentation says that ntext(max) should be used.
If I have table Table1 and ntext column Column1. When I execute following SQL statements:
alter table Table1 alter column
Column1 nvarchar(max)
go
1.) Are out of row data automatically move to in row?
2.) Or should I also execute something like this ?
update Table1 set Column1 = Column1+'' where Column1 is not null
3.) Is there way to check if data is stored out or in row?
Best regards
edvin
Hi,
see this article for more information:
http://msdn2.microsoft.com/en-US/library/ms189087.aspx
Find out the option on your table using sp_tableoption
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||>> 1.) Are out of row data automatically move to in row?
No. ALTER TABLE operation is typically a metadata only operation. There are exceptions however where we have to rewrite every single row. But in this case, there is no reason to touch every single row and text page.
>> 2.) Or should I also execute something like this ?
>> update Table1 set Column1 = Column1+'' where Column1 is not null
You could, but I would recommend against doing this due to the logging requirements but it depends on the number of rows being updated and the percentage of data in the table that can be moved in-row. Future inserts will automatically be in-row depending on their length. Updates to values that are already stored out-of-row will be moved in-row depending on their length. You could recreate the table using SELECT INTO operation which will be more efficient than UPDATE but requires more logic. And you may also have to defrag the table if you update due to migration of the rows or fragmentation of pages.
>> 3.) Is there way to check if data is stored out or in row?
There is no easy way to check this. But you can use the query below to see the allocations happening in the table based on the data insertions. Below is some sample code that will demonstrate the whole process.
use tempdb
go
create table dbo.lobtest ( i int not null identity, t ntext not null );
insert into dbo.lobtest values(replicate(cast(N'x' as nvarchar(max)), 1024*100));
insert into dbo.lobtest values(replicate(cast(N'x' as nvarchar(max)), 1024));
-- look at allocation entries (generic query to alloc units for a table):
select au.*
, coalesce(p1.object_id, p2.object_id) as object_id
, coalesce(p1.index_id, p2.index_id) as index_id
from sys.allocation_units as au
outer apply (
select top(1) p.object_id, p.index_id
from sys.partitions as p
where p.hobt_id = au.container_id and au.type in (1, 3)
) as p1
outer apply (
select top(1) p.object_id, p.index_id
from sys.partitions as p
where p.partition_id = au.container_id and au.type = 2
) as p2
where coalesce(p1.object_id, p2.object_id) = object_id('dbo.lobtest');
-- convert ntext column:
alter table dbo.lobtest alter column t nvarchar(max) not null;
-- look at allocation entries again:
select au.*
, coalesce(p1.object_id, p2.object_id) as object_id
, coalesce(p1.index_id, p2.index_id) as index_id
from sys.allocation_units as au
outer apply (
select top(1) p.object_id, p.index_id
from sys.partitions as p
where p.hobt_id = au.container_id and au.type in (1, 3)
) as p1
outer apply (
select top(1) p.object_id, p.index_id
from sys.partitions as p
where p.partition_id = au.container_id and au.type = 2
) as p2
where coalesce(p1.object_id, p2.object_id) = object_id('dbo.lobtest');
-- add more rows that should be inline
insert into dbo.lobtest values(replicate(cast(N'x' as nvarchar(max)), 1024));
insert into dbo.lobtest values(replicate(cast(N'x' as nvarchar(max)), 1024));
insert into dbo.lobtest values(replicate(cast(N'x' as nvarchar(max)), 1024));
-- check allocation entries again (only IN_ROW_DATA pages increased):
select au.*
, coalesce(p1.object_id, p2.object_id) as object_id
, coalesce(p1.index_id, p2.index_id) as index_id
from sys.allocation_units as au
outer apply (
select top(1) p.object_id, p.index_id
from sys.partitions as p
where p.hobt_id = au.container_id and au.type in (1, 3)
) as p1
outer apply (
select top(1) p.object_id, p.index_id
from sys.partitions as p
where p.partition_id = au.container_id and au.type = 2
) as p2
where coalesce(p1.object_id, p2.object_id) = object_id('dbo.lobtest');
drop table dbo.lobtest;
go
Hi,
thanks for your replies. But are you really sure that simple updating all rows will not move date from out row to in row. Because in SQL documentation (http://msdn2.microsoft.com/en-US/library/ms189087.aspx) states that:
When the large value types out of row option value is changed, existing varchar(max), nvarchar(max), varbinary(max), and xml values are not immediately converted. The storage of the strings is changed as they are subsequently updated. Any new values inserted into a table are stored according to the table option in effect.
-
From this I understand that updating row data will also change the storage. Recreating tables demands also recreating constraints, indexes..etc..
Best regards
edvin
moving northwind
hey all,
what's the best way to move my northwind that's in msde and move it to sql
express 2005?
thanks,
rodcharYou can easily back it up & restore it since it is a really small database.
Alternatively you can download it from MS site or you can run the script
that generate the database ( instnwnd.sql is available in your Microsoft SQL
Server\MSSQL\Install\ folder )
Anith|||Thank you.
"Anith Sen" wrote:
> You can easily back it up & restore it since it is a really small database
.
> Alternatively you can download it from MS site or you can run the script
> that generate the database ( instnwnd.sql is available in your Microsoft S
QL
> Server\MSSQL\Install\ folder )
> --
> Anith
>
>
what's the best way to move my northwind that's in msde and move it to sql
express 2005?
thanks,
rodcharYou can easily back it up & restore it since it is a really small database.
Alternatively you can download it from MS site or you can run the script
that generate the database ( instnwnd.sql is available in your Microsoft SQL
Server\MSSQL\Install\ folder )
Anith|||Thank you.
"Anith Sen" wrote:
> You can easily back it up & restore it since it is a really small database
.
> Alternatively you can download it from MS site or you can run the script
> that generate the database ( instnwnd.sql is available in your Microsoft S
QL
> Server\MSSQL\Install\ folder )
> --
> Anith
>
>
Moving Non-Clustered to Clustered
Hi,
I have been looking for the last few hours for how to move a non-clustered
environment to a clustered environment without having to change the
connection strings of any of our applications. I'm not finding it anywhere.
It's been a while since I did this, and I thought we could have a virtual
name for both instances that are the same as the old computer names (I.E.
Instance 1 is called "Bitter" and instance 2 is called "silver" from the
apps, even if the actual names are ClustName\Instance1 &
Clustname\Instance2).
Is this possible, and can someone point me to where I can find how to do
this, if it is?
Thanks,
Ryan S
SQL DBA
1Jn5:12
You do it by using DNS SRV records. SRV records allows for an arbitary
service to use DNS to map a name to an IP Address and Port number.
When you cut over, create a "Bitter" and "Silver" record that points to the
new clustered instance names.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
news:EA78A067-5C48-4C17-9819-064C8399BF0F@.microsoft.com...
> Hi,
> I have been looking for the last few hours for how to move a non-clustered
> environment to a clustered environment without having to change the
> connection strings of any of our applications. I'm not finding it
> anywhere.
> It's been a while since I did this, and I thought we could have a virtual
> name for both instances that are the same as the old computer names (I.E.
> Instance 1 is called "Bitter" and instance 2 is called "silver" from the
> apps, even if the actual names are ClustName\Instance1 &
> Clustname\Instance2).
> Is this possible, and can someone point me to where I can find how to do
> this, if it is?
> Thanks,
> --
> Ryan S
> SQL DBA
> 1Jn5:12
|||Thanks for the help, but I am still having trouble finding exactly how to do
it.
Is it just as simple as redirecting the TCP/IP traffic to the correct
ip/port, like a dyn dns service or is there more to it?
Sorry if we are being obtuse, but neither I, nor my Net Admin, can seem to
find anything in BOL, or at MS or online about setting up a SQL Instance with
DNS SRV records.
Ryan S
SQL DBA
1Jn5:12
"Geoff N. Hiten" wrote:
> You do it by using DNS SRV records. SRV records allows for an arbitary
> service to use DNS to map a name to an IP Address and Port number.
> When you cut over, create a "Bitter" and "Silver" record that points to the
> new clustered instance names.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
> news:EA78A067-5C48-4C17-9819-064C8399BF0F@.microsoft.com...
>
|||That is about all there is to it. And there is no KB article or section in
BOL about abstracting the service name of a SQL server using DNS SRV
records. Maybe I should write something.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
news:6FC957E4-8170-470A-AD57-9EC781EBFF6B@.microsoft.com...[vbcol=seagreen]
> Thanks for the help, but I am still having trouble finding exactly how to
> do
> it.
> Is it just as simple as redirecting the TCP/IP traffic to the correct
> ip/port, like a dyn dns service or is there more to it?
> Sorry if we are being obtuse, but neither I, nor my Net Admin, can seem to
> find anything in BOL, or at MS or online about setting up a SQL Instance
> with
> DNS SRV records.
> --
> Ryan S
> SQL DBA
> 1Jn5:12
>
> "Geoff N. Hiten" wrote:
|||Thanks,
If you do write it, reply to this, and I'll be notified.
Thanks again,
Ryan S
Sr SQL DBA
1Jn5:12
"Geoff N. Hiten" wrote:
[vbcol=seagreen]
> That is about all there is to it. And there is no KB article or section in
> BOL about abstracting the service name of a SQL server using DNS SRV
> records. Maybe I should write something.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
> news:6FC957E4-8170-470A-AD57-9EC781EBFF6B@.microsoft.com...
I have been looking for the last few hours for how to move a non-clustered
environment to a clustered environment without having to change the
connection strings of any of our applications. I'm not finding it anywhere.
It's been a while since I did this, and I thought we could have a virtual
name for both instances that are the same as the old computer names (I.E.
Instance 1 is called "Bitter" and instance 2 is called "silver" from the
apps, even if the actual names are ClustName\Instance1 &
Clustname\Instance2).
Is this possible, and can someone point me to where I can find how to do
this, if it is?
Thanks,
Ryan S
SQL DBA
1Jn5:12
You do it by using DNS SRV records. SRV records allows for an arbitary
service to use DNS to map a name to an IP Address and Port number.
When you cut over, create a "Bitter" and "Silver" record that points to the
new clustered instance names.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
news:EA78A067-5C48-4C17-9819-064C8399BF0F@.microsoft.com...
> Hi,
> I have been looking for the last few hours for how to move a non-clustered
> environment to a clustered environment without having to change the
> connection strings of any of our applications. I'm not finding it
> anywhere.
> It's been a while since I did this, and I thought we could have a virtual
> name for both instances that are the same as the old computer names (I.E.
> Instance 1 is called "Bitter" and instance 2 is called "silver" from the
> apps, even if the actual names are ClustName\Instance1 &
> Clustname\Instance2).
> Is this possible, and can someone point me to where I can find how to do
> this, if it is?
> Thanks,
> --
> Ryan S
> SQL DBA
> 1Jn5:12
|||Thanks for the help, but I am still having trouble finding exactly how to do
it.
Is it just as simple as redirecting the TCP/IP traffic to the correct
ip/port, like a dyn dns service or is there more to it?
Sorry if we are being obtuse, but neither I, nor my Net Admin, can seem to
find anything in BOL, or at MS or online about setting up a SQL Instance with
DNS SRV records.
Ryan S
SQL DBA
1Jn5:12
"Geoff N. Hiten" wrote:
> You do it by using DNS SRV records. SRV records allows for an arbitary
> service to use DNS to map a name to an IP Address and Port number.
> When you cut over, create a "Bitter" and "Silver" record that points to the
> new clustered instance names.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
> news:EA78A067-5C48-4C17-9819-064C8399BF0F@.microsoft.com...
>
|||That is about all there is to it. And there is no KB article or section in
BOL about abstracting the service name of a SQL server using DNS SRV
records. Maybe I should write something.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
news:6FC957E4-8170-470A-AD57-9EC781EBFF6B@.microsoft.com...[vbcol=seagreen]
> Thanks for the help, but I am still having trouble finding exactly how to
> do
> it.
> Is it just as simple as redirecting the TCP/IP traffic to the correct
> ip/port, like a dyn dns service or is there more to it?
> Sorry if we are being obtuse, but neither I, nor my Net Admin, can seem to
> find anything in BOL, or at MS or online about setting up a SQL Instance
> with
> DNS SRV records.
> --
> Ryan S
> SQL DBA
> 1Jn5:12
>
> "Geoff N. Hiten" wrote:
|||Thanks,
If you do write it, reply to this, and I'll be notified.
Thanks again,
Ryan S
Sr SQL DBA
1Jn5:12
"Geoff N. Hiten" wrote:
[vbcol=seagreen]
> That is about all there is to it. And there is no KB article or section in
> BOL about abstracting the service name of a SQL server using DNS SRV
> records. Maybe I should write something.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
> news:6FC957E4-8170-470A-AD57-9EC781EBFF6B@.microsoft.com...
Moving Next in your dataset from Custom Code
Can you pass a value into the custom code window, do some logic, and if the
criteria aren't met move to the next dataset record? I don't know how to do
this or aren't sure if you can.DO that with a filter...
Create a public function in the code section that returns an integer which
indicates whether the row should be included or not... Pass whatever
parameterts into the function, and the function returns the approriate
value.
In the filter section for your report add the filter condition
code.myfilterfunctionname(whatever parameters) = 0
When the funtion returns 0 for a row , it will be included otherwise
excluded from the report
--
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
"dillig" <dillig@.discussions.microsoft.com> wrote in message
news:A96EB455-A6C8-4DD5-A984-7E9C9F353CAE@.microsoft.com...
> Can you pass a value into the custom code window, do some logic, and if
the
> criteria aren't met move to the next dataset record? I don't know how to
do
> this or aren't sure if you can.
criteria aren't met move to the next dataset record? I don't know how to do
this or aren't sure if you can.DO that with a filter...
Create a public function in the code section that returns an integer which
indicates whether the row should be included or not... Pass whatever
parameterts into the function, and the function returns the approriate
value.
In the filter section for your report add the filter condition
code.myfilterfunctionname(whatever parameters) = 0
When the funtion returns 0 for a row , it will be included otherwise
excluded from the report
--
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
"dillig" <dillig@.discussions.microsoft.com> wrote in message
news:A96EB455-A6C8-4DD5-A984-7E9C9F353CAE@.microsoft.com...
> Can you pass a value into the custom code window, do some logic, and if
the
> criteria aren't met move to the next dataset record? I don't know how to
do
> this or aren't sure if you can.
Moving new data into dimension tables automatically using Integration Services
I have an Integration Services package that loads new data into tables that are dimension tables wi my cube. The same situation exists for my fact table. If I perform an "Analysis Services Processing Task" for the dimensions ,cube and measures, will that move the new data into my cube or do I need to perform the "Dimension Processing Destination" data flow task prior to this? Is the initial processing task good enough?
thx,
-Marilyn
You only need the Analysis Services processing Task!
-jamie
P.S. The correct nomenclature is the "Dimension Processing Destination" data flow component, not the "Dimension Processing Destination" data flow task. Tasks are in the control-flow.
|||thanks jamie for the good info...Moving my SQL Server to another computer
I will moving my SQL Server to another server. The plan is to stop SQL Server copy database file to a temp netwokr location, Switch off this server. Configure the new server with the same name and IP, install SQL to the same paths and service pack to the same level (SQL 2000 sp3). Then start and stop the SQL server. Once stop I will then copy the old database file over the new ones.
I know in general this works as I have doen this many times before expect this time round there is a replicaiton database which is new, I am expecting this will work the same but has any one else tried this before?
Unfortunately, you have to disable the publication before you can detach and move the database.
BTW, I recommend you to detach the database before you move the database file to another server, this ensure you can attach it to the new server even though it is missing the transaction log file.
Moving my SQL 7.0 databases to a new server to replace the old server
My existing SQL server is an old box that can no longer cope with the load. I need to replace it with a brand new box.
I am looking for a comprehensive set of steps that I could follow to ensure that the transition to the new server goes well.
I'm looking to transfer all my user databases but I'm not so sure whether I have to backup and restore my system databases to the new server as well.
I want to name the new server the same as the old server since I will be taking the old server out of production but I'm not sure whether I should rename the server AFTER I move over all the database and how that would affect SQL. Or should I first rename the old server, remove it out of the domain, then name my new server with the same name as my old server, and then proceed with the SQL installation and the moving of the databases.
Also, I do have a maintenance plan, DTS packages and some jobs set up on my old server that I would also like to move to the new server.
Is there a web page that explains all the steps in granular detail ?
SQL Server 2005 Books Online actually has pretty good info on this. I just did a search on "upgrade 7.0" and it provided a good roadmap.
Paul
Moving my SQL 7.0 databases to a new server to replace the old server
My existing SQL server is an old box that can no longer cope with the load. I need to replace it with a brand new box.
I am looking for a comprehensive set of steps that I could follow to ensure that the transition to the new server goes well.
I'm looking to transfer all my user databases but I'm not so sure whether I have to backup and restore my system databases to the new server as well.
I want to name the new server the same as the old server since I will be taking the old server out of production but I'm not sure whether I should rename the server AFTER I move over all the database and how that would affect SQL. Or should I first rename the old server, remove it out of the domain, then name my new server with the same name as my old server, and then proceed with the SQL installation and the moving of the databases.
Also, I do have a maintenance plan, DTS packages and some jobs set up on my old server that I would also like to move to the new server.
Is there a web page that explains all the steps in granular detail ?
SQL Server 2005 Books Online actually has pretty good info on this. I just did a search on "upgrade 7.0" and it provided a good roadmap.
Paul
Moving Multiple MDB files into SQL Server
Hello,
I have multiiple MDB files to move into SQL Server 2000. What is the best
way to import these files? I want to keep checking
a certain network folder to see if a new MDB exists. If so, I'll move it
into the SQL Server,
then move the MDB file to a subfolder, then I'll check to see if any other
MDB files exist on the network folder.
Thanks
Don
Hi,
You can import the MS Access (MDB) tables to SQL server using DTS.
Thanks
Hari
MCDBA
"Don" <dons100@.ameritech.net> wrote in message
news:91eCc.27585$eH1.12952254@.newssvr28.news.prodi gy.com...
> Hello,
> I have multiiple MDB files to move into SQL Server 2000. What is the best
> way to import these files? I want to keep checking
> a certain network folder to see if a new MDB exists. If so, I'll move it
> into the SQL Server,
> then move the MDB file to a subfolder, then I'll check to see if any other
> MDB files exist on the network folder.
> Thanks
> Don
>
I have multiiple MDB files to move into SQL Server 2000. What is the best
way to import these files? I want to keep checking
a certain network folder to see if a new MDB exists. If so, I'll move it
into the SQL Server,
then move the MDB file to a subfolder, then I'll check to see if any other
MDB files exist on the network folder.
Thanks
Don
Hi,
You can import the MS Access (MDB) tables to SQL server using DTS.
Thanks
Hari
MCDBA
"Don" <dons100@.ameritech.net> wrote in message
news:91eCc.27585$eH1.12952254@.newssvr28.news.prodi gy.com...
> Hello,
> I have multiiple MDB files to move into SQL Server 2000. What is the best
> way to import these files? I want to keep checking
> a certain network folder to see if a new MDB exists. If so, I'll move it
> into the SQL Server,
> then move the MDB file to a subfolder, then I'll check to see if any other
> MDB files exist on the network folder.
> Thanks
> Don
>
Moving Multiple MDB files into SQL Server
Hello,
I have multiiple MDB files to move into SQL Server 2000. What is the best
way to import these files? I want to keep checking
a certain network folder to see if a new MDB exists. If so, I'll move it
into the SQL Server,
then move the MDB file to a subfolder, then I'll check to see if any other
MDB files exist on the network folder.
Thanks
DonHi,
You can import the MS Access (MDB) tables to SQL server using DTS.
--
Thanks
Hari
MCDBA
"Don" <dons100@.ameritech.net> wrote in message
news:91eCc.27585$eH1.12952254@.newssvr28.news.prodigy.com...
> Hello,
> I have multiiple MDB files to move into SQL Server 2000. What is the best
> way to import these files? I want to keep checking
> a certain network folder to see if a new MDB exists. If so, I'll move it
> into the SQL Server,
> then move the MDB file to a subfolder, then I'll check to see if any other
> MDB files exist on the network folder.
> Thanks
> Don
>
I have multiiple MDB files to move into SQL Server 2000. What is the best
way to import these files? I want to keep checking
a certain network folder to see if a new MDB exists. If so, I'll move it
into the SQL Server,
then move the MDB file to a subfolder, then I'll check to see if any other
MDB files exist on the network folder.
Thanks
DonHi,
You can import the MS Access (MDB) tables to SQL server using DTS.
--
Thanks
Hari
MCDBA
"Don" <dons100@.ameritech.net> wrote in message
news:91eCc.27585$eH1.12952254@.newssvr28.news.prodigy.com...
> Hello,
> I have multiiple MDB files to move into SQL Server 2000. What is the best
> way to import these files? I want to keep checking
> a certain network folder to see if a new MDB exists. If so, I'll move it
> into the SQL Server,
> then move the MDB file to a subfolder, then I'll check to see if any other
> MDB files exist on the network folder.
> Thanks
> Don
>
Moving Multiple MDB files into SQL Server
Hello,
I have multiiple MDB files to move into SQL Server 2000. What is the best
way to import these files? I want to keep checking
a certain network folder to see if a new MDB exists. If so, I'll move it
into the SQL Server,
then move the MDB file to a subfolder, then I'll check to see if any other
MDB files exist on the network folder.
Thanks
DonHi,
You can import the MS Access (MDB) tables to SQL server using DTS.
Thanks
Hari
MCDBA
"Don" <dons100@.ameritech.net> wrote in message
news:91eCc.27585$eH1.12952254@.newssvr28.news.prodigy.com...
> Hello,
> I have multiiple MDB files to move into SQL Server 2000. What is the best
> way to import these files? I want to keep checking
> a certain network folder to see if a new MDB exists. If so, I'll move it
> into the SQL Server,
> then move the MDB file to a subfolder, then I'll check to see if any other
> MDB files exist on the network folder.
> Thanks
> Don
>
I have multiiple MDB files to move into SQL Server 2000. What is the best
way to import these files? I want to keep checking
a certain network folder to see if a new MDB exists. If so, I'll move it
into the SQL Server,
then move the MDB file to a subfolder, then I'll check to see if any other
MDB files exist on the network folder.
Thanks
DonHi,
You can import the MS Access (MDB) tables to SQL server using DTS.
Thanks
Hari
MCDBA
"Don" <dons100@.ameritech.net> wrote in message
news:91eCc.27585$eH1.12952254@.newssvr28.news.prodigy.com...
> Hello,
> I have multiiple MDB files to move into SQL Server 2000. What is the best
> way to import these files? I want to keep checking
> a certain network folder to see if a new MDB exists. If so, I'll move it
> into the SQL Server,
> then move the MDB file to a subfolder, then I'll check to see if any other
> MDB files exist on the network folder.
> Thanks
> Don
>
Moving MSSQL 7.0 Replicated database to MSSQL 2000
Hi,
I have a SQL Server 7.0 database which is configured for merge replication.
It has one publication and the publisher and distributor all reside on the
one server.
I now need to move the database to a new server with MSSQL 2000.
I would like to move the DB, replication and all if that's possible.
I have considered the copy database wizard but, as far as I know, it cannot
deal with replicated databases. I also tried restoring the database but get a
invalid column name'excluded_cols' error message which, I believe, is down to
replication being enabled on the original database.
As the merge replication is relatively uncomplicated I could perhaps create
the publication afresh on the new server. However how do I get the database
on to the MSSQL 2000 server in the first place?
I have also considered installing MSSQL 7.0 on the new server and then
restoring the database and upgrading it. Then decommissioning the old server.
Would replication be enabled on the new server?
Or are there any simpler means of achieving the same ends?
Any advice or shared experience appreciated.
DOM
Hi
Why don't you remove replication, restore the database and then re-create
the replication?
John
"Dom" wrote:
> Hi,
> I have a SQL Server 7.0 database which is configured for merge replication.
> It has one publication and the publisher and distributor all reside on the
> one server.
> I now need to move the database to a new server with MSSQL 2000.
> I would like to move the DB, replication and all if that's possible.
> I have considered the copy database wizard but, as far as I know, it cannot
> deal with replicated databases. I also tried restoring the database but get a
> invalid column name'excluded_cols' error message which, I believe, is down to
> replication being enabled on the original database.
> As the merge replication is relatively uncomplicated I could perhaps create
> the publication afresh on the new server. However how do I get the database
> on to the MSSQL 2000 server in the first place?
> I have also considered installing MSSQL 7.0 on the new server and then
> restoring the database and upgrading it. Then decommissioning the old server.
> Would replication be enabled on the new server?
> Or are there any simpler means of achieving the same ends?
> Any advice or shared experience appreciated.
> DOM
>
|||Hi John,
I would like to leave the original MSSQL 7.0 server fully operational as a
backup in case of problems with the new MSSQL 2000 box.
Therefore I want to leave replication intact on the original server .
I have no problem re-creating replication on the new box (although I'd
prefer not to), as I said it's a relatively simple replication scenario.
My problem is how to copy or restore a replicated MSSQL 7 database onto a
MSSQL 2000 box without any problems and leave the original databse intact on
the original server.
Any ideas?
DOM.
"John Bell" wrote:
> Hi
> Why don't you remove replication, restore the database and then re-create
> the replication?
> John
>
|||Hi
I would install SQL 2000 as a second instance on the second server. Restore
the database on the SQL 7 instance. Remove replication from the database.
Backup the database and restore it on SQL 2000.
Once tested you can use the same method for the upgrade, but on the primary
server you can remove SQL 7 and do a fresh SQL 2000 install. Once that is
working you can upgrade the secondary server.
You can do risk assessment on what/if scenarios, and you may want to take
server images in case you need to recover quickly at any point. Your
secondary server can be a standby alternative SQL 7 installation and SQL 2000
installation (you just need the disc space to hold it all!).
John
"Dom" wrote:
[vbcol=seagreen]
> Hi John,
> I would like to leave the original MSSQL 7.0 server fully operational as a
> backup in case of problems with the new MSSQL 2000 box.
> Therefore I want to leave replication intact on the original server .
> I have no problem re-creating replication on the new box (although I'd
> prefer not to), as I said it's a relatively simple replication scenario.
> My problem is how to copy or restore a replicated MSSQL 7 database onto a
> MSSQL 2000 box without any problems and leave the original databse intact on
> the original server.
> Any ideas?
> DOM.
>
> "John Bell" wrote:
I have a SQL Server 7.0 database which is configured for merge replication.
It has one publication and the publisher and distributor all reside on the
one server.
I now need to move the database to a new server with MSSQL 2000.
I would like to move the DB, replication and all if that's possible.
I have considered the copy database wizard but, as far as I know, it cannot
deal with replicated databases. I also tried restoring the database but get a
invalid column name'excluded_cols' error message which, I believe, is down to
replication being enabled on the original database.
As the merge replication is relatively uncomplicated I could perhaps create
the publication afresh on the new server. However how do I get the database
on to the MSSQL 2000 server in the first place?
I have also considered installing MSSQL 7.0 on the new server and then
restoring the database and upgrading it. Then decommissioning the old server.
Would replication be enabled on the new server?
Or are there any simpler means of achieving the same ends?
Any advice or shared experience appreciated.
DOM
Hi
Why don't you remove replication, restore the database and then re-create
the replication?
John
"Dom" wrote:
> Hi,
> I have a SQL Server 7.0 database which is configured for merge replication.
> It has one publication and the publisher and distributor all reside on the
> one server.
> I now need to move the database to a new server with MSSQL 2000.
> I would like to move the DB, replication and all if that's possible.
> I have considered the copy database wizard but, as far as I know, it cannot
> deal with replicated databases. I also tried restoring the database but get a
> invalid column name'excluded_cols' error message which, I believe, is down to
> replication being enabled on the original database.
> As the merge replication is relatively uncomplicated I could perhaps create
> the publication afresh on the new server. However how do I get the database
> on to the MSSQL 2000 server in the first place?
> I have also considered installing MSSQL 7.0 on the new server and then
> restoring the database and upgrading it. Then decommissioning the old server.
> Would replication be enabled on the new server?
> Or are there any simpler means of achieving the same ends?
> Any advice or shared experience appreciated.
> DOM
>
|||Hi John,
I would like to leave the original MSSQL 7.0 server fully operational as a
backup in case of problems with the new MSSQL 2000 box.
Therefore I want to leave replication intact on the original server .
I have no problem re-creating replication on the new box (although I'd
prefer not to), as I said it's a relatively simple replication scenario.
My problem is how to copy or restore a replicated MSSQL 7 database onto a
MSSQL 2000 box without any problems and leave the original databse intact on
the original server.
Any ideas?
DOM.
"John Bell" wrote:
> Hi
> Why don't you remove replication, restore the database and then re-create
> the replication?
> John
>
|||Hi
I would install SQL 2000 as a second instance on the second server. Restore
the database on the SQL 7 instance. Remove replication from the database.
Backup the database and restore it on SQL 2000.
Once tested you can use the same method for the upgrade, but on the primary
server you can remove SQL 7 and do a fresh SQL 2000 install. Once that is
working you can upgrade the secondary server.
You can do risk assessment on what/if scenarios, and you may want to take
server images in case you need to recover quickly at any point. Your
secondary server can be a standby alternative SQL 7 installation and SQL 2000
installation (you just need the disc space to hold it all!).
John
"Dom" wrote:
[vbcol=seagreen]
> Hi John,
> I would like to leave the original MSSQL 7.0 server fully operational as a
> backup in case of problems with the new MSSQL 2000 box.
> Therefore I want to leave replication intact on the original server .
> I have no problem re-creating replication on the new box (although I'd
> prefer not to), as I said it's a relatively simple replication scenario.
> My problem is how to copy or restore a replicated MSSQL 7 database onto a
> MSSQL 2000 box without any problems and leave the original databse intact on
> the original server.
> Any ideas?
> DOM.
>
> "John Bell" wrote:
Moving MSSQL 7.0 Replicated database to MSSQL 2000
Hi,
I have a SQL Server 7.0 database which is configured for merge replication.
It has one publication and the publisher and distributor all reside on the
one server.
I now need to move the database to a new server with MSSQL 2000.
I would like to move the DB, replication and all if that's possible.
I have considered the copy database wizard but, as far as I know, it cannot
deal with replicated databases. I also tried restoring the database but get a
invalid column name'excluded_cols' error message which, I believe, is down to
replication being enabled on the original database.
As the merge replication is relatively uncomplicated I could perhaps create
the publication afresh on the new server. However how do I get the database
on to the MSSQL 2000 server in the first place?
I have also considered installing MSSQL 7.0 on the new server and then
restoring the database and upgrading it. Then decommissioning the old server.
Would replication be enabled on the new server?
Or are there any simpler means of achieving the same ends?
Any advice or shared experience appreciated.
DOMHi
Why don't you remove replication, restore the database and then re-create
the replication?
John
"Dom" wrote:
> Hi,
> I have a SQL Server 7.0 database which is configured for merge replication.
> It has one publication and the publisher and distributor all reside on the
> one server.
> I now need to move the database to a new server with MSSQL 2000.
> I would like to move the DB, replication and all if that's possible.
> I have considered the copy database wizard but, as far as I know, it cannot
> deal with replicated databases. I also tried restoring the database but get a
> invalid column name'excluded_cols' error message which, I believe, is down to
> replication being enabled on the original database.
> As the merge replication is relatively uncomplicated I could perhaps create
> the publication afresh on the new server. However how do I get the database
> on to the MSSQL 2000 server in the first place?
> I have also considered installing MSSQL 7.0 on the new server and then
> restoring the database and upgrading it. Then decommissioning the old server.
> Would replication be enabled on the new server?
> Or are there any simpler means of achieving the same ends?
> Any advice or shared experience appreciated.
> DOM
>|||Hi John,
I would like to leave the original MSSQL 7.0 server fully operational as a
backup in case of problems with the new MSSQL 2000 box.
Therefore I want to leave replication intact on the original server .
I have no problem re-creating replication on the new box (although I'd
prefer not to), as I said it's a relatively simple replication scenario.
My problem is how to copy or restore a replicated MSSQL 7 database onto a
MSSQL 2000 box without any problems and leave the original databse intact on
the original server.
Any ideas?
DOM.
"John Bell" wrote:
> Hi
> Why don't you remove replication, restore the database and then re-create
> the replication?
> John
>|||Hi
I would install SQL 2000 as a second instance on the second server. Restore
the database on the SQL 7 instance. Remove replication from the database.
Backup the database and restore it on SQL 2000.
Once tested you can use the same method for the upgrade, but on the primary
server you can remove SQL 7 and do a fresh SQL 2000 install. Once that is
working you can upgrade the secondary server.
You can do risk assessment on what/if scenarios, and you may want to take
server images in case you need to recover quickly at any point. Your
secondary server can be a standby alternative SQL 7 installation and SQL 2000
installation (you just need the disc space to hold it all!).
John
"Dom" wrote:
> Hi John,
> I would like to leave the original MSSQL 7.0 server fully operational as a
> backup in case of problems with the new MSSQL 2000 box.
> Therefore I want to leave replication intact on the original server .
> I have no problem re-creating replication on the new box (although I'd
> prefer not to), as I said it's a relatively simple replication scenario.
> My problem is how to copy or restore a replicated MSSQL 7 database onto a
> MSSQL 2000 box without any problems and leave the original databse intact on
> the original server.
> Any ideas?
> DOM.
>
> "John Bell" wrote:
> > Hi
> >
> > Why don't you remove replication, restore the database and then re-create
> > the replication?
> >
> > John
> >
I have a SQL Server 7.0 database which is configured for merge replication.
It has one publication and the publisher and distributor all reside on the
one server.
I now need to move the database to a new server with MSSQL 2000.
I would like to move the DB, replication and all if that's possible.
I have considered the copy database wizard but, as far as I know, it cannot
deal with replicated databases. I also tried restoring the database but get a
invalid column name'excluded_cols' error message which, I believe, is down to
replication being enabled on the original database.
As the merge replication is relatively uncomplicated I could perhaps create
the publication afresh on the new server. However how do I get the database
on to the MSSQL 2000 server in the first place?
I have also considered installing MSSQL 7.0 on the new server and then
restoring the database and upgrading it. Then decommissioning the old server.
Would replication be enabled on the new server?
Or are there any simpler means of achieving the same ends?
Any advice or shared experience appreciated.
DOMHi
Why don't you remove replication, restore the database and then re-create
the replication?
John
"Dom" wrote:
> Hi,
> I have a SQL Server 7.0 database which is configured for merge replication.
> It has one publication and the publisher and distributor all reside on the
> one server.
> I now need to move the database to a new server with MSSQL 2000.
> I would like to move the DB, replication and all if that's possible.
> I have considered the copy database wizard but, as far as I know, it cannot
> deal with replicated databases. I also tried restoring the database but get a
> invalid column name'excluded_cols' error message which, I believe, is down to
> replication being enabled on the original database.
> As the merge replication is relatively uncomplicated I could perhaps create
> the publication afresh on the new server. However how do I get the database
> on to the MSSQL 2000 server in the first place?
> I have also considered installing MSSQL 7.0 on the new server and then
> restoring the database and upgrading it. Then decommissioning the old server.
> Would replication be enabled on the new server?
> Or are there any simpler means of achieving the same ends?
> Any advice or shared experience appreciated.
> DOM
>|||Hi John,
I would like to leave the original MSSQL 7.0 server fully operational as a
backup in case of problems with the new MSSQL 2000 box.
Therefore I want to leave replication intact on the original server .
I have no problem re-creating replication on the new box (although I'd
prefer not to), as I said it's a relatively simple replication scenario.
My problem is how to copy or restore a replicated MSSQL 7 database onto a
MSSQL 2000 box without any problems and leave the original databse intact on
the original server.
Any ideas?
DOM.
"John Bell" wrote:
> Hi
> Why don't you remove replication, restore the database and then re-create
> the replication?
> John
>|||Hi
I would install SQL 2000 as a second instance on the second server. Restore
the database on the SQL 7 instance. Remove replication from the database.
Backup the database and restore it on SQL 2000.
Once tested you can use the same method for the upgrade, but on the primary
server you can remove SQL 7 and do a fresh SQL 2000 install. Once that is
working you can upgrade the secondary server.
You can do risk assessment on what/if scenarios, and you may want to take
server images in case you need to recover quickly at any point. Your
secondary server can be a standby alternative SQL 7 installation and SQL 2000
installation (you just need the disc space to hold it all!).
John
"Dom" wrote:
> Hi John,
> I would like to leave the original MSSQL 7.0 server fully operational as a
> backup in case of problems with the new MSSQL 2000 box.
> Therefore I want to leave replication intact on the original server .
> I have no problem re-creating replication on the new box (although I'd
> prefer not to), as I said it's a relatively simple replication scenario.
> My problem is how to copy or restore a replicated MSSQL 7 database onto a
> MSSQL 2000 box without any problems and leave the original databse intact on
> the original server.
> Any ideas?
> DOM.
>
> "John Bell" wrote:
> > Hi
> >
> > Why don't you remove replication, restore the database and then re-create
> > the replication?
> >
> > John
> >
Moving MSSQL 7.0 Replicated database to MSSQL 2000
Hi,
I have a SQL Server 7.0 database which is configured for merge replication.
It has one publication and the publisher and distributor all reside on the
one server.
I now need to move the database to a new server with MSSQL 2000.
I would like to move the DB, replication and all if that's possible.
I have considered the copy database wizard but, as far as I know, it cannot
deal with replicated databases. I also tried restoring the database but get
a
invalid column name'excluded_cols' error message which, I believe, is down t
o
replication being enabled on the original database.
As the merge replication is relatively uncomplicated I could perhaps create
the publication afresh on the new server. However how do I get the database
on to the MSSQL 2000 server in the first place?
I have also considered installing MSSQL 7.0 on the new server and then
restoring the database and upgrading it. Then decommissioning the old server
.
Would replication be enabled on the new server?
Or are there any simpler means of achieving the same ends?
Any advice or shared experience appreciated.
DOMHi
Why don't you remove replication, restore the database and then re-create
the replication?
John
"Dom" wrote:
> Hi,
> I have a SQL Server 7.0 database which is configured for merge replicatio
n.
> It has one publication and the publisher and distributor all reside on the
> one server.
> I now need to move the database to a new server with MSSQL 2000.
> I would like to move the DB, replication and all if that's possible.
> I have considered the copy database wizard but, as far as I know, it canno
t
> deal with replicated databases. I also tried restoring the database but ge
t a
> invalid column name'excluded_cols' error message which, I believe, is down
to
> replication being enabled on the original database.
> As the merge replication is relatively uncomplicated I could perhaps creat
e
> the publication afresh on the new server. However how do I get the databas
e
> on to the MSSQL 2000 server in the first place?
> I have also considered installing MSSQL 7.0 on the new server and then
> restoring the database and upgrading it. Then decommissioning the old serv
er.
> Would replication be enabled on the new server?
> Or are there any simpler means of achieving the same ends?
> Any advice or shared experience appreciated.
> DOM
>|||Hi John,
I would like to leave the original MSSQL 7.0 server fully operational as a
backup in case of problems with the new MSSQL 2000 box.
Therefore I want to leave replication intact on the original server .
I have no problem re-creating replication on the new box (although I'd
prefer not to), as I said it's a relatively simple replication scenario.
My problem is how to copy or restore a replicated MSSQL 7 database onto a
MSSQL 2000 box without any problems and leave the original databse intact on
the original server.
Any ideas?
DOM.
"John Bell" wrote:
> Hi
> Why don't you remove replication, restore the database and then re-create
> the replication?
> John
>|||Hi
I would install SQL 2000 as a second instance on the second server. Restore
the database on the SQL 7 instance. Remove replication from the database.
Backup the database and restore it on SQL 2000.
Once tested you can use the same method for the upgrade, but on the primary
server you can remove SQL 7 and do a fresh SQL 2000 install. Once that is
working you can upgrade the secondary server.
You can do risk assessment on what/if scenarios, and you may want to take
server images in case you need to recover quickly at any point. Your
secondary server can be a standby alternative SQL 7 installation and SQL 200
0
installation (you just need the disc space to hold it all!).
John
"Dom" wrote:
[vbcol=seagreen]
> Hi John,
> I would like to leave the original MSSQL 7.0 server fully operational as
a
> backup in case of problems with the new MSSQL 2000 box.
> Therefore I want to leave replication intact on the original server .
> I have no problem re-creating replication on the new box (although I'd
> prefer not to), as I said it's a relatively simple replication scenario.
> My problem is how to copy or restore a replicated MSSQL 7 database onto a
> MSSQL 2000 box without any problems and leave the original databse intact
on
> the original server.
> Any ideas?
> DOM.
>
> "John Bell" wrote:
>
I have a SQL Server 7.0 database which is configured for merge replication.
It has one publication and the publisher and distributor all reside on the
one server.
I now need to move the database to a new server with MSSQL 2000.
I would like to move the DB, replication and all if that's possible.
I have considered the copy database wizard but, as far as I know, it cannot
deal with replicated databases. I also tried restoring the database but get
a
invalid column name'excluded_cols' error message which, I believe, is down t
o
replication being enabled on the original database.
As the merge replication is relatively uncomplicated I could perhaps create
the publication afresh on the new server. However how do I get the database
on to the MSSQL 2000 server in the first place?
I have also considered installing MSSQL 7.0 on the new server and then
restoring the database and upgrading it. Then decommissioning the old server
.
Would replication be enabled on the new server?
Or are there any simpler means of achieving the same ends?
Any advice or shared experience appreciated.
DOMHi
Why don't you remove replication, restore the database and then re-create
the replication?
John
"Dom" wrote:
> Hi,
> I have a SQL Server 7.0 database which is configured for merge replicatio
n.
> It has one publication and the publisher and distributor all reside on the
> one server.
> I now need to move the database to a new server with MSSQL 2000.
> I would like to move the DB, replication and all if that's possible.
> I have considered the copy database wizard but, as far as I know, it canno
t
> deal with replicated databases. I also tried restoring the database but ge
t a
> invalid column name'excluded_cols' error message which, I believe, is down
to
> replication being enabled on the original database.
> As the merge replication is relatively uncomplicated I could perhaps creat
e
> the publication afresh on the new server. However how do I get the databas
e
> on to the MSSQL 2000 server in the first place?
> I have also considered installing MSSQL 7.0 on the new server and then
> restoring the database and upgrading it. Then decommissioning the old serv
er.
> Would replication be enabled on the new server?
> Or are there any simpler means of achieving the same ends?
> Any advice or shared experience appreciated.
> DOM
>|||Hi John,
I would like to leave the original MSSQL 7.0 server fully operational as a
backup in case of problems with the new MSSQL 2000 box.
Therefore I want to leave replication intact on the original server .
I have no problem re-creating replication on the new box (although I'd
prefer not to), as I said it's a relatively simple replication scenario.
My problem is how to copy or restore a replicated MSSQL 7 database onto a
MSSQL 2000 box without any problems and leave the original databse intact on
the original server.
Any ideas?
DOM.
"John Bell" wrote:
> Hi
> Why don't you remove replication, restore the database and then re-create
> the replication?
> John
>|||Hi
I would install SQL 2000 as a second instance on the second server. Restore
the database on the SQL 7 instance. Remove replication from the database.
Backup the database and restore it on SQL 2000.
Once tested you can use the same method for the upgrade, but on the primary
server you can remove SQL 7 and do a fresh SQL 2000 install. Once that is
working you can upgrade the secondary server.
You can do risk assessment on what/if scenarios, and you may want to take
server images in case you need to recover quickly at any point. Your
secondary server can be a standby alternative SQL 7 installation and SQL 200
0
installation (you just need the disc space to hold it all!).
John
"Dom" wrote:
[vbcol=seagreen]
> Hi John,
> I would like to leave the original MSSQL 7.0 server fully operational as
a
> backup in case of problems with the new MSSQL 2000 box.
> Therefore I want to leave replication intact on the original server .
> I have no problem re-creating replication on the new box (although I'd
> prefer not to), as I said it's a relatively simple replication scenario.
> My problem is how to copy or restore a replicated MSSQL 7 database onto a
> MSSQL 2000 box without any problems and leave the original databse intact
on
> the original server.
> Any ideas?
> DOM.
>
> "John Bell" wrote:
>
Moving MSDE SQL Server with OSQL
I am a complete neophyt to SQL. I am attempting to restore a backup from a
MSDE 2000 SQL server from a peer to peer server to a server running Small
Business Server 2003 using OSQL. (In other words I’m moving the database to
a dedicated server.) I performed a RESTORE DATABASE xxx FROM DISK=
‘PATHNAME’ WITH REPLACE
OSQL responded with “RESTORE DATABASE successfully processed xxx pages” Now
I need to run some stored procedures to fix the orphaned user issue, but when
I attempt to login to the database with user “sa” no matter what password I
use I can’t get in. (I’m not sure there is a user “sa” in the restored
database). From what I’ve read, I believe a may need to run the
sp_changedbowner command, but I’m not sure what login I need to change to.
Also, I DID NOT move any "system files" ie master.mdf or model.mdf files. Do
these have to be moved as well? Any suggestions would be greatly
appreciated. Thanks in advance.
Mark G
First, you need to know the new SQL Server (on your Smaill Business
Server2003) has mixed security mode enabled (Only Windows security is
enabled by default installation). If not, you would obviously cannot use
"sa" ( and cannot use any username/password pair in that matter).
To use OSQL.exe tool, you do not have to use "sa" though, you can use -E
swicth with osql.exe to log into SQL Server with trusted connection (Windows
Authentication). Of course you need to log onto your computer as local
admin.
"Mark Grantom" <mgrantom@.swbell.net[no spam]> wrote in message
news:D218EA2E-9D0B-4372-8E22-A58E8FBA1F96@.microsoft.com...
>I am a complete neophyt to SQL. I am attempting to restore a backup from a
> MSDE 2000 SQL server from a peer to peer server to a server running Small
> Business Server 2003 using OSQL. (In other words I'm moving the database
> to
> a dedicated server.) I performed a RESTORE DATABASE xxx FROM DISK=
> 'PATHNAME' WITH REPLACE
> OSQL responded with "RESTORE DATABASE successfully processed xxx pages"
> Now
> I need to run some stored procedures to fix the orphaned user issue, but
> when
> I attempt to login to the database with user "sa" no matter what password
> I
> use I can't get in. (I'm not sure there is a user "sa" in the restored
> database). From what I've read, I believe a may need to run the
> sp_changedbowner command, but I'm not sure what login I need to change to.
> Also, I DID NOT move any "system files" ie master.mdf or model.mdf files.
> Do
> these have to be moved as well? Any suggestions would be greatly
> appreciated. Thanks in advance.
> --
> Mark G
|||hi Mark,
Mark Grantom wrote:
> I am a complete neophyt to SQL. I am attempting to restore a backup
> from a MSDE 2000 SQL server from a peer to peer server to a server
> running Small Business Server 2003 using OSQL. (In other words I'm
> moving the database to a dedicated server.) I performed a RESTORE
> DATABASE xxx FROM DISK= 'PATHNAME' WITH REPLACE
> OSQL responded with "RESTORE DATABASE successfully processed xxx
> pages" Now I need to run some stored procedures to fix the orphaned
> user issue, but when I attempt to login to the database with user
> "sa" no matter what password I use I can't get in. (I'm not sure
> there is a user "sa" in the restored database). From what I've read,
> I believe a may need to run the sp_changedbowner command, but I'm not
> sure what login I need to change to. Also, I DID NOT move any "system
> files" ie master.mdf or model.mdf files. Do these have to be moved
> as well? Any suggestions would be greatly appreciated. Thanks in
> advance.
chances are the problem is related to authentication... MSDE installs by
default only allowing trusted connections and not allowing mixed security
connections relating to SQL Server logins and password credentials.. if
this is the case, you can have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;285097 for further
info about how to "hack" the Windows registry to allow trusted and mixed
security authenticated connections..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||OK, I forgot to say, I did log in with entrusted option to do the initial
RESTORE. I can change to the mixed login option by modifying the registry no
problem. Do I then move the "system files" or not. If so, how? Thanks
Mark G
"Andrea Montanari" wrote:
> hi Mark,
> Mark Grantom wrote:
> chances are the problem is related to authentication... MSDE installs by
> default only allowing trusted connections and not allowing mixed security
> connections relating to SQL Server logins and password credentials.. if
> this is the case, you can have a look at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;285097 for further
> info about how to "hack" the Windows registry to allow trusted and mixed
> security authenticated connections..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> OK, I forgot to say, I did log in with entrusted option to do the
> initial RESTORE. I can change to the mixed login option by modifying
> the registry no problem. Do I then move the "system files" or not.
> If so, how? Thanks
why do you like to "move" system database as well? transferring system
databases between different instances is not a very safe operation.. I'd
not...
you've better "stay" with the new instance ones... you "only" have to
re-create all the "original" desired/required logins and remap them to your
user's databases via that system stored procedure you already mentionned,
so_change_users_login..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||I went back and read my messages twice. I don't "like" to move system
databases. In fact I have NEVER moved a system database. I'm not entirely
certain WHAT a system database is although I do have my suspicions. Remember
I am a rank beginner with SQL. I did ask twice, whether I NEEDED to move
system databases. I take it from your response that the answer is NO? Also,
I checked my system and the "mixed" login mode was already enabled in the
registry. I don't believe that I have a user "sa". How do I create this
user? Thanks.
Mark G
"Andrea Montanari" wrote:
> hi Mark,
> Mark Grantom wrote:
> why do you like to "move" system database as well? transferring system
> databases between different instances is not a very safe operation.. I'd
> not...
> you've better "stay" with the new instance ones... you "only" have to
> re-create all the "original" desired/required logins and remap them to your
> user's databases via that system stored procedure you already mentionned,
> so_change_users_login..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> I went back and read my messages twice. I don't "like" to move system
> databases. In fact I have NEVER moved a system database. I'm not
> entirely certain WHAT a system database is although I do have my
> suspicions. Remember I am a rank beginner with SQL. I did ask
> twice, whether I NEEDED to move system databases. I take it from
> your response that the answer is NO?
you usually do not have to... when you installed the "new" SQL Server/MSDE
instance it installed with it's own system databases... so you are ok with
them..
> Also, I checked my system and
> the "mixed" login mode was already enabled in the registry. I don't
> believe that I have a user "sa". How do I create this user? Thanks.
"sa" login can not be created... it's created at installation time.. and you
have it for sure
what is the exact exception you are reported with when connecting using "sa"
credentials?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||I get:
Login failed for user 'sa'.
Mark G
"Andrea Montanari" wrote:
> hi Mark,
> Mark Grantom wrote:
> you usually do not have to... when you installed the "new" SQL Server/MSDE
> instance it installed with it's own system databases... so you are ok with
> them..
> "sa" login can not be created... it's created at installation time.. and you
> have it for sure
> what is the exact exception you are reported with when connecting using "sa"
> credentials?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> I get:
> Login failed for user 'sa'.
with something else, like "not associated with a trusted connection"?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
MSDE 2000 SQL server from a peer to peer server to a server running Small
Business Server 2003 using OSQL. (In other words I’m moving the database to
a dedicated server.) I performed a RESTORE DATABASE xxx FROM DISK=
‘PATHNAME’ WITH REPLACE
OSQL responded with “RESTORE DATABASE successfully processed xxx pages” Now
I need to run some stored procedures to fix the orphaned user issue, but when
I attempt to login to the database with user “sa” no matter what password I
use I can’t get in. (I’m not sure there is a user “sa” in the restored
database). From what I’ve read, I believe a may need to run the
sp_changedbowner command, but I’m not sure what login I need to change to.
Also, I DID NOT move any "system files" ie master.mdf or model.mdf files. Do
these have to be moved as well? Any suggestions would be greatly
appreciated. Thanks in advance.
Mark G
First, you need to know the new SQL Server (on your Smaill Business
Server2003) has mixed security mode enabled (Only Windows security is
enabled by default installation). If not, you would obviously cannot use
"sa" ( and cannot use any username/password pair in that matter).
To use OSQL.exe tool, you do not have to use "sa" though, you can use -E
swicth with osql.exe to log into SQL Server with trusted connection (Windows
Authentication). Of course you need to log onto your computer as local
admin.
"Mark Grantom" <mgrantom@.swbell.net[no spam]> wrote in message
news:D218EA2E-9D0B-4372-8E22-A58E8FBA1F96@.microsoft.com...
>I am a complete neophyt to SQL. I am attempting to restore a backup from a
> MSDE 2000 SQL server from a peer to peer server to a server running Small
> Business Server 2003 using OSQL. (In other words I'm moving the database
> to
> a dedicated server.) I performed a RESTORE DATABASE xxx FROM DISK=
> 'PATHNAME' WITH REPLACE
> OSQL responded with "RESTORE DATABASE successfully processed xxx pages"
> Now
> I need to run some stored procedures to fix the orphaned user issue, but
> when
> I attempt to login to the database with user "sa" no matter what password
> I
> use I can't get in. (I'm not sure there is a user "sa" in the restored
> database). From what I've read, I believe a may need to run the
> sp_changedbowner command, but I'm not sure what login I need to change to.
> Also, I DID NOT move any "system files" ie master.mdf or model.mdf files.
> Do
> these have to be moved as well? Any suggestions would be greatly
> appreciated. Thanks in advance.
> --
> Mark G
|||hi Mark,
Mark Grantom wrote:
> I am a complete neophyt to SQL. I am attempting to restore a backup
> from a MSDE 2000 SQL server from a peer to peer server to a server
> running Small Business Server 2003 using OSQL. (In other words I'm
> moving the database to a dedicated server.) I performed a RESTORE
> DATABASE xxx FROM DISK= 'PATHNAME' WITH REPLACE
> OSQL responded with "RESTORE DATABASE successfully processed xxx
> pages" Now I need to run some stored procedures to fix the orphaned
> user issue, but when I attempt to login to the database with user
> "sa" no matter what password I use I can't get in. (I'm not sure
> there is a user "sa" in the restored database). From what I've read,
> I believe a may need to run the sp_changedbowner command, but I'm not
> sure what login I need to change to. Also, I DID NOT move any "system
> files" ie master.mdf or model.mdf files. Do these have to be moved
> as well? Any suggestions would be greatly appreciated. Thanks in
> advance.
chances are the problem is related to authentication... MSDE installs by
default only allowing trusted connections and not allowing mixed security
connections relating to SQL Server logins and password credentials.. if
this is the case, you can have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;285097 for further
info about how to "hack" the Windows registry to allow trusted and mixed
security authenticated connections..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||OK, I forgot to say, I did log in with entrusted option to do the initial
RESTORE. I can change to the mixed login option by modifying the registry no
problem. Do I then move the "system files" or not. If so, how? Thanks
Mark G
"Andrea Montanari" wrote:
> hi Mark,
> Mark Grantom wrote:
> chances are the problem is related to authentication... MSDE installs by
> default only allowing trusted connections and not allowing mixed security
> connections relating to SQL Server logins and password credentials.. if
> this is the case, you can have a look at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;285097 for further
> info about how to "hack" the Windows registry to allow trusted and mixed
> security authenticated connections..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> OK, I forgot to say, I did log in with entrusted option to do the
> initial RESTORE. I can change to the mixed login option by modifying
> the registry no problem. Do I then move the "system files" or not.
> If so, how? Thanks
why do you like to "move" system database as well? transferring system
databases between different instances is not a very safe operation.. I'd
not...
you've better "stay" with the new instance ones... you "only" have to
re-create all the "original" desired/required logins and remap them to your
user's databases via that system stored procedure you already mentionned,
so_change_users_login..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||I went back and read my messages twice. I don't "like" to move system
databases. In fact I have NEVER moved a system database. I'm not entirely
certain WHAT a system database is although I do have my suspicions. Remember
I am a rank beginner with SQL. I did ask twice, whether I NEEDED to move
system databases. I take it from your response that the answer is NO? Also,
I checked my system and the "mixed" login mode was already enabled in the
registry. I don't believe that I have a user "sa". How do I create this
user? Thanks.
Mark G
"Andrea Montanari" wrote:
> hi Mark,
> Mark Grantom wrote:
> why do you like to "move" system database as well? transferring system
> databases between different instances is not a very safe operation.. I'd
> not...
> you've better "stay" with the new instance ones... you "only" have to
> re-create all the "original" desired/required logins and remap them to your
> user's databases via that system stored procedure you already mentionned,
> so_change_users_login..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> I went back and read my messages twice. I don't "like" to move system
> databases. In fact I have NEVER moved a system database. I'm not
> entirely certain WHAT a system database is although I do have my
> suspicions. Remember I am a rank beginner with SQL. I did ask
> twice, whether I NEEDED to move system databases. I take it from
> your response that the answer is NO?
you usually do not have to... when you installed the "new" SQL Server/MSDE
instance it installed with it's own system databases... so you are ok with
them..
> Also, I checked my system and
> the "mixed" login mode was already enabled in the registry. I don't
> believe that I have a user "sa". How do I create this user? Thanks.
"sa" login can not be created... it's created at installation time.. and you
have it for sure
what is the exact exception you are reported with when connecting using "sa"
credentials?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||I get:
Login failed for user 'sa'.
Mark G
"Andrea Montanari" wrote:
> hi Mark,
> Mark Grantom wrote:
> you usually do not have to... when you installed the "new" SQL Server/MSDE
> instance it installed with it's own system databases... so you are ok with
> them..
> "sa" login can not be created... it's created at installation time.. and you
> have it for sure
> what is the exact exception you are reported with when connecting using "sa"
> credentials?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Mark,
Mark Grantom wrote:
> I get:
> Login failed for user 'sa'.
with something else, like "not associated with a trusted connection"?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
moving MSDE database to SQL...
rI have an end-use that created a database on MSDE and is housing it on
his local computer. We want to move/copy it to our SQL server so it
can be backed up etc. What are the appropriate steps in doing so?
Thanks in advance,
KenIf they have both the same (and probably latest) service packs, the
compatibility is 100% and you don't have to take any special step (excerpt
maybe for authentification and login information). So a Backup/Restore or a
Detach/Reattach operation will be the easiest way.
S. L.
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> rI have an end-use that created a database on MSDE and is housing it on
> his local computer. We want to move/copy it to our SQL server so it
> can be backed up etc. What are the appropriate steps in doing so?
> Thanks in advance,
> Ken
>|||Thanks for the reply, but I have no idea what the command lines are for MSDE
in order to backup etc. Where would I find those that I need in order to
backup and then restore to the SQL server?
Thanks,
Ken
"Sylvain Lafontaine" wrote:
> If they have both the same (and probably latest) service packs, the
> compatibility is 100% and you don't have to take any special step (excerpt
> maybe for authentification and login information). So a Backup/Restore or
a
> Detach/Reattach operation will be the easiest way.
> S. L.
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
>
>|||Well, look up BACKUP DATABASE in Books Online, and to execute it against
MSDE, you can use
osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
or
osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
http://www.aspfaq.com/
(Reverse address to reply.)
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> Thanks for the reply, but I have no idea what the command lines are for
MSDE[vbcol=seagreen]
> in order to backup etc. Where would I find those that I need in order to
> backup and then restore to the SQL server?
> Thanks,
> Ken
> "Sylvain Lafontaine" wrote:
>
(excerpt[vbcol=seagreen]
or a[vbcol=seagreen]
on[vbcol=seagreen]|||Mr. Aaron,
The problem with this is going to be the users password which Ken needs to
recreate after restoring the db.
v/r
ktf
"Aaron [SQL Server MVP]" wrote:
> Well, look up BACKUP DATABASE in Books Online, and to execute it against
> MSDE, you can use
> osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
> or
> osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> MSDE
> (excerpt
> or a
> on
>
>|||> The problem with this is going to be the users password which Ken needs to
> recreate after restoring the db.
And he can't do:
osql -S(local)\instancename -E -Q"EXEC sp_password ..."
?
http://www.aspfaq.com/
(Reverse address to reply.)
his local computer. We want to move/copy it to our SQL server so it
can be backed up etc. What are the appropriate steps in doing so?
Thanks in advance,
KenIf they have both the same (and probably latest) service packs, the
compatibility is 100% and you don't have to take any special step (excerpt
maybe for authentification and login information). So a Backup/Restore or a
Detach/Reattach operation will be the easiest way.
S. L.
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> rI have an end-use that created a database on MSDE and is housing it on
> his local computer. We want to move/copy it to our SQL server so it
> can be backed up etc. What are the appropriate steps in doing so?
> Thanks in advance,
> Ken
>|||Thanks for the reply, but I have no idea what the command lines are for MSDE
in order to backup etc. Where would I find those that I need in order to
backup and then restore to the SQL server?
Thanks,
Ken
"Sylvain Lafontaine" wrote:
> If they have both the same (and probably latest) service packs, the
> compatibility is 100% and you don't have to take any special step (excerpt
> maybe for authentification and login information). So a Backup/Restore or
a
> Detach/Reattach operation will be the easiest way.
> S. L.
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
>
>|||Well, look up BACKUP DATABASE in Books Online, and to execute it against
MSDE, you can use
osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
or
osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
http://www.aspfaq.com/
(Reverse address to reply.)
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> Thanks for the reply, but I have no idea what the command lines are for
MSDE[vbcol=seagreen]
> in order to backup etc. Where would I find those that I need in order to
> backup and then restore to the SQL server?
> Thanks,
> Ken
> "Sylvain Lafontaine" wrote:
>
(excerpt[vbcol=seagreen]
or a[vbcol=seagreen]
on[vbcol=seagreen]|||Mr. Aaron,
The problem with this is going to be the users password which Ken needs to
recreate after restoring the db.
v/r
ktf
"Aaron [SQL Server MVP]" wrote:
> Well, look up BACKUP DATABASE in Books Online, and to execute it against
> MSDE, you can use
> osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
> or
> osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> MSDE
> (excerpt
> or a
> on
>
>|||> The problem with this is going to be the users password which Ken needs to
> recreate after restoring the db.
And he can't do:
osql -S(local)\instancename -E -Q"EXEC sp_password ..."
?
http://www.aspfaq.com/
(Reverse address to reply.)
moving MSDE database to SQL...
rI have an end-use that created a database on MSDE and is housing it on
his local computer. We want to move/copy it to our SQL server so it
can be backed up etc. What are the appropriate steps in doing so?
Thanks in advance,
Ken
If they have both the same (and probably latest) service packs, the
compatibility is 100% and you don't have to take any special step (excerpt
maybe for authentification and login information). So a Backup/Restore or a
Detach/Reattach operation will be the easiest way.
S. L.
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> rI have an end-use that created a database on MSDE and is housing it on
> his local computer. We want to move/copy it to our SQL server so it
> can be backed up etc. What are the appropriate steps in doing so?
> Thanks in advance,
> Ken
>
|||Thanks for the reply, but I have no idea what the command lines are for MSDE
in order to backup etc. Where would I find those that I need in order to
backup and then restore to the SQL server?
Thanks,
Ken
"Sylvain Lafontaine" wrote:
> If they have both the same (and probably latest) service packs, the
> compatibility is 100% and you don't have to take any special step (excerpt
> maybe for authentification and login information). So a Backup/Restore or a
> Detach/Reattach operation will be the easiest way.
> S. L.
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
>
>
|||Well, look up BACKUP DATABASE in Books Online, and to execute it against
MSDE, you can use
osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
or
osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
http://www.aspfaq.com/
(Reverse address to reply.)
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> Thanks for the reply, but I have no idea what the command lines are for
MSDE[vbcol=seagreen]
> in order to backup etc. Where would I find those that I need in order to
> backup and then restore to the SQL server?
> Thanks,
> Ken
> "Sylvain Lafontaine" wrote:
(excerpt[vbcol=seagreen]
or a[vbcol=seagreen]
on[vbcol=seagreen]
|||Mr. Aaron,
The problem with this is going to be the users password which Ken needs to
recreate after restoring the db.
v/r
ktf
"Aaron [SQL Server MVP]" wrote:
> Well, look up BACKUP DATABASE in Books Online, and to execute it against
> MSDE, you can use
> osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
> or
> osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> MSDE
> (excerpt
> or a
> on
>
>
|||> The problem with this is going to be the users password which Ken needs to
> recreate after restoring the db.
And he can't do:
osql -S(local)\instancename -E -Q"EXEC sp_password ..."
?
http://www.aspfaq.com/
(Reverse address to reply.)
his local computer. We want to move/copy it to our SQL server so it
can be backed up etc. What are the appropriate steps in doing so?
Thanks in advance,
Ken
If they have both the same (and probably latest) service packs, the
compatibility is 100% and you don't have to take any special step (excerpt
maybe for authentification and login information). So a Backup/Restore or a
Detach/Reattach operation will be the easiest way.
S. L.
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> rI have an end-use that created a database on MSDE and is housing it on
> his local computer. We want to move/copy it to our SQL server so it
> can be backed up etc. What are the appropriate steps in doing so?
> Thanks in advance,
> Ken
>
|||Thanks for the reply, but I have no idea what the command lines are for MSDE
in order to backup etc. Where would I find those that I need in order to
backup and then restore to the SQL server?
Thanks,
Ken
"Sylvain Lafontaine" wrote:
> If they have both the same (and probably latest) service packs, the
> compatibility is 100% and you don't have to take any special step (excerpt
> maybe for authentification and login information). So a Backup/Restore or a
> Detach/Reattach operation will be the easiest way.
> S. L.
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
>
>
|||Well, look up BACKUP DATABASE in Books Online, and to execute it against
MSDE, you can use
osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
or
osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
http://www.aspfaq.com/
(Reverse address to reply.)
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> Thanks for the reply, but I have no idea what the command lines are for
MSDE[vbcol=seagreen]
> in order to backup etc. Where would I find those that I need in order to
> backup and then restore to the SQL server?
> Thanks,
> Ken
> "Sylvain Lafontaine" wrote:
(excerpt[vbcol=seagreen]
or a[vbcol=seagreen]
on[vbcol=seagreen]
|||Mr. Aaron,
The problem with this is going to be the users password which Ken needs to
recreate after restoring the db.
v/r
ktf
"Aaron [SQL Server MVP]" wrote:
> Well, look up BACKUP DATABASE in Books Online, and to execute it against
> MSDE, you can use
> osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
> or
> osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> MSDE
> (excerpt
> or a
> on
>
>
|||> The problem with this is going to be the users password which Ken needs to
> recreate after restoring the db.
And he can't do:
osql -S(local)\instancename -E -Q"EXEC sp_password ..."
?
http://www.aspfaq.com/
(Reverse address to reply.)
moving MSDE database to SQL...
rI have an end-use that created a database on MSDE and is housing it on
his local computer. We want to move/copy it to our SQL server so it
can be backed up etc. What are the appropriate steps in doing so?
Thanks in advance,
KenIf they have both the same (and probably latest) service packs, the
compatibility is 100% and you don't have to take any special step (excerpt
maybe for authentification and login information). So a Backup/Restore or a
Detach/Reattach operation will be the easiest way.
S. L.
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> rI have an end-use that created a database on MSDE and is housing it on
> his local computer. We want to move/copy it to our SQL server so it
> can be backed up etc. What are the appropriate steps in doing so?
> Thanks in advance,
> Ken
>|||Thanks for the reply, but I have no idea what the command lines are for MSDE
in order to backup etc. Where would I find those that I need in order to
backup and then restore to the SQL server?
Thanks,
Ken
"Sylvain Lafontaine" wrote:
> If they have both the same (and probably latest) service packs, the
> compatibility is 100% and you don't have to take any special step (excerpt
> maybe for authentification and login information). So a Backup/Restore or a
> Detach/Reattach operation will be the easiest way.
> S. L.
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> > rI have an end-use that created a database on MSDE and is housing it on
> > his local computer. We want to move/copy it to our SQL server so it
> > can be backed up etc. What are the appropriate steps in doing so?
> >
> > Thanks in advance,
> >
> > Ken
> >
>
>|||Well, look up BACKUP DATABASE in Books Online, and to execute it against
MSDE, you can use
osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
or
osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> Thanks for the reply, but I have no idea what the command lines are for
MSDE
> in order to backup etc. Where would I find those that I need in order to
> backup and then restore to the SQL server?
> Thanks,
> Ken
> "Sylvain Lafontaine" wrote:
> > If they have both the same (and probably latest) service packs, the
> > compatibility is 100% and you don't have to take any special step
(excerpt
> > maybe for authentification and login information). So a Backup/Restore
or a
> > Detach/Reattach operation will be the easiest way.
> >
> > S. L.
> >
> > "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> > news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> > > rI have an end-use that created a database on MSDE and is housing it
on
> > > his local computer. We want to move/copy it to our SQL server so it
> > > can be backed up etc. What are the appropriate steps in doing so?
> > >
> > > Thanks in advance,
> > >
> > > Ken
> > >
> >
> >
> >|||Mr. Aaron,
The problem with this is going to be the users password which Ken needs to
recreate after restoring the db.
v/r
ktf
"Aaron [SQL Server MVP]" wrote:
> Well, look up BACKUP DATABASE in Books Online, and to execute it against
> MSDE, you can use
> osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
> or
> osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> > Thanks for the reply, but I have no idea what the command lines are for
> MSDE
> > in order to backup etc. Where would I find those that I need in order to
> > backup and then restore to the SQL server?
> >
> > Thanks,
> >
> > Ken
> >
> > "Sylvain Lafontaine" wrote:
> >
> > > If they have both the same (and probably latest) service packs, the
> > > compatibility is 100% and you don't have to take any special step
> (excerpt
> > > maybe for authentification and login information). So a Backup/Restore
> or a
> > > Detach/Reattach operation will be the easiest way.
> > >
> > > S. L.
> > >
> > > "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> > > news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> > > > rI have an end-use that created a database on MSDE and is housing it
> on
> > > > his local computer. We want to move/copy it to our SQL server so it
> > > > can be backed up etc. What are the appropriate steps in doing so?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Ken
> > > >
> > >
> > >
> > >
>
>|||> The problem with this is going to be the users password which Ken needs to
> recreate after restoring the db.
And he can't do:
osql -S(local)\instancename -E -Q"EXEC sp_password ..."
?
--
http://www.aspfaq.com/
(Reverse address to reply.)
his local computer. We want to move/copy it to our SQL server so it
can be backed up etc. What are the appropriate steps in doing so?
Thanks in advance,
KenIf they have both the same (and probably latest) service packs, the
compatibility is 100% and you don't have to take any special step (excerpt
maybe for authentification and login information). So a Backup/Restore or a
Detach/Reattach operation will be the easiest way.
S. L.
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> rI have an end-use that created a database on MSDE and is housing it on
> his local computer. We want to move/copy it to our SQL server so it
> can be backed up etc. What are the appropriate steps in doing so?
> Thanks in advance,
> Ken
>|||Thanks for the reply, but I have no idea what the command lines are for MSDE
in order to backup etc. Where would I find those that I need in order to
backup and then restore to the SQL server?
Thanks,
Ken
"Sylvain Lafontaine" wrote:
> If they have both the same (and probably latest) service packs, the
> compatibility is 100% and you don't have to take any special step (excerpt
> maybe for authentification and login information). So a Backup/Restore or a
> Detach/Reattach operation will be the easiest way.
> S. L.
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> > rI have an end-use that created a database on MSDE and is housing it on
> > his local computer. We want to move/copy it to our SQL server so it
> > can be backed up etc. What are the appropriate steps in doing so?
> >
> > Thanks in advance,
> >
> > Ken
> >
>
>|||Well, look up BACKUP DATABASE in Books Online, and to execute it against
MSDE, you can use
osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
or
osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> Thanks for the reply, but I have no idea what the command lines are for
MSDE
> in order to backup etc. Where would I find those that I need in order to
> backup and then restore to the SQL server?
> Thanks,
> Ken
> "Sylvain Lafontaine" wrote:
> > If they have both the same (and probably latest) service packs, the
> > compatibility is 100% and you don't have to take any special step
(excerpt
> > maybe for authentification and login information). So a Backup/Restore
or a
> > Detach/Reattach operation will be the easiest way.
> >
> > S. L.
> >
> > "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> > news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> > > rI have an end-use that created a database on MSDE and is housing it
on
> > > his local computer. We want to move/copy it to our SQL server so it
> > > can be backed up etc. What are the appropriate steps in doing so?
> > >
> > > Thanks in advance,
> > >
> > > Ken
> > >
> >
> >
> >|||Mr. Aaron,
The problem with this is going to be the users password which Ken needs to
recreate after restoring the db.
v/r
ktf
"Aaron [SQL Server MVP]" wrote:
> Well, look up BACKUP DATABASE in Books Online, and to execute it against
> MSDE, you can use
> osql -S(local)\instancename -E -Q"BACKUP DATABASE ..."
> or
> osql -S(local)\instancename -E -Q"EXEC sp_detachcb ..."
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> news:17196A2A-FC3F-4B6C-AC32-BF41E842AB48@.microsoft.com...
> > Thanks for the reply, but I have no idea what the command lines are for
> MSDE
> > in order to backup etc. Where would I find those that I need in order to
> > backup and then restore to the SQL server?
> >
> > Thanks,
> >
> > Ken
> >
> > "Sylvain Lafontaine" wrote:
> >
> > > If they have both the same (and probably latest) service packs, the
> > > compatibility is 100% and you don't have to take any special step
> (excerpt
> > > maybe for authentification and login information). So a Backup/Restore
> or a
> > > Detach/Reattach operation will be the easiest way.
> > >
> > > S. L.
> > >
> > > "Ken Gardner" <KenGardner@.discussions.microsoft.com> wrote in message
> > > news:1CE3E73D-87E1-4058-BDAC-5D2FDB3984FE@.microsoft.com...
> > > > rI have an end-use that created a database on MSDE and is housing it
> on
> > > > his local computer. We want to move/copy it to our SQL server so it
> > > > can be backed up etc. What are the appropriate steps in doing so?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Ken
> > > >
> > >
> > >
> > >
>
>|||> The problem with this is going to be the users password which Ken needs to
> recreate after restoring the db.
And he can't do:
osql -S(local)\instancename -E -Q"EXEC sp_password ..."
?
--
http://www.aspfaq.com/
(Reverse address to reply.)
Moving MSDB to new location in SQL2000--Urgent
HI all,
what is best way to move msdb to new loctaion (from F to E drive)on the
same system in sql server2000?
Shall I use restore command instead of attaching and detaching...
Thanks in advance..
Suchi
I believe that KB 224071 has explicit instructions for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Suchi" <Suchi@.discussions.microsoft.com> wrote in message
news:F096E1C9-CDDF-4A6B-BFA2-62415245E612@.microsoft.com...
> HI all,
> what is best way to move msdb to new loctaion (from F to E drive)on the
> same system in sql server2000?
> Shall I use restore command instead of attaching and detaching...
> Thanks in advance..
> Suchi
>
what is best way to move msdb to new loctaion (from F to E drive)on the
same system in sql server2000?
Shall I use restore command instead of attaching and detaching...
Thanks in advance..
Suchi
I believe that KB 224071 has explicit instructions for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Suchi" <Suchi@.discussions.microsoft.com> wrote in message
news:F096E1C9-CDDF-4A6B-BFA2-62415245E612@.microsoft.com...
> HI all,
> what is best way to move msdb to new loctaion (from F to E drive)on the
> same system in sql server2000?
> Shall I use restore command instead of attaching and detaching...
> Thanks in advance..
> Suchi
>
Subscribe to:
Posts (Atom)