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 Instances

Hello everyone. After finally getting MSDE installed, I
am having trouble with instances. At bootup the instance
that is loading is the wrong one, and is not working. The
instance that is loading is just "computername," and I
need "computername\instance" to load. I have checked the
registry for the other instance and it is not there. The
only place I can find this instance is when I open the SQL
Server Service Manager and click the drop down menu for
server. When I select the "computername\instance" from
the drop down menu everything works fine, it is just
initially it loads a defective instance. Anyone have any
ideas?
Thanks,
Chris
hi Chris,
"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
news:010701c4ac9d$fa3d49a0$a501280a@.phx.gbl
> Hello everyone. After finally getting MSDE installed, I
> am having trouble with instances. At bootup the instance
> that is loading is the wrong one, and is not working. The
> instance that is loading is just "computername," and I
> need "computername\instance" to load. I have checked the
> registry for the other instance and it is not there. The
> only place I can find this instance is when I open the SQL
> Server Service Manager and click the drop down menu for
> server. When I select the "computername\instance" from
> the drop down menu everything works fine, it is just
> initially it loads a defective instance. Anyone have any
> ideas?
Just a question... to understand...
you do have 2 MSDE instances installed...
a default instance and a named instance... please verify that both (or the
instance you are interestd in) services are set to start at bootstrap,
inspecting the Windows services manager (control panel->administrative
tools->services).. startup has to be "Automatic"...
why the default instance is not working?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi, and thank you for the reply. Sorry that I did not
make this more clear to begin with. No, I do not have two
instances installed, and I don't want two instances
installed. I guess somewhere in the middle of all the
trouble I had installing MSDE it created some kind of
bogus instance. All the readings I have read say that a
default instance in the registry will be located under
MSSQL Server and a named instance will be under Microsoft
SQL Server. I have deleted the MSSQL Server key and then
everything works fine until I reboot, then the key is re-
created. I can log off and back on after the key is
deleted and it works like it is supposed to.
When I open SVRNETCN.exe it says that I have two instances
installed:
1.) computername
2.) computername\instancename
I cannot find a way to get rid of "computername" and that
is the way that it is loading by default.
Let me know if you need more info and I hope I made it a
little more clear.
Thanks,
Chris[vbcol=seagreen]
>--Original Message--
>hi Chris,
>"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
>news:010701c4ac9d$fa3d49a0$a501280a@.phx.gbl
instance[vbcol=seagreen]
The[vbcol=seagreen]
the[vbcol=seagreen]
The[vbcol=seagreen]
SQL[vbcol=seagreen]
any
>Just a question... to understand...
>you do have 2 MSDE instances installed...
>a default instance and a named instance... please verify
that both (or the
>instance you are interestd in) services are set to start
at bootstrap,
>inspecting the Windows services manager (control panel-
>administrative
>tools->services).. startup has to be "Automatic"...
>why the default instance is not working?
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
|||hi Chris,
"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
news:089801c4ad48$ccdfdc10$a501280a@.phx.gbl
> Hi, and thank you for the reply. Sorry that I did not
> make this more clear to begin with. No, I do not have two
> instances installed, and I don't want two instances
> installed. I guess somewhere in the middle of all the
> trouble I had installing MSDE it created some kind of
> bogus instance. All the readings I have read say that a
> default instance in the registry will be located under
> MSSQL Server and a named instance will be under Microsoft
> SQL Server. I have deleted the MSSQL Server key and then
> everything works fine until I reboot, then the key is re-
> created. I can log off and back on after the key is
> deleted and it works like it is supposed to.
> When I open SVRNETCN.exe it says that I have two instances
> installed:
> 1.) computername
> 2.) computername\instancename
> I cannot find a way to get rid of "computername" and that
> is the way that it is loading by default.
> Let me know if you need more info and I hope I made it a
> little more clear.
>
ok... you do have 2 MSDE instances installed =;-D
a default instance, and a named instance named "instancename"...
and both of them shoul'd run at startup as this is the default setting
(please verify checking the services management tool)
and please do not delete registy keys that easy, becouse, as someone
elsewhere stated:
>"And by the way, editing the registry is extremely dangerous and I'm not
>responsible if you make a mistake and your hair is sure to fall out and you
>will catch pneumonia blah blah blah..." =:-)
so SQL Server Service Manager should list both instances, and both should be
running...
if you want to remove an MSDE instance, you should find an entry in the
Add/Remove programs applet, and please use that...
if you want to "manually" remove an MSDE instance,
http://support.microsoft.com/default...;EN-US;Q290991 Knowledge
Base article explains exactely the tasks to be performed as
http://support.microsoft.com/default...b;en-us;320873 does...
the second article uses a tool from the Platform SDK, Msizap.exe, which can
clear the Windows Installer entries too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE install

Dear Everybody,
When i am installing MSDE 2000 Release A on Windows XP Professional System.
It gives me Error "Invalid Instance Name".
What I done wrong please help me.
Ashok
hi,
Ashok wrote:
> Dear Everybody,
> When i am installing MSDE 2000 Release A on Windows XP Professional
> System. It gives me Error "Invalid Instance Name".
>
can you please provide the command line you passed to the setup.exe boostrap
installer?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 BLANKSAPWD=1
Here the instance name is NetSDK.
Once you are instlled successful with this instance name NetSDK, if you want
to install again with the same instance name, you need to remove instance.
"Ashok" wrote:

> Dear Everybody,
> When i am installing MSDE 2000 Release A on Windows XP Professional System.
> It gives me Error "Invalid Instance Name".
> What I done wrong please help me.
> Ashok
>
>

MSDE from Hoster installed

Hello
my DEd win 2003 server, uses MSDE
all is ok, the server run, and can create from script Db
but if i want login or create connection MSDE say wrong pass
i never change the pass or other
i have the server complet reinstalled from hoster image
what i doing wrong ?
hi,
MS News wrote:
> Hello
> my DEd win 2003 server, uses MSDE
> all is ok, the server run, and can create from script Db
> but if i want login or create connection MSDE say wrong pass
> i never change the pass or other
> i have the server complet reinstalled from hoster image
> what i doing wrong ?
assuming you are trying to connect using the standard SQL Server
authentication with the "sa" login and you can't remember it's pasword, you
can login using integrated security (the Windows authentication) using a
local admin member and set the "sa" password to whatever you want via the
system stored procedure sp_password,
http://msdn.microsoft.com/library/de...a-pz_5x44.asp,
in the form
EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
as all local admins members are automatically members of the
BUILTIN\Administrators login group in MSDE too, with sysadmins privileges...
connect via oSql.exe providing the -E parameter to specify integrated
security..
c:\..\>osql.exe -E -S(local)\InstanceName
1>EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
2>GO
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hey thats realy works !
thanks!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> schrieb im Newsbeitrag
news:3s11vbFlebp5U1@.individual.net...
> hi,
> MS News wrote:
> assuming you are trying to connect using the standard SQL Server
> authentication with the "sa" login and you can't remember it's pasword,
> you can login using integrated security (the Windows authentication) using
> a local admin member and set the "sa" password to whatever you want via
> the system stored procedure sp_password,
> http://msdn.microsoft.com/library/de...a-pz_5x44.asp,
> in the form
> EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
> as all local admins members are automatically members of the
> BUILTIN\Administrators login group in MSDE too, with sysadmins
> privileges...
> connect via oSql.exe providing the -E parameter to specify integrated
> security..
> c:\..\>osql.exe -E -S(local)\InstanceName
> 1>EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
> 2>GO
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>