Minimum components required to create 2005 database/tables programmatically

I want to know what are the minimum SQL Server 2005 tools required to perform the following task, and how do I install them:

1. I have a server with SQLS 2005 (and all of its management components) installed. Let's call this Server A. I want to create a database and tables in an instance on this machine.

2. I have another machine (Workstation B) on the same domain from which I want to programmatically create the database on Server A with legacy code that uses SQL-DMO.

What are the minimum components (i.e. SQLDMO for 2005?) I need to install on Workstation B and how/where are they available/packaged? I know that SMO is the replacement for SQLDMO, but we're not ready to upgrade to it yet and we still want to create databases on the 2005 instance.

Thanks in advance,

jd

You just have to install SQLDMO for SQL 2005. It is available as a separate download as part of SQL Server 2005 Feature Pack.

You can get it from here:

http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Regards,

Minimum components required to create 2005 database/tables programmatically

I want to know what are the minimum SQL Server 2005 tools required to perform the following task, and how do I install them:

1. I have a server with SQLS 2005 (and all of its management components) installed. Let's call this Server A. I want to create a database and tables in an instance on this machine.

2. I have another machine (Workstation B) on the same domain from which I want to programmatically create the database on Server A with legacy code that uses SQL-DMO.

What are the minimum components (i.e. SQLDMO for 2005?) I need to install on Workstation B and how/where are they available/packaged? I know that SMO is the replacement for SQLDMO, but we're not ready to upgrade to it yet and we still want to create databases on the 2005 instance.

Thanks in advance,

jd

You just have to install SQLDMO for SQL 2005. It is available as a separate download as part of SQL Server 2005 Feature Pack.

You can get it from here:

http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Regards,

Migration Tools For 2005 Express

Hi everyone

Does anyone know or has anyone heard of any migration tools which
are/might be available for converting SQL Server 2000 databases to SQL
Server 2005 Express?

I'm guessing it is probably a bit early but it was worth a shot!
Thanks

Dave[posted and mailed, please reply in news]

Bungle (dave@.court-technologies.com) writes:
> Does anyone know or has anyone heard of any migration tools which
> are/might be available for converting SQL Server 2000 databases to SQL
> Server 2005 Express?
> I'm guessing it is probably a bit early but it was worth a shot!

Well, I know of one, which is currently in beta. It's called SQL Server
2005.

You can simply attach your SQL 2000 databases to SQL 2005, and they
will be converted to SQL 2005. The same if you restore a backup from
SQL 2005. They will be left in compatibility mode 80, though.

Will the code run right away on SQL 2005? Well, it depends a little.
If you want to move on to compatibility level 90, there are a few
things to check:

o If you use index/lock hints, they must now be preceeded by WITH:
SELECT * FROM tbl WITH (INDEX = pk_tbl)
There is an exception for one-word hints, though.
o Old-style outer-joins *= may not work. (They do in the current
beta, but I think I saw something that it will change. They are
an abomination, so change them anyway.)
o There might be more, this is what I recall here and now.

Even if you stay on level 80, there are issues to look out for:

o SQL 2000 permitted for some incorrect syntax:
SELECT col FROM tbl ORDER BY crap.col
That is, in ORDER BY you could use non-existing aliases. There
were also some other funny things, that SQL 2005 now traps.
o If you make direct access to metadata in stored procedures
executed by plain users - system tables or INFORMATION_SCHEMA
does not matter - beware that users now by default does not
have access to metadata, if they don't have access to the
object itself.

And then of course, there is always the risk that a query executed
fine, now suddenly takes very long time, because the optimizer finds
another plan.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Migration Tools

Can somebody suggest me migration tools for DB2 to SQL Server?
Thanks
Prashanttry this perhaps:

http://www.swissql.com/products/db2-to-sqlserver/db2-to-sql-server.html

Bill

Migration from Access to Sql Server

Hi, I import my tables from Access to SQl Server 2000
actually MSDE with the SQL server tools.

Is there a way to have the same table name as in access
because in SQl server it seems I have to call my
tables that way : testdb.dbo.po instead of just po in VB access.
That means changing all my Querys :(

Also I installed sql server on 1 PC (WinXp Pro) on my network and install the client
tools on another PC (Win98) but how can I access SQL Server from that PC?
When I'm in VB and do a connection with the ADO object I don't get
any server listed in it??
My connection string use on my local PC with server on it is working fine.

StrSqlSrv = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _
"Persist Security Info=False;Initial Catalog=imdedi;" & _
"Data Source=" & servername

Also Is it possible to package (With VB package) a program using MSDE so that it will
install MSDE and create all tables on the client PC?

Can DAO connects to sql server?

Thank you. I know... alot of questions :)> That means changing all my Querys :(

no it doesn't. try it. you can use

databasename.username.tablename

or just

tablename|||Hi, this is my connections that work fine with ADO
The only thing I do is changing the ConnectionString to my Sql Server
To make it work I have to use the .dbo thing....
This works ->> testdb.dbo.company

company.ConnectionString = StrSqlSrv
company.RecordSource = "SELECT compno,compname,telno FROM company ORDER BY compno;"

company.Refresh

Here is the error I get
A message box display Invalif Object Name company
When I click OK then
a run-time error"
(80040e37) Method 'Refresh' of Object 'IAdodc' failed|||Hi, I was able to access my tables without the .dbo
I was missing a user...