Help with agent job to import from ODBC?

SQL Server 2005 Standard Edition.
Using wizard, no problem to use SQL to import from ODBC data source. Saved
the DTS job to an SSIS package, unable to use with agent scheduler.
Error is DTS_E_PRODUCTLEVELTOLOW.
Please help why is this happening?Frank
Do you want to move jobs to SQL Server 2005?
"Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
> SQL Server 2005 Standard Edition.
> Using wizard, no problem to use SQL to import from ODBC data source. Saved
> the DTS job to an SSIS package, unable to use with agent scheduler.
> Error is DTS_E_PRODUCTLEVELTOLOW.
> Please help why is this happening?|||I just want them to run as scheduled without operator intervention. I don't
really care how it do it.
Does that make sense?
thanks in advance..
"Uri Dimant" wrote:
> Frank
> Do you want to move jobs to SQL Server 2005?
>
> "Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
> message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
> > SQL Server 2005 Standard Edition.
> >
> > Using wizard, no problem to use SQL to import from ODBC data source. Saved
> > the DTS job to an SSIS package, unable to use with agent scheduler.
> >
> > Error is DTS_E_PRODUCTLEVELTOLOW.
> >
> > Please help why is this happening?
>
>

Help with agent job to import from ODBC?

SQL Server 2005 Standard Edition.
Using wizard, no problem to use SQL to import from ODBC data source. Saved
the DTS job to an SSIS package, unable to use with agent scheduler.
Error is DTS_E_PRODUCTLEVELTOLOW.
Please help why is this happening?
Frank
Do you want to move jobs to SQL Server 2005?
"Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
> SQL Server 2005 Standard Edition.
> Using wizard, no problem to use SQL to import from ODBC data source. Saved
> the DTS job to an SSIS package, unable to use with agent scheduler.
> Error is DTS_E_PRODUCTLEVELTOLOW.
> Please help why is this happening?
|||I just want them to run as scheduled without operator intervention. I don't
really care how it do it.
Does that make sense?
thanks in advance..
"Uri Dimant" wrote:

> Frank
> Do you want to move jobs to SQL Server 2005?
>
> "Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
> message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
>
>

Help w/Templates

I have windows xp home edition. I downloaded some templates (clip art) from Microsoft Office but when I go to open them it says it doesn't know wher/how/who they were made by. It says they are bmf?
Can I use the templates in Microsoft office? thank you
Vanessa
"Vanessa" <anonymous@.discussions.microsoft.com> wrote in message
news:8B78E492-2EB8-4DEB-8858-8723E309B866@.microsoft.com...
> I have windows xp home edition. I downloaded some templates (clip art)
from Microsoft Office but when I go to open them it says it doesn't know
wher/how/who they were made by. It says they are bmf?
> Can I use the templates in Microsoft office? thank you
Try the Office newsgroups...
Bryant

Help w/SQL Mobile to SQL Compact Edition

Hello

We currently use SQL Mobile and SQL Server 2005. We depend heavily on merge replication for data to the field handheld devices.

We are going to be starting some new projects and I was wondering about moving to SQL Compact Edition as the first step to migrating all of our applications.

I am concerned, however, about the server side and replication. If we simply deploy SQL Compact Edition will there need to be any changes to the server for replication?

Thanks,

- will

Yes, that should be the case. SQL CE is basiclay just a newer version of SQL Mobile.

|||

Are you saying that there isn't anything on the server that I need to do...or that I will need to install and test the newer versions of the server tools?

|||The server tools have been update slightly, so you should use these. Download from: http://www.microsoft.com/downloads/details.aspx?FamilyID=4e45f676-e69a-4f7f-a016-c1585acf4310&displaylang=en

Help w/SQL Mobile to SQL Compact Edition

Hello

We currently use SQL Mobile and SQL Server 2005. We depend heavily on merge replication for data to the field handheld devices.

We are going to be starting some new projects and I was wondering about moving to SQL Compact Edition as the first step to migrating all of our applications.

I am concerned, however, about the server side and replication. If we simply deploy SQL Compact Edition will there need to be any changes to the server for replication?

Thanks,

- will

Yes, that should be the case. SQL CE is basiclay just a newer version of SQL Mobile.

|||

Are you saying that there isn't anything on the server that I need to do...or that I will need to install and test the newer versions of the server tools?

|||The server tools have been update slightly, so you should use these. Download from: http://www.microsoft.com/downloads/details.aspx?FamilyID=4e45f676-e69a-4f7f-a016-c1585acf4310&displaylang=en

HELP using SQL Server 2005

I am using SQLServer2005 Express Edition in Visual Studio 2005. I uploaded the database to the server with the rest of the web files. When I try to insert data into a table, I receive the "error: 26 - Error Locating Server/Instance Specified" error message.

It is my belief that it is the connection string that is causing the problem. Currently the connection string looks like this:

Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\MYDATABASE.mdf;Integrated Security=True;User Instance=True

Is there a way using VS2005 to create a username and pass for the database? Then how do I set up a typical connection string that will work on a web server?

Desired connection string format would be something like:

Data Source=??serverIP??;UID=MYusername;PASSWORD=MYpassword;SERVER=?serverIP/NAME?

The question marks are in there because I am not 100% sure what would go in those properties. Any help is appreciated.

Thanks,
KJAK

Are you sure that the sqlserver is installed in the server ? When you use .mdf files is necessary that the server have the sql server installed.

A connection string that will work on a web server is something like this:

connectionString="Data Source=SERVERIP;Initial Catalog=DATABASENAE;Persist Security Info=True;User ID=USER;Password=PASSWORD"providerName="System.Data.SqlClient"

|||

SQLServer is installed on the server. The current connection string is provided from my development machine in the web.config file. I will try to adjust it to be similar to what you have posted.

I don't have full access to the server so I can't make any direct adjustments to SQLServer if that is needed. How can I create a username and password for the database using Visual Studio 2005?

|||

SQLServer is installed on the server

which version of sql server is installed? express? or sql 2005?

But whatever,based on my understanding, in neither case you can create sql user name and passwork through visual studio. The sql database is managed by database management tool thus you can only create/modify user name and psw through management studio.

I don't have full access to the server so I can't make any direct adjustments to SQLServer if that is needed.

and based on my understanding, i think you must have admin previlage if you want to create new sql user accounts.

Hope my suggestion helps

help upgrade!

hello to all!

i have a hx4700 with an aplication that uses a sdf database. my pocket as 2 edition ( not w mobile5). i want to upgrade that sdf to a database compact edition but when i execute that command:

upgrade.exe /s "aaa.sdf" /d "bbb.sdf" i have an error message:

upgrade database error.

what am i doing wrong or what have i missed?

i have choose the upgrade that is in the arm4 directory.

thkx!

I am not really sure whether I understood your question right. But upgrade exe is only for upgrading SQL CE 2.0 database to SQL CE 3.0 database. There is no update required from 3.0 to 3.1.

Thanks,

Laxmi

Help to verify ?

I do a SQL migration. Help to verify whether it's OK.
Old Server: SVR1, SQL Server Enterprise edition
New Server: SVR2, SQL Server Enterprise Edition
There are many user databases and linked server in SVR1,
it's inconvenient to copy database file and attach to new
server. And also need to create user account, etc. Because
all user database registeration info are stored in master
database, so I try to modify master database. Following is
the procedure:
1.At SVR1, set using SQL authentication, stop SQL server.
copy all system and user database to SVR2, save at
c:\olddata
2.At SVR2, attach master.mdf and mastlog.ldf in c:\olddata
as masternew.
3.In three table sysdatabases, sysaltfiles, sysdevices of
masternew database, modify old path to the real path
c:\sqldata.
4.At SVR2, stop all SQL service, copy all file from
c:\oldpath to c:\sqldata, select yes if need to confirm
file replace
5.At SVR2, start SQL Service, use SQL Query analyzer, run
following script:
exec sp_dropserver 'SVR1'
go
exec sp_addserver 'SVR2','local'
go
6.Open SQL Server Enterprise Manager, it seems all is ok.
Is there any problem to do like this? Or I need to do any
more? Your message to me is my pleasure.Hi
The following article describes how to transfer over to a new server
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546#2
If you followed the steps then there would be no need copy the master
database, but the following article details how to:
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b224071
Your process does not seem to transfer any jobs
John
"ronggui" <ronggui999@.hotmail.com> wrote in message
news:001601c34967$c1a43850$a601280a@.phx.gbl...
> I do a SQL migration. Help to verify whether it's OK.
> Old Server: SVR1, SQL Server Enterprise edition
> New Server: SVR2, SQL Server Enterprise Edition
> There are many user databases and linked server in SVR1,
> it's inconvenient to copy database file and attach to new
> server. And also need to create user account, etc. Because
> all user database registeration info are stored in master
> database, so I try to modify master database. Following is
> the procedure:
> 1.At SVR1, set using SQL authentication, stop SQL server.
> copy all system and user database to SVR2, save at
> c:\olddata
> 2.At SVR2, attach master.mdf and mastlog.ldf in c:\olddata
> as masternew.
> 3.In three table sysdatabases, sysaltfiles, sysdevices of
> masternew database, modify old path to the real path
> c:\sqldata.
> 4.At SVR2, stop all SQL service, copy all file from
> c:\oldpath to c:\sqldata, select yes if need to confirm
> file replace
> 5.At SVR2, start SQL Service, use SQL Query analyzer, run
> following script:
> exec sp_dropserver 'SVR1'
> go
> exec sp_addserver 'SVR2','local'
> go
> 6.Open SQL Server Enterprise Manager, it seems all is ok.
> Is there any problem to do like this? Or I need to do any
> more? Your message to me is my pleasure.
>|||Hi,
Because in new server SVR2, there is already a master
database. I want to change all the old paths in the master
database from old server SVR1, so I attached as masternew.
By the way, at old server SVR1 system and user databases
are saved in different path, I need changing path in
master, so it can work in new server SVR2.
After changing path, I stop SQL Server SVR2, and copy all
old files to exact location.
>--Original Message--
>You attached the master database as "Masternew". I
>thought the master database must be called "Master".
>I will only copy all the databases to the exact location
>in SVR2 including "Master", "Msdb" etc as SVR1.
>.
>|||Hi
The articles do show how to move the master database, you should follow that
procedure.
John
"ronggui" <ronggui999@.hotmail.com> wrote in message
news:040b01c349b0$cab4bca0$a301280a@.phx.gbl...
> Hi,
> Because in new server SVR2, there is already a master
> database. I want to change all the old paths in the master
> database from old server SVR1, so I attached as masternew.
> By the way, at old server SVR1 system and user databases
> are saved in different path, I need changing path in
> master, so it can work in new server SVR2.
> After changing path, I stop SQL Server SVR2, and copy all
> old files to exact location.
> >--Original Message--
> >You attached the master database as "Masternew". I
> >thought the master database must be called "Master".
> >
> >I will only copy all the databases to the exact location
> >in SVR2 including "Master", "Msdb" etc as SVR1.
> >.
> >

Help SP3a installation error

I have just installed a new Win2000 server, and loaded
SQL2000 Standard Edition. As soon as I try to install sp3a
I get the following error:
"Setup Initialization error.
Access is denied.
Source: D:\installs\SP3a-SQL2000\x86\setup\sqlspre.ini
Target: ...path\temp\setupsql.ini"
I am running the installation as administrator.| I have just installed a new Win2000 server, and loaded
| SQL2000 Standard Edition. As soon as I try to install sp3a
| I get the following error:
| "Setup Initialization error.
| Access is denied.
| Source: D:\installs\SP3a-SQL2000\x86\setup\sqlspre.ini
| Target: ...path\temp\setupsql.ini"
|
| I am running the installation as administrator.
--
Hi Sean,
Check c:\winnt\temp folder and see if setupsql.ini already exists. If it
does,
delete it. This should allow setupsql to complete successfully.
Hope this helps,
--
Eric Cárdenas
SQL Server support

Help Req: how to upgrade from MSDE to Standard Edition

I have Merge Publication with SQL Standard Edition publisher
and MSDE subscribers. Due to database size (1,8 GB) I'm preparing
to upgrade SQL Server subscribers from MSDE SP3a to Standard Edition.
Can I do this without breaking the subscription (i.e. simple upgrade),
or I have to unsubscribe , upgrade to SQL Standard Edition SP3a
and re-subscribe to publication.
What is the best practice ?
Any advice or link is appreciated.
Pagus
..
The best approach would be to backup the databases, upgrade, restore them,
and then do no sync (the subscriber already has the schema and data)
subscriptions.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pagus" <pagus@.writeme.com> wrote in message
news:85dfm05hhog0h9h42v54vu2c81f95nn5pq@.4ax.com...
> I have Merge Publication with SQL Standard Edition publisher
> and MSDE subscribers. Due to database size (1,8 GB) I'm preparing
> to upgrade SQL Server subscribers from MSDE SP3a to Standard Edition.
> Can I do this without breaking the subscription (i.e. simple upgrade),
> or I have to unsubscribe , upgrade to SQL Standard Edition SP3a
> and re-subscribe to publication.
> What is the best practice ?
> Any advice or link is appreciated.
> Pagus
> .
|||I did it and it works fine.
Thank you Hilary !
On Sat, 9 Oct 2004 22:33:42 -0400, "Hilary Cotter"
<hilary.cotter@.gmail.com> wrote:

>The best approach would be to backup the databases, upgrade, restore them,
>and then do no sync (the subscriber already has the schema and data)
>subscriptions.