Data not visible??

I recently imported some Access tables into SQL Server. I can go into enterprise manager and return all rows and the data is there.

I build an ASP page to edit the data. After the connection the data for the record is displayed in a form. For some reason some fields are not coming through?

Is this a problem when converting to SQL Server. It just doesn't make sense that the table in Enterprise manager says the field is populated but when I do a pull via ASP the data doesn't come through.

Does anyone know anything about this?

Any help or pointing in the right direction would be greatly appreciated.

Thanks,

JWExecute your query in Query Analyzer. Compare the results to those obtained through your ASP page.|||There is nothing special about the query. It's select all from the table but by the vaiable ID number that is passed.

See the weird thing is, is that it doesn't bomb out or anything and brings back some fields in the recordset but not all. But then I return all rows in query analyzer and the data for those fields is populated.|||Please post the ASP code that executes the query and displays the data from the recordset.|||<%
Set objConn = Server.CreateObject("ADODB.Connection")
objConn.ConnectionString = "DSN=golfinam;UID=golfinam;PWD=XXXXXX;DATABASE=XXXX XX"
objConn.Open
Set objRS = Server.CreateObject("ADODB.Recordset")
strSQL = "SELECT * FROM tbl_Courses where CourseID = " & request.querystring("CourseID")
objRS.Open strSQL, objConn%>
<% if ObjRS.eof then %><% else %>

'Then this is where the form is with each forms default set to a field,
<textarea rows="7" name="PTPDirections" cols="53"><%=objRS("PTPDirections")%></textarea>

<%End If%>
<%'Close the Recordset object
objRS.Close

'Delete the Recordset Object
Set objRS = Nothing

'Close the Connection object
objConn.Close

'Delete the Connection Object
Set objConn = Nothing
%>|||Is there a setting or something in the import that would cause it to act this way?

Data not showing for some users

Hi there,

Some users, when they select a table and try to "Return all rows" in Enterprise Manager, they get the word Binary instead of the data that should be there. The table has 4 columns, an ID column and three data columns. The ID field data is correct but the data in the other columns just show the word 'Binary'.

I got the user to connect to the database using the 'sa' login and the problem is still there. I can connect from my machine and see the data fine. Only one user is experiencing these problems.

The problem occurs with all the tables in the database. Any field that should have text data, e.g. nchar, nvarchar, etc., is showing 'Binary'. Fields that have numeric or date types show fine.

If the users runs a select query from Query Analyser, then the data appears fine.

Any help??This problem seems to have occured since i tried to install a SQLBase odbc driver. The data in the database is fine but Enterprise Manager seems to be corrupted.

Any help??

Data Import/export fails to start

While logged onto an SQL server through enterprise manager, when I select a
database, right click and select import or export nothing happens. No boxes
or errors appear.
If I try it through Tools|Data Transformation Services|Import - I get a MMC
error
Details are: AppName mmc.exe AppVer:5.1.2600.2180 Modname:sqldmo.dll
ModVer:2000.80.194.0 offset 002606e0
Clicking OK kills MMC
This functionality works if I connect using Remote Desktop.
Any Ideas?
Hi
Apply the same service pack on your client machine as you have on the
server, reboot and see if it still occurs. You don't have any SP's on the
client machine based on the build version of sqldmo.dll.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"TLuebke" <TLuebke@.discussions.microsoft.com> wrote in message
news:686D1C15-A11E-4A98-8949-8121E5B0496A@.microsoft.com...
> While logged onto an SQL server through enterprise manager, when I select
> a
> database, right click and select import or export nothing happens. No
> boxes
> or errors appear.
> If I try it through Tools|Data Transformation Services|Import - I get a
> MMC
> error
> Details are: AppName mmc.exe AppVer:5.1.2600.2180 Modname:sqldmo.dll
> ModVer:2000.80.194.0 offset 002606e0
> Clicking OK kills MMC
> This functionality works if I connect using Remote Desktop.
> Any Ideas?
>
|||Thanks Mike,
That did the trick.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Apply the same service pack on your client machine as you have on the
> server, reboot and see if it still occurs. You don't have any SP's on the
> client machine based on the build version of sqldmo.dll.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "TLuebke" <TLuebke@.discussions.microsoft.com> wrote in message
> news:686D1C15-A11E-4A98-8949-8121E5B0496A@.microsoft.com...
>
>

Data Import/export fails to start

While logged onto an SQL server through enterprise manager, when I select a
database, right click and select import or export nothing happens. No boxes
or errors appear.
If I try it through Tools|Data Transformation Services|Import - I get a MMC
error
Details are: AppName mmc.exe AppVer:5.1.2600.2180 Modname:sqldmo.dll
ModVer:2000.80.194.0 offset 002606e0
Clicking OK kills MMC
This functionality works if I connect using Remote Desktop.
Any Ideas?Hi
Apply the same service pack on your client machine as you have on the
server, reboot and see if it still occurs. You don't have any SP's on the
client machine based on the build version of sqldmo.dll.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"TLuebke" <TLuebke@.discussions.microsoft.com> wrote in message
news:686D1C15-A11E-4A98-8949-8121E5B0496A@.microsoft.com...
> While logged onto an SQL server through enterprise manager, when I select
> a
> database, right click and select import or export nothing happens. No
> boxes
> or errors appear.
> If I try it through Tools|Data Transformation Services|Import - I get a
> MMC
> error
> Details are: AppName mmc.exe AppVer:5.1.2600.2180 Modname:sqldmo.dll
> ModVer:2000.80.194.0 offset 002606e0
> Clicking OK kills MMC
> This functionality works if I connect using Remote Desktop.
> Any Ideas?
>|||Thanks Mike,
That did the trick.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Apply the same service pack on your client machine as you have on the
> server, reboot and see if it still occurs. You don't have any SP's on the
> client machine based on the build version of sqldmo.dll.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "TLuebke" <TLuebke@.discussions.microsoft.com> wrote in message
> news:686D1C15-A11E-4A98-8949-8121E5B0496A@.microsoft.com...
>
>

Data Import/export fails to start

While logged onto an SQL server through enterprise manager, when I select a
database, right click and select import or export nothing happens. No boxes
or errors appear.
If I try it through Tools|Data Transformation Services|Import - I get a MMC
error
Details are: AppName mmc.exe AppVer:5.1.2600.2180 Modname:sqldmo.dll
ModVer:2000.80.194.0 offset 002606e0
Clicking OK kills MMC
This functionality works if I connect using Remote Desktop.
Any Ideas?Hi
Apply the same service pack on your client machine as you have on the
server, reboot and see if it still occurs. You don't have any SP's on the
client machine based on the build version of sqldmo.dll.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"TLuebke" <TLuebke@.discussions.microsoft.com> wrote in message
news:686D1C15-A11E-4A98-8949-8121E5B0496A@.microsoft.com...
> While logged onto an SQL server through enterprise manager, when I select
> a
> database, right click and select import or export nothing happens. No
> boxes
> or errors appear.
> If I try it through Tools|Data Transformation Services|Import - I get a
> MMC
> error
> Details are: AppName mmc.exe AppVer:5.1.2600.2180 Modname:sqldmo.dll
> ModVer:2000.80.194.0 offset 002606e0
> Clicking OK kills MMC
> This functionality works if I connect using Remote Desktop.
> Any Ideas?
>|||Thanks Mike,
That did the trick.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Apply the same service pack on your client machine as you have on the
> server, reboot and see if it still occurs. You don't have any SP's on the
> client machine based on the build version of sqldmo.dll.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "TLuebke" <TLuebke@.discussions.microsoft.com> wrote in message
> news:686D1C15-A11E-4A98-8949-8121E5B0496A@.microsoft.com...
> > While logged onto an SQL server through enterprise manager, when I select
> > a
> > database, right click and select import or export nothing happens. No
> > boxes
> > or errors appear.
> >
> > If I try it through Tools|Data Transformation Services|Import - I get a
> > MMC
> > error
> > Details are: AppName mmc.exe AppVer:5.1.2600.2180 Modname:sqldmo.dll
> > ModVer:2000.80.194.0 offset 002606e0
> > Clicking OK kills MMC
> >
> > This functionality works if I connect using Remote Desktop.
> >
> > Any Ideas?
> >
>
>

Data handling capabilities of SQL Server 2000 Enterprise Edition

I am developing an intranet portal on Microsoft .NET platform and using
SQL Server 2000 Enterprise Edition as the database.
I would like to know the maximum size to which the database can grow to
in SQL Server as many tables in the database will have over 1 million
records with each row having images, documents stored in it.
The server housing SQL Server is Dell PowerEdge 2950 with single CPU
dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.In reality the size of the database is limited by your disk space.
According to BOL the database size can be up to 1,048,516 TB (depending
on the edition that you have). If you meant to ask at what size the
database's performance will not be good, then that depends on the
database's structure, the quality of the code that works with the
database, the number of concurrent users and other factors much more
then it depends on the database's size.
Adi
ram2811 wrote:
> I am developing an intranet portal on Microsoft .NET platform and using
> SQL Server 2000 Enterprise Edition as the database.
> I would like to know the maximum size to which the database can grow to
> in SQL Server as many tables in the database will have over 1 million
> records with each row having images, documents stored in it.
> The server housing SQL Server is Dell PowerEdge 2950 with single CPU
> dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.|||"ram2811" <ram2811@.gmail.com> wrote in message
news:1163533063.339418.203140@.i42g2000cwa.googlegroups.com...
>I am developing an intranet portal on Microsoft .NET platform and using
> SQL Server 2000 Enterprise Edition as the database.
> I would like to know the maximum size to which the database can grow to
> in SQL Server as many tables in the database will have over 1 million
> records with each row having images, documents stored in it.
> The server housing SQL Server is Dell PowerEdge 2950 with single CPU
> dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.
In this case it sounds like the max size will be 73 GB.
I'd suggest NOT storing images in the database, but that's a different
debate.
btw, 1 million records is generally considered, "small" these days.
>|||thanks for the reply
Adi wrote:
> In reality the size of the database is limited by your disk space.
> According to BOL the database size can be up to 1,048,516 TB (depending
> on the edition that you have). If you meant to ask at what size the
> database's performance will not be good, then that depends on the
> database's structure, the quality of the code that works with the
> database, the number of concurrent users and other factors much more
> then it depends on the database's size.
> Adi
> ram2811 wrote:
> > I am developing an intranet portal on Microsoft .NET platform and using
> > SQL Server 2000 Enterprise Edition as the database.
> > I would like to know the maximum size to which the database can grow to
> > in SQL Server as many tables in the database will have over 1 million
> > records with each row having images, documents stored in it.
> > The server housing SQL Server is Dell PowerEdge 2950 with single CPU
> > dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.

Data handling capabilities of SQL Server 2000 Enterprise Edition

I am developing an intranet portal on Microsoft .NET platform and using
SQL Server 2000 Enterprise Edition as the database.
I would like to know the maximum size to which the database can grow to
in SQL Server as many tables in the database will have over 1 million
records with each row having images, documents stored in it.
The server housing SQL Server is Dell PowerEdge 2950 with single CPU
dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.
In reality the size of the database is limited by your disk space.
According to BOL the database size can be up to 1,048,516 TB (depending
on the edition that you have). If you meant to ask at what size the
database's performance will not be good, then that depends on the
database's structure, the quality of the code that works with the
database, the number of concurrent users and other factors much more
then it depends on the database's size.
Adi
ram2811 wrote:
> I am developing an intranet portal on Microsoft .NET platform and using
> SQL Server 2000 Enterprise Edition as the database.
> I would like to know the maximum size to which the database can grow to
> in SQL Server as many tables in the database will have over 1 million
> records with each row having images, documents stored in it.
> The server housing SQL Server is Dell PowerEdge 2950 with single CPU
> dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.
|||"ram2811" <ram2811@.gmail.com> wrote in message
news:1163533063.339418.203140@.i42g2000cwa.googlegr oups.com...
>I am developing an intranet portal on Microsoft .NET platform and using
> SQL Server 2000 Enterprise Edition as the database.
> I would like to know the maximum size to which the database can grow to
> in SQL Server as many tables in the database will have over 1 million
> records with each row having images, documents stored in it.
> The server housing SQL Server is Dell PowerEdge 2950 with single CPU
> dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.
In this case it sounds like the max size will be 73 GB.
I'd suggest NOT storing images in the database, but that's a different
debate.
btw, 1 million records is generally considered, "small" these days.

>
|||thanks for the reply
Adi wrote:[vbcol=seagreen]
> In reality the size of the database is limited by your disk space.
> According to BOL the database size can be up to 1,048,516 TB (depending
> on the edition that you have). If you meant to ask at what size the
> database's performance will not be good, then that depends on the
> database's structure, the quality of the code that works with the
> database, the number of concurrent users and other factors much more
> then it depends on the database's size.
> Adi
> ram2811 wrote:

Data handling capabilities of SQL Server 2000 Enterprise Edition

I am developing an intranet portal on Microsoft .NET platform and using
SQL Server 2000 Enterprise Edition as the database.
I would like to know the maximum size to which the database can grow to
in SQL Server as many tables in the database will have over 1 million
records with each row having images, documents stored in it.
The server housing SQL Server is Dell PowerEdge 2950 with single CPU
dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.In reality the size of the database is limited by your disk space.
According to BOL the database size can be up to 1,048,516 TB (depending
on the edition that you have). If you meant to ask at what size the
database's performance will not be good, then that depends on the
database's structure, the quality of the code that works with the
database, the number of concurrent users and other factors much more
then it depends on the database's size.
Adi
ram2811 wrote:
> I am developing an intranet portal on Microsoft .NET platform and using
> SQL Server 2000 Enterprise Edition as the database.
> I would like to know the maximum size to which the database can grow to
> in SQL Server as many tables in the database will have over 1 million
> records with each row having images, documents stored in it.
> The server housing SQL Server is Dell PowerEdge 2950 with single CPU
> dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.|||"ram2811" <ram2811@.gmail.com> wrote in message
news:1163533063.339418.203140@.i42g2000cwa.googlegroups.com...
>I am developing an intranet portal on Microsoft .NET platform and using
> SQL Server 2000 Enterprise Edition as the database.
> I would like to know the maximum size to which the database can grow to
> in SQL Server as many tables in the database will have over 1 million
> records with each row having images, documents stored in it.
> The server housing SQL Server is Dell PowerEdge 2950 with single CPU
> dual Core Xeon 4MB Cache 3.0Ghz, 2GB memory, 73GB disk space and RAID 5.
In this case it sounds like the max size will be 73 GB.
I'd suggest NOT storing images in the database, but that's a different
debate.
btw, 1 million records is generally considered, "small" these days.

>|||thanks for the reply
Adi wrote:[vbcol=seagreen]
> In reality the size of the database is limited by your disk space.
> According to BOL the database size can be up to 1,048,516 TB (depending
> on the edition that you have). If you meant to ask at what size the
> database's performance will not be good, then that depends on the
> database's structure, the quality of the code that works with the
> database, the number of concurrent users and other factors much more
> then it depends on the database's size.
> Adi
> ram2811 wrote: