MSDE Toolkit issue with windows 98

Hello,
My 1st attempt to install .Net framework, MSDE, my application and the databases during setup (using the MSDE deployment toolkit RC) works fine on windows xp. Now when I try to do the same for windows 98 SE machine, I am able to install .Net framweork an
d MSDE, but after that during the installation I get the following error message:
"An exception occured in the OnAfterInstall event handler of DBInstaller.CustomInstaller --> Unable to access service: Operating system does not support controlling a Windows service. A service can only be controlled on Windows NT, Windows 2000, or lat
er."
It's clear that when the setup tries to start the service to create the database etc it fails. Is this a known issue. I researched on web but couldn't find anything. Any ideas.
Thanks
dev
Any ideas..

MSDE Tookit thinks MSDE is not installed when it is.

I have multiple applications that will use the same named instance of MSDE. When I try to setup my second application using the MSDE Deployment addin it thinks that MSDE needs to be installed again. According to the flowchart it should bypass this and
just install my appliation. Any suggestions as to why my setup insists in needs to install another instance? My instance name is the same for all applications.
Thanks,
Bill
Bill in one of the previous messages someone from Microsoft mentioned that it is a known bug in the beta version of the toolkit. Hopefully it will be fixed.
goodluck
dev
|||Thanks for the info. Does anyone know when the full release will be out?
sql

MSDE to SQL2000

I would like to know if it's possible to transfer a database from MSDE to SQ
L 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000Yep. Just handle orphaned users afterwards. sp_change_users_logins or
http://dbmaint.com/SyncSqlLogins.asp.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C3EE7F95-750A-4559-AC34-3D1514DA5919@.microsoft.com...
> I would like to know if it's possible to transfer a database from MSDE to
SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000

MSDE to SQL2000

I would like to know if it's possible to transfer a database from MSDE to SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000Yep. Just handle orphaned users afterwards. sp_change_users_logins or
http://dbmaint.com/SyncSqlLogins.asp.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C3EE7F95-750A-4559-AC34-3D1514DA5919@.microsoft.com...
> I would like to know if it's possible to transfer a database from MSDE to
SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000

MSDE to SQL Server Express

Hi - I have an MSDE database running on my server - I'd like to port my asp.net 1.1 app to asp.net2, and make use of SQL 2005 Express.

How do I transfer my data from an MSDE database to SQL Server Express, keeping intact all of my unique ID fields, indexes, and SPs (I don't have any functions or views)

Thanks for any help,

Mark

Your best bet is either to "detach" it on the MSDE side, and "attach" it or "restore from backup" on the SQL 2005 side, or use DTS (data transformation services).

|||Hi - it's just SQL Server 2005 Express I have available, so no management tools are there to allow me to 'restore from backup' - I'm not sure it supports DTS either.

Has anyone else been able to do this?

Thanks, Mark|||

Even with SQL Express you should have the ability to detach the database. You need the Management studio installed to work with the Express server engine though. You can download it here.

http://www.microsoft.com/downloads/details.aspx?familyid=82afbd59-57a4-455e-a2d6-1d4c98d40f6e&displaylang=en

|||You don't have to detach from SQL Express if you are using a file based database (You are if you use the AttachDB attribute in your connect string). Just stop whatever application that uses it, and copy the mdb/ldb files to SQL Sever 2005 and attach.

MSDE to SQL Server 2005 Express

Howdy,
My company is setting up a new dedicated hosting server and we're debating
using the new SQL 2005 verse the MSDE. I'm not familiar with the new
version, so I have one big question:: Outside of the connection string, will
any syntax in my existing ASP.NET script/stored procs have to change to
support SQL 2005? Is the migration process painless?
I've searched MSDN but really can't find what I'm looking for.
Thanks,
David Lozzi
Web Applications Developer
dlozzi@.(remove-this)delphi-ts.comHello David,

> Outside of the
> connection string, will any syntax in my existing ASP.NET
> script/stored procs have to change to support SQL 2005?
Without specifics, its hard to say precisely. Some things change some, a
few a lot, most hardly at all. There's an upgrade advisor tool on the distri
bution
media and here [0] that I'd recommend starting with. It should catch a major
ity
of the changes needed with a minimum of effort.

> Is the
> migration process painless?
Again, that depends on what you've done in the past. I suspect not, but the
upgrade advisor will help you know more for sure.
[0]: http://www.microsoft.com/downloads/...&displaylang=en
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/

MSDE to SQL Server 2000 connection drops on XP Pro

Using MSDE 2000 SP3
Sql Server 2000 SP3
Win XP Pro SP1
Microsoft.Jet.OLEDB.4.0
We have recently upgraded field laptops from Windows 2000 to XP Pro. One of our applications which was developed with Visual C++ 6.0 and using MSDE will just drop it's connection to our consolidated Sql Server 2000. This works on Windows 2000 machines.
I have ran the profiler, monitored Sql Processes for locks, checked Event logs and I am unable to find any type of error. Our sync process just drops off. I am uncertain if it is MSDE, Sql Server or XP.
I even set the application's compatiability settings to Windows 2000 but still same result. I am uncertain as to how to do anymore troubleshooting.
Any ideas would be much appreciated.
Thanks,
Vannie Keever
SQL Server (including the MSDE edition) cannot close a connection by itself
except when shutting down. The client, the OS, or the network has to tell
SQL Server to drop the connection. Try a netmon trace to get more details.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
sql

MSDE to SQL Server

HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

MSDE to SQL Server

HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

MSDE to SQL 2000

What's the best way to get the data from the MSDE server
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>

MSDE to SQL 2000

What's the best way to get the data from the MSDE server
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:

> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>

MSDE to SQL

When scaling a system's back end from MSDE to the enterprise version of SQL what types of issues or concerns would you watch for?
Thanks
I am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/pr...o/overview.asp
Greg Jackson
PDX, Oregon
|||Miles,
MSDE IS SQL Server... You should have no problems at all...
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
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
sql

MSDE to SQL

When scaling a system's back end from MSDE to the enterprise version of SQL
what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/p...fo/overview.asp
Greg Jackson
PDX, Oregon|||Miles,
MSDE IS SQL Server... You should have no problems at all...
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
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks

MSDE to SQL

When scaling a system's back end from MSDE to the enterprise version of SQL what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/productinfo/overview.asp
Greg Jackson
PDX, Oregon|||i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not se the SQL server.
My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the domain
"Jaxon" wrote:
> I am sure there are tons of white papers on this, but I dont suspect that
> you'll experience any huge hurdles.
> MSDE is essentially a throttled down version of the SQL Server Engine.
> "Because it is fully compatible with other editions of SQL Server,
> developers can easily target both SQL Server and MSDE 2000 with the same
> core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> Server if an application grows beyond the storage and scalability limits of
> MSDE 2000."
>
> http://www.microsoft.com/sql/msde/productinfo/overview.asp
>
>
> Greg Jackson
> PDX, Oregon
>
>|||MSDE doesn't have network access enabled by default. Enable using svrnetcn.exe.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Visual FoxPro programmer" <VisualFoxProprogrammer@.discussions.microsoft.com> wrote in message
news:927CFF5D-751E-4040-AF0D-B3896E64D68C@.microsoft.com...
> i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a
domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not
se the SQL server.
> My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the
domain
>
> "Jaxon" wrote:
> > I am sure there are tons of white papers on this, but I dont suspect that
> > you'll experience any huge hurdles.
> >
> > MSDE is essentially a throttled down version of the SQL Server Engine.
> >
> > "Because it is fully compatible with other editions of SQL Server,
> > developers can easily target both SQL Server and MSDE 2000 with the same
> > core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> > Server if an application grows beyond the storage and scalability limits of
> > MSDE 2000."
> >
> >
> > http://www.microsoft.com/sql/msde/productinfo/overview.asp
> >
> >
> >
> >
> > Greg Jackson
> > PDX, Oregon
> >
> >
> >|||Miles,
MSDE IS SQL Server... You should have no problems at all...
--
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
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks

MSDE to MSDE replication with T-SQL/sp?

How can we replicate data in one MSDE to the other MSDE without having to
pay for MSSQL2000 full version to use the sql enterprise manager?
It seems that Enterprise Manager or SQL-DMO based programs rely on
system-provided stored procedures to do replication. So why not run sp thru
osql?
Is is possible for a t-sql expert to create such an sp? I searched
Internet and found few resources about msde to msde replication.
hi,
"news.microsoft.com" <martinc@.hume-travel.com> ha scritto nel messaggio
news:u40hNYVWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> How can we replicate data in one MSDE to the other MSDE without having to
> pay for MSSQL2000 full version to use the sql enterprise manager?
> It seems that Enterprise Manager or SQL-DMO based programs rely on
> system-provided stored procedures to do replication. So why not run sp
thru
> osql?
> Is is possible for a t-sql expert to create such an sp? I searched
> Internet and found few resources about msde to msde replication.
>
yep... it's not very documented, but you can even use SQL-DMO replication
ActiveX controls
this is a great article,
http://www.winnetmag.com/Article/Art...079/39079.html , but only for
SQL Server Magazine subscribers...
http://www.compman.co.uk/cgi-win/browse.exe?ref=552118 has an entire
(little) chapter about replication and SQL-DMO... this is the best book
about SQL-DMO ever released...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||With the developers edition of SQL Server you can setup replication between
test systems, then script out the the entire replication setup. The script
can then be used as a template for setting up future replications.
Jim
"news.microsoft.com" <martinc@.hume-travel.com> wrote in message
news:u40hNYVWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> How can we replicate data in one MSDE to the other MSDE without having to
> pay for MSSQL2000 full version to use the sql enterprise manager?
> It seems that Enterprise Manager or SQL-DMO based programs rely on
> system-provided stored procedures to do replication. So why not run sp
thru
> osql?
> Is is possible for a t-sql expert to create such an sp? I searched
> Internet and found few resources about msde to msde replication.
>

MSDE to MSDE Replication

Hi,
I would like to know if I can do Replication from a MSDE 2000 to another
MSDE 2000 system (one way).
All I need to do is Sync Server database changes on to a Workstation
database(Real-Time).
Let me give an example.
We have Server and Workstation product. Our Server will have a LiveConfig db
and each workstation will have a localLookupDB(basically same as
LiveConfig). I know If I have the Server as Std SQL Server 2000 I can use
Replication to propogate changes onto workstation what if the Server is
MSDE?
Are there any ways to Replicate data From a Server database onto Workstation
database (Real-Time).
Your advice is appreciated.
Thanks
Arun
You can use merge replication for msde to msde. You can use snapshot,
transactional or merge replication to MSDE from SQL Server 2000. Your
latency may be in the order of minutes.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Arun Kumar" <arunpv@.hotmail.com> wrote in message
news:ObTva%232pFHA.748@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I would like to know if I can do Replication from a MSDE 2000 to another
> MSDE 2000 system (one way).
> All I need to do is Sync Server database changes on to a Workstation
> database(Real-Time).
> Let me give an example.
> We have Server and Workstation product. Our Server will have a LiveConfig
db
> and each workstation will have a localLookupDB(basically same as
> LiveConfig). I know If I have the Server as Std SQL Server 2000 I can use
> Replication to propogate changes onto workstation what if the Server is
> MSDE?
> Are there any ways to Replicate data From a Server database onto
Workstation
> database (Real-Time).
> Your advice is appreciated.
> Thanks
> Arun
>
|||Thanks for the reply.
If I do use merge replication from MSDE to MSDE what are the drawbacks?
Are there any other ways you can suggest for replicating data from one
server to another? (or one to many MSDE)
Thanks
Arun
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23KmSQu3pFHA.820@.TK2MSFTNGP09.phx.gbl...
> You can use merge replication for msde to msde. You can use snapshot,
> transactional or merge replication to MSDE from SQL Server 2000. Your
> latency may be in the order of minutes.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Arun Kumar" <arunpv@.hotmail.com> wrote in message
> news:ObTva%232pFHA.748@.TK2MSFTNGP12.phx.gbl...
> db
> Workstation
>

MSDE to MS SQL restore

I have a MSDE database that I am trying to restore into MS SQL 7.

I am running the following restore from Query Analyzer;

RESTORE DATABASE name
FROM DISK = 'c:\mssql7\backup\name_backup'

I am getting the following error

Server: Msg 3624, Level 20, State 1, Line 1

Location: upgraddb.cpp:214
Expression: tableIndex < ARRAY_LEN (upgradeMap)
SPID: 7
Process ID: 748

Connection Broken

Is what I'm trying to do impossible or something I'm doing wrong. Any help would be much appreciatedI don't know if this will help.

I had the same problem where I wanted to resore a MSDE database to SQL Server 2000. There was just no way. So I then used DTS to just transfer the Database to the SQL Server 2000.|||Originally posted by machado
I don't know if this will help.

I had the same problem where I wanted to resore a MSDE database to SQL Server 2000. There was just no way. So I then used DTS to just transfer the Database to the SQL Server 2000.

I only have the backup file, I don't actually posess MSDE so as far as I know I can't actually connect to anything for a dts to work|||MSDE can be distributed free and is included on the MS Office Prof. 2000/XP CDs.
What I would suggest is installing MSDE on any other machine on your network and restoring the database to MSDE and then transfering the databse using DTS.|||Originally posted by machado
MSDE can be distributed free and is included on the MS Office Prof. 2000/XP CDs.
What I would suggest is installing MSDE on any other machine on your network and restoring the database to MSDE and then transfering the databse using DTS.

So it is :)

Thanks, I'm installing it nowsql

MSDE timeout with wireless network enabled

Hi,
I have local MSDE installed on my laptop. When I am physically
connected to our network I can connect through my ODBC application
without issue.
However, when I have wireless networking enabled the first time I try to
connect I get a timeout. But, I'm able to immediately connect after
that initial timeout without a problem. This only occurs when wireless
networking is enabled, as the timeout does not occur with a physical LAN
connection.
I have the following installation:
MDAC SDK 2.8
MSDE 8.00.761
XP SP2
VS.NET 7.1
Any help would be greatly appreciated.
Thanks,
John
I am having a similar issue using SQL querries over a wireless connection.
Is there a technology that is better suited for wireless? Say .net?
Thanks in advance...
"JohnD" wrote:

> Hi,
> I have local MSDE installed on my laptop. When I am physically
> connected to our network I can connect through my ODBC application
> without issue.
> However, when I have wireless networking enabled the first time I try to
> connect I get a timeout. But, I'm able to immediately connect after
> that initial timeout without a problem. This only occurs when wireless
> networking is enabled, as the timeout does not occur with a physical LAN
> connection.
> I have the following installation:
> MDAC SDK 2.8
> MSDE 8.00.761
> XP SP2
> VS.NET 7.1
> Any help would be greatly appreciated.
> Thanks,
> John
>
|||Do you have the same problem if you use an IP address instead of the MSDE
instance name? Perhaps you're having a name resolution problem?
Jim
"Chris James" <Chris James@.discussions.microsoft.com> wrote in message
news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...[vbcol=seagreen]
>I am having a similar issue using SQL querries over a wireless connection.
> Is there a technology that is better suited for wireless? Say .net?
> Thanks in advance...
> "JohnD" wrote:
|||Thanks for the post Jim, Ive tried it using IP and Instance name... The
funny thing is that not all wireless installations have this issue, I have
two sites across the street and down about 1/4 mile. One site with approx
250' between wireless access point and client work fairly reliably, the other
is only 50' apart and they fail all the time. I wonder if its the
application making too many querries and boging down the wireless. Both
sites are using identical equipment as well.
"Jim Young" wrote:

> Do you have the same problem if you use an IP address instead of the MSDE
> instance name? Perhaps you're having a name resolution problem?
> Jim
> "Chris James" <Chris James@.discussions.microsoft.com> wrote in message
> news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...
>
>

MSDE Text datatype - unable to store more than 900 characters. (msde + visual studio 2003)

Hello,
I'm not sure if it's the setup I did wrong, but I can't seem to get mytext datatype in my database to store more than 900 characters. I'm trying to setup a news database for my website, which will populatethe information into a datagrid. To test, I manually added a newsitem in the database through the visual studio 2003 gui. Iimmediately noticed a problem as the I was getting an error after along news item saying:
"The value you entered is not consistent with the data type or length of the column, or over grid buffer limit."
I couldn't find anthing to set the buffer limit and the datatype is"text" filled with simple text in the column. As a further test,Isimply entered 12334567890123... up to 900 characters and stillrecevied the error.
I would appreciate someone leading me in the right direction on this one.
Thanks a lot.
I think may be your create table statement was not executed correctly because text can grow it is not table space based SQL Server creates an Arithmetic pointer to the file. Try the link below see if you can download the eval edition of the SQL Server. Or you could drop the table and recreate it and test again. Hope this helps.
http://www.microsoft.com/sql/evaluation/trial/default.mspx

MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack yet) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to make the MSDE server listen on TCP/IP port 1433. But it will not listen on that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.