Copy diagram from one MSSQL db to another

Hallo,
The subj actually says it all. I have developed the database locally, and
added a nicley formatted diagram to it, and would like to spare the
possibility to remake it once again on another database that has exactly the
same structure. So, there must be some way to copy the diagram from here to
there. I'd appreciate if someone could hint me how that could be possible to
achieve.
Thank you,
-- PavilsThe following article explains how to do it:
HOW TO: Move a Database Diagram
http://support.microsoft.com/?id=320125
-Sue
On Tue, 2 Mar 2004 16:31:13 +0200, "Pavils Jurjans"
<pavils@.mailbox.riga.lv> wrote:

>Hallo,
>The subj actually says it all. I have developed the database locally, and
>added a nicley formatted diagram to it, and would like to spare the
>possibility to remake it once again on another database that has exactly th
e
>same structure. So, there must be some way to copy the diagram from here to
>there. I'd appreciate if someone could hint me how that could be possible t
o
>achieve.
>Thank you,
>-- Pavils
>|||Thanks, that works well. Luckily, I have only one diag to copy and the
destination database does not contain any diagrams. There could be
complications using this copy *.* approach on some finer cases.
-- Pavils
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:s279401gpnvhr8892a3s1gq7rsqoi4rnpl@.
4ax.com...
> The following article explains how to do it:
> HOW TO: Move a Database Diagram
> http://support.microsoft.com/?id=320125
> -Sue
> On Tue, 2 Mar 2004 16:31:13 +0200, "Pavils Jurjans"
> <pavils@.mailbox.riga.lv> wrote:
>
the
to
to
>sqlsql

Copy diagram from one MSSQL db to another

Hallo,
The subj actually says it all. I have developed the database locally, and
added a nicley formatted diagram to it, and would like to spare the
possibility to remake it once again on another database that has exactly the
same structure. So, there must be some way to copy the diagram from here to
there. I'd appreciate if someone could hint me how that could be possible to
achieve.
Thank you,
-- PavilsThe following article explains how to do it:
HOW TO: Move a Database Diagram
http://support.microsoft.com/?id=320125
-Sue
On Tue, 2 Mar 2004 16:31:13 +0200, "Pavils Jurjans"
<pavils@.mailbox.riga.lv> wrote:
>Hallo,
>The subj actually says it all. I have developed the database locally, and
>added a nicley formatted diagram to it, and would like to spare the
>possibility to remake it once again on another database that has exactly the
>same structure. So, there must be some way to copy the diagram from here to
>there. I'd appreciate if someone could hint me how that could be possible to
>achieve.
>Thank you,
>-- Pavils
>|||Thanks, that works well. Luckily, I have only one diag to copy and the
destination database does not contain any diagrams. There could be
complications using this copy *.* approach on some finer cases.
-- Pavils
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:s279401gpnvhr8892a3s1gq7rsqoi4rnpl@.4ax.com...
> The following article explains how to do it:
> HOW TO: Move a Database Diagram
> http://support.microsoft.com/?id=320125
> -Sue
> On Tue, 2 Mar 2004 16:31:13 +0200, "Pavils Jurjans"
> <pavils@.mailbox.riga.lv> wrote:
> >Hallo,
> >
> >The subj actually says it all. I have developed the database locally, and
> >added a nicley formatted diagram to it, and would like to spare the
> >possibility to remake it once again on another database that has exactly
the
> >same structure. So, there must be some way to copy the diagram from here
to
> >there. I'd appreciate if someone could hint me how that could be possible
to
> >achieve.
> >
> >Thank you,
> >
> >-- Pavils
> >
>

Copy DB to a different Machine

Hi,

I have developed an application using SQl Server 2000.

I want to transfer the database to my new server. I want all the tables and datas to be transferred.

I am new to this application. So i am not able to get mysel started. Can someone help me in this problem.

My database is large. It has stored procedures, database diagrams.

Any help in this regard would be highly appreciated.

Thanks,
-sriramFin MS Sql Server on your Programs menu. Choose 'Import/Export' data > next. The following Dialogue is the From dialogue. Choose the Databse you want to copy and press next. In the 'To' dialogue, enter the IP/URL to the remote SQL Server. In the Dropdown list, choose '<New>' and name your Database - press OK. I nteh next dialogue, choose 'Copy objects and data between SQL Server databases'. Click Next 3 times and then End. Now your Database and data will be copied to your new Server.|||I prefer doing a full backup and then restoring the backup on the new machine. I find it quicker that way. This way your DB Diagrams will survive too.|||i agree with the full backup technique.

the only time i "object copy" between db's is to keep my local DB in sync with a shared Development DB and 2 other developers.|||Hi,

Thanks for replying.

How can i do a full backup. I am not able to backup and transfer to the new machine.

So can you help me??
thanks,
-sriram|||if you go to C:\Program Files\Microsoft SQL Server\MSSQL\Data
find your db files ...( 2- the db file and the log file)

copy them over to the new machine in the same data folder...and "attach" the db...

** remember to "Stop" the sql server before you do this...

hth|||I'm working on a project with 3 other people whom are using MSDE for the DB. Is there a function similar to 'attach db' that can be used with MSDE. Our computers are not networked, so we will only be able to pass the database file around.

Thanks in advance!

converting sql 2000 script to sql 7. gurus... please help!

We have a customer who got their site developed somewhere else. Well,
this host sent me all of the files along with a sql script to create
all the tables, sps, views, etc. I tried running it on our customer
sql box which is sql 7 and I got a number of errors. When I ran it on
my own machine which is developer 2000, it works fine. So, I've found
the main 3 lines that are causing the problems. Is there a way to
convert these lines to some syntax that is compatible with sql 7?

error 1: Incorrect syntax near the keyword 'ON'.
offending line: ON DELETE CASCADE ON UPDATE CASCADE

error 2: 'scope_identity' is not a recognized function name.
offending line: select @.access_id=scope_identity()

error 3: Incorrect syntax near the keyword 'level'.
offending line: select a.*,b.name level,c.username

I tried on error 3 doing "select a.*, b.name AS level, c.username" but
it still gave the same error.On 5 Aug 2004 06:06:49 -0700, geoff wrote:

>We have a customer who got their site developed somewhere else. Well,
>this host sent me all of the files along with a sql script to create
>all the tables, sps, views, etc. I tried running it on our customer
>sql box which is sql 7 and I got a number of errors. When I ran it on
>my own machine which is developer 2000, it works fine. So, I've found
>the main 3 lines that are causing the problems. Is there a way to
>convert these lines to some syntax that is compatible with sql 7?
>error 1: Incorrect syntax near the keyword 'ON'.
>offending line: ON DELETE CASCADE ON UPDATE CASCADE
>error 2: 'scope_identity' is not a recognized function name.
>offending line: select @.access_id=scope_identity()
>error 3: Incorrect syntax near the keyword 'level'.
>offending line: select a.*,b.name level,c.username
>I tried on error 3 doing "select a.*, b.name AS level, c.username" but
>it still gave the same error.

Hi Geoff,

Yes, it can be done.

re error 1: cascading foreign key constraints are new in SQL Server 2000.
To convert toi SQL Server 7.0, you'll have to remove the foreign key
("REFERENCES") constraint completely and replace it with your own checking
routines in triggers. I believe Books Online has some examples on this; if
not and you do need further assistance, let me know.

re error 2: I usually try to avoid identity so I'm not very experiences
with this, but I believe you can replace scope_identity() with either
IDENNT_CURRENT or @.@.IDENTITY. Do read the info in Books Online for
possible differences!

re error 3: level was a reserved keyword up to SQL Server 7.0. You either
have to usa another column alias, or enclose it in [brackets] or
"quotation marks": select a.*, b.name AS [level], c.username

Best, Hugo
--

(Remove _NO_ and _SPAM_ to get my e-mail address)

Converting MS-Access to MS-SQL Server

Hello all,
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
Jack
You can use the Access upsizing wizard (not recommended because it
creates a lot of junk of the server that you have to clean up). You
can also use DTS (or SSIS in SQLS 2005), but then you have to create
keys, indexes, etc. The other option you should seriously consider is
that this is a golden opportunity for rewriting the database schema to
optimize it for SQL Server. SQLS is not just a bigger Jet--it's a
completely different RDBMS. Migrating the data is the least of the
issues involved.
--Mary
On Sat, 21 Jan 2006 17:45:02 -0800, "Jack"
<Jack@.discussions.microsoft.com> wrote:

>Hello all,
>I got a application which is developed using VB6.0 as front end and
>MS-Access as backend. Now i would like to change the database from MS-Access
>to MS-SQLserver.
>How do I change the databse from MS-Access to MS-SQLServer?
>Regards
>Jack