First a little history:
We have a Pentium II server running SQL 7.0. The SQL has a database that
our users connect to using a client front end app that was created by a
former programmer in our office. The file server name in the beginning was
called FRE3.
In the beginning the server was running NT4 and the users were on Win95
desktops.
We had a migration a few years ago where the server was upgraded to Windows
2000 server and the desktops were upgraded to Windows 2000 Professional. We
also had to make a server name change to fall in line with official naming
conventions. The server's name was changed to NTFRE. It was and still is
just a member server in our AD.
Of course, the client app had to be modified as it refers to the server name
and us non-programmers figured out how to change the name in the Visual Basic
code and recompiled a new executable and it worked fine. Just had to change
one instance in the code where it names the server.
We are now going through a new migration. We have a new box and have
installed Windows Server 2003 Enterprise on it. We have also installed SQL
2000 on it. Have updated all service packs and everything. Ran the copy
database wizard and successfully brought over the database from the SQL 7.0
server, as well as user logins. User destops are being migrated to Windows
XP as well.
So we broke into the code again, and changed the server name again like last
time, (new 2003 server is called S2K3-FRE-SQL1), and recompiled a new
executable.
Houston, we now have a problem. When I executed new executable on new XP
machine, I get this error message after logging in:
Run Time Error - '2147217900(80040e14)
Incorrect syntax near keyword 'function'
Does this error message mean anything to any of you gurus?
There is one bit of info that I need to relay, not sure if it matters or not:
The old server running 7.0, in Enterprise Manager, under SQL Server Group,
it states 2KFRE (Windows NT).
In the new server running 2000, in Enterprise Manager, under SQL Server
Group, it does not state the name of the server (S2K3-FRE-SQL1), it just
states Local (Windows NT).
Should I worry about this? Is the code looking for S2K3-FRE-SQL1 and seeing
the word Local instead, thus giving me my error message'?
Do you believe that the client code needs to be modified somewhere else now'
Is this error message a reflection of code built to address a SQL 7.0
installation and now it doesn't work as it's trying to talk to a SQL 2000
installation'Hi
function is a keyword so can't be used in the code. You may want to use the
scripting options of Enterprise Manager to script out the stored procedures
to try a textual search for function and see where it occurs. It could be
that you also have triggers which may contain the the key word. Alternatively
you could use SQL profiler to look at what SQL is being run on the server and
try and narrow down what is going on. If you want to look at
http://tinyurl.com/yejfye which is a MSDN webcast on using SQL 2000 Profiler,
there is also one for SQL 2005 and other tools.
You also have a lot of information in books online and it is certainly worth
your while browsing it.
HTH
John
"Rockitman" wrote:
> First a little history:
> We have a Pentium II server running SQL 7.0. The SQL has a database that
> our users connect to using a client front end app that was created by a
> former programmer in our office. The file server name in the beginning was
> called FRE3.
> In the beginning the server was running NT4 and the users were on Win95
> desktops.
> We had a migration a few years ago where the server was upgraded to Windows
> 2000 server and the desktops were upgraded to Windows 2000 Professional. We
> also had to make a server name change to fall in line with official naming
> conventions. The server's name was changed to NTFRE. It was and still is
> just a member server in our AD.
> Of course, the client app had to be modified as it refers to the server name
> and us non-programmers figured out how to change the name in the Visual Basic
> code and recompiled a new executable and it worked fine. Just had to change
> one instance in the code where it names the server.
> We are now going through a new migration. We have a new box and have
> installed Windows Server 2003 Enterprise on it. We have also installed SQL
> 2000 on it. Have updated all service packs and everything. Ran the copy
> database wizard and successfully brought over the database from the SQL 7.0
> server, as well as user logins. User destops are being migrated to Windows
> XP as well.
> So we broke into the code again, and changed the server name again like last
> time, (new 2003 server is called S2K3-FRE-SQL1), and recompiled a new
> executable.
> Houston, we now have a problem. When I executed new executable on new XP
> machine, I get this error message after logging in:
> Run Time Error - '2147217900(80040e14)
> Incorrect syntax near keyword 'function'
>
> Does this error message mean anything to any of you gurus?
> There is one bit of info that I need to relay, not sure if it matters or not:
> The old server running 7.0, in Enterprise Manager, under SQL Server Group,
> it states 2KFRE (Windows NT).
> In the new server running 2000, in Enterprise Manager, under SQL Server
> Group, it does not state the name of the server (S2K3-FRE-SQL1), it just
> states Local (Windows NT).
> Should I worry about this? Is the code looking for S2K3-FRE-SQL1 and seeing
> the word Local instead, thus giving me my error message'?
> Do you believe that the client code needs to be modified somewhere else now'
> Is this error message a reflection of code built to address a SQL 7.0
> installation and now it doesn't work as it's trying to talk to a SQL 2000
> installation'
>
>sql
Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts
Monday, March 26, 2012
Incorrect syntax near keyword "function".
First a little history:
We have a Pentium II server running SQL 7.0. The SQL has a database that
our users connect to using a client front end app that was created by a
former programmer in our office. The file server name in the beginning was
called FRE3.
In the beginning the server was running NT4 and the users were on Win95
desktops.
We had a migration a few years ago where the server was upgraded to Windows
2000 server and the desktops were upgraded to Windows 2000 Professional. W
e
also had to make a server name change to fall in line with official naming
conventions. The server's name was changed to NTFRE. It was and still is
just a member server in our AD.
Of course, the client app had to be modified as it refers to the server name
and us non-programmers figured out how to change the name in the Visual Basi
c
code and recompiled a new executable and it worked fine. Just had to change
one instance in the code where it names the server.
We are now going through a new migration. We have a new box and have
installed Windows Server 2003 Enterprise on it. We have also installed SQL
2000 on it. Have updated all service packs and everything. Ran the copy
database wizard and successfully brought over the database from the SQL 7.0
server, as well as user logins. User destops are being migrated to Windows
XP as well.
So we broke into the code again, and changed the server name again like last
time, (new 2003 server is called S2K3-FRE-SQL1), and recompiled a new
executable.
Houston, we now have a problem. When I executed new executable on new XP
machine, I get this error message after logging in:
Run Time Error - '2147217900(80040e14)
Incorrect syntax near keyword 'function'
Does this error message mean anything to any of you gurus?
There is one bit of info that I need to relay, not sure if it matters or not
:
The old server running 7.0, in Enterprise Manager, under SQL Server Group,
it states 2KFRE (Windows NT).
In the new server running 2000, in Enterprise Manager, under SQL Server
Group, it does not state the name of the server (S2K3-FRE-SQL1), it just
states Local (Windows NT).
Should I worry about this? Is the code looking for S2K3-FRE-SQL1 and seeing
the word Local instead, thus giving me my error message'?
Do you believe that the client code needs to be modified somewhere else now?
?
Is this error message a reflection of code built to address a SQL 7.0
installation and now it doesn't work as it's trying to talk to a SQL 2000
installation'Hi
function is a keyword so can't be used in the code. You may want to use the
scripting options of Enterprise Manager to script out the stored procedures
to try a textual search for function and see where it occurs. It could be
that you also have triggers which may contain the the key word. Alternativel
y
you could use SQL profiler to look at what SQL is being run on the server an
d
try and narrow down what is going on. If you want to look at
http://tinyurl.com/yejfye which is a MSDN webcast on using SQL 2000 Profiler
,
there is also one for SQL 2005 and other tools.
You also have a lot of information in books online and it is certainly worth
your while browsing it.
HTH
John
"Rockitman" wrote:
> First a little history:
> We have a Pentium II server running SQL 7.0. The SQL has a database that
> our users connect to using a client front end app that was created by a
> former programmer in our office. The file server name in the beginning wa
s
> called FRE3.
> In the beginning the server was running NT4 and the users were on Win95
> desktops.
> We had a migration a few years ago where the server was upgraded to Window
s
> 2000 server and the desktops were upgraded to Windows 2000 Professional.
We
> also had to make a server name change to fall in line with official naming
> conventions. The server's name was changed to NTFRE. It was and still i
s
> just a member server in our AD.
> Of course, the client app had to be modified as it refers to the server na
me
> and us non-programmers figured out how to change the name in the Visual Ba
sic
> code and recompiled a new executable and it worked fine. Just had to chan
ge
> one instance in the code where it names the server.
> We are now going through a new migration. We have a new box and have
> installed Windows Server 2003 Enterprise on it. We have also installed SQ
L
> 2000 on it. Have updated all service packs and everything. Ran the copy
> database wizard and successfully brought over the database from the SQL 7.
0
> server, as well as user logins. User destops are being migrated to Window
s
> XP as well.
> So we broke into the code again, and changed the server name again like la
st
> time, (new 2003 server is called S2K3-FRE-SQL1), and recompiled a new
> executable.
> Houston, we now have a problem. When I executed new executable on new XP
> machine, I get this error message after logging in:
> Run Time Error - '2147217900(80040e14)
> Incorrect syntax near keyword 'function'
>
> Does this error message mean anything to any of you gurus?
> There is one bit of info that I need to relay, not sure if it matters or n
ot:
> The old server running 7.0, in Enterprise Manager, under SQL Server Grou
p,
> it states 2KFRE (Windows NT).
> In the new server running 2000, in Enterprise Manager, under SQL Server
> Group, it does not state the name of the server (S2K3-FRE-SQL1), it just
> states Local (Windows NT).
> Should I worry about this? Is the code looking for S2K3-FRE-SQL1 and seei
ng
> the word Local instead, thus giving me my error message'?
> Do you believe that the client code needs to be modified somewhere else no
w'
> Is this error message a reflection of code built to address a SQL 7.0
> installation and now it doesn't work as it's trying to talk to a SQL 2000
> installation'
>
>
We have a Pentium II server running SQL 7.0. The SQL has a database that
our users connect to using a client front end app that was created by a
former programmer in our office. The file server name in the beginning was
called FRE3.
In the beginning the server was running NT4 and the users were on Win95
desktops.
We had a migration a few years ago where the server was upgraded to Windows
2000 server and the desktops were upgraded to Windows 2000 Professional. W
e
also had to make a server name change to fall in line with official naming
conventions. The server's name was changed to NTFRE. It was and still is
just a member server in our AD.
Of course, the client app had to be modified as it refers to the server name
and us non-programmers figured out how to change the name in the Visual Basi
c
code and recompiled a new executable and it worked fine. Just had to change
one instance in the code where it names the server.
We are now going through a new migration. We have a new box and have
installed Windows Server 2003 Enterprise on it. We have also installed SQL
2000 on it. Have updated all service packs and everything. Ran the copy
database wizard and successfully brought over the database from the SQL 7.0
server, as well as user logins. User destops are being migrated to Windows
XP as well.
So we broke into the code again, and changed the server name again like last
time, (new 2003 server is called S2K3-FRE-SQL1), and recompiled a new
executable.
Houston, we now have a problem. When I executed new executable on new XP
machine, I get this error message after logging in:
Run Time Error - '2147217900(80040e14)
Incorrect syntax near keyword 'function'
Does this error message mean anything to any of you gurus?
There is one bit of info that I need to relay, not sure if it matters or not
:
The old server running 7.0, in Enterprise Manager, under SQL Server Group,
it states 2KFRE (Windows NT).
In the new server running 2000, in Enterprise Manager, under SQL Server
Group, it does not state the name of the server (S2K3-FRE-SQL1), it just
states Local (Windows NT).
Should I worry about this? Is the code looking for S2K3-FRE-SQL1 and seeing
the word Local instead, thus giving me my error message'?
Do you believe that the client code needs to be modified somewhere else now?
?
Is this error message a reflection of code built to address a SQL 7.0
installation and now it doesn't work as it's trying to talk to a SQL 2000
installation'Hi
function is a keyword so can't be used in the code. You may want to use the
scripting options of Enterprise Manager to script out the stored procedures
to try a textual search for function and see where it occurs. It could be
that you also have triggers which may contain the the key word. Alternativel
y
you could use SQL profiler to look at what SQL is being run on the server an
d
try and narrow down what is going on. If you want to look at
http://tinyurl.com/yejfye which is a MSDN webcast on using SQL 2000 Profiler
,
there is also one for SQL 2005 and other tools.
You also have a lot of information in books online and it is certainly worth
your while browsing it.
HTH
John
"Rockitman" wrote:
> First a little history:
> We have a Pentium II server running SQL 7.0. The SQL has a database that
> our users connect to using a client front end app that was created by a
> former programmer in our office. The file server name in the beginning wa
s
> called FRE3.
> In the beginning the server was running NT4 and the users were on Win95
> desktops.
> We had a migration a few years ago where the server was upgraded to Window
s
> 2000 server and the desktops were upgraded to Windows 2000 Professional.
We
> also had to make a server name change to fall in line with official naming
> conventions. The server's name was changed to NTFRE. It was and still i
s
> just a member server in our AD.
> Of course, the client app had to be modified as it refers to the server na
me
> and us non-programmers figured out how to change the name in the Visual Ba
sic
> code and recompiled a new executable and it worked fine. Just had to chan
ge
> one instance in the code where it names the server.
> We are now going through a new migration. We have a new box and have
> installed Windows Server 2003 Enterprise on it. We have also installed SQ
L
> 2000 on it. Have updated all service packs and everything. Ran the copy
> database wizard and successfully brought over the database from the SQL 7.
0
> server, as well as user logins. User destops are being migrated to Window
s
> XP as well.
> So we broke into the code again, and changed the server name again like la
st
> time, (new 2003 server is called S2K3-FRE-SQL1), and recompiled a new
> executable.
> Houston, we now have a problem. When I executed new executable on new XP
> machine, I get this error message after logging in:
> Run Time Error - '2147217900(80040e14)
> Incorrect syntax near keyword 'function'
>
> Does this error message mean anything to any of you gurus?
> There is one bit of info that I need to relay, not sure if it matters or n
ot:
> The old server running 7.0, in Enterprise Manager, under SQL Server Grou
p,
> it states 2KFRE (Windows NT).
> In the new server running 2000, in Enterprise Manager, under SQL Server
> Group, it does not state the name of the server (S2K3-FRE-SQL1), it just
> states Local (Windows NT).
> Should I worry about this? Is the code looking for S2K3-FRE-SQL1 and seei
ng
> the word Local instead, thus giving me my error message'?
> Do you believe that the client code needs to be modified somewhere else no
w'
> Is this error message a reflection of code built to address a SQL 7.0
> installation and now it doesn't work as it's trying to talk to a SQL 2000
> installation'
>
>
Sunday, February 19, 2012
IN SQL Server Management Studio - Can connect to database sort of but Icon isn't green anymore
Preface: I'm a newbie at 2005 and sql server in general.
I can connect to a sql server (2005 express) but I can only make views and not run queries. When I open up a new query and create it with query designer and click add table I see no tables, views or anything in the box. When I create a new view in the database I do see tables and views though.
The little circle part of the icon on the server in the left hand pane is clear now when before it was green. I still can connect to the database ok but I can't use the query analyzer for queries anymore. I need to do that because I do have some slow running queries.
~Capt howdy
Select the database first (ie:AdventureWorks), 'new query' and then click design view.
|||I'm such a n00b with sql server it hurts sometimes. Thanks! I am used to access but it is definitely time to step up.
~Capt. Howdy
IN SQL Server Management Studio - Can connect to database sort of but Icon isn't green anym
Preface: I'm a newbie at 2005 and sql server in general.
I can connect to a sql server (2005 express) but I can only make views and not run queries. When I open up a new query and create it with query designer and click add table I see no tables, views or anything in the box. When I create a new view in the database I do see tables and views though.
The little circle part of the icon on the server in the left hand pane is clear now when before it was green. I still can connect to the database ok but I can't use the query analyzer for queries anymore. I need to do that because I do have some slow running queries.
~Capt howdy
Select the database first (ie:AdventureWorks), 'new query' and then click design view.
|||I'm such a n00b with sql server it hurts sometimes. Thanks! I am used to access but it is definitely time to step up.
~Capt. Howdy
Subscribe to:
Posts (Atom)