PAGE HEADER: sqlserver

Showing posts with label sqlserver. Show all posts

Friday, March 30, 2012

problem with sqlserver 2005 express

I am using VS2005 with sql server 2005 express.
I have database with atached datafile. when I am using Select command from
created table, there is not case sensitive in the result. I mean I have in
the table the row with value "Disp1" in col1, and when I am selecting with
filter Where col1="disp1" , I amd getting this one row where value is
"Disp1".
I saw in server explorer window, that connection have parameter Case
Sensitive, which value is False, but it is desabled and I can't change.
How to solve this problem.
Thanks
Collation is an attribute of the column in the table. A database has a default collation which is
applied if you don't specify a collation in the CREATE TABLE statement. Also, if you want a query to
be resolved with a different collation than the data is stored with, you can use COLLATE keyword in
the query.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Vaidas" <Vaidas@.discussions.microsoft.com> wrote in message
news:8E0BF60C-1A43-49F3-A41B-E1E05E30BE23@.microsoft.com...
>I am using VS2005 with sql server 2005 express.
> I have database with atached datafile. when I am using Select command from
> created table, there is not case sensitive in the result. I mean I have in
> the table the row with value "Disp1" in col1, and when I am selecting with
> filter Where col1="disp1" , I amd getting this one row where value is
> "Disp1".
> I saw in server explorer window, that connection have parameter Case
> Sensitive, which value is False, but it is desabled and I can't change.
> How to solve this problem.
> Thanks
>

problem with sqlserver 2005 express

I am using VS2005 with sql server 2005 express.
I have database with atached datafile. when I am using Select command from
created table, there is not case sensitive in the result. I mean I have in
the table the row with value "Disp1" in col1, and when I am selecting with
filter Where col1="disp1" , I amd getting this one row where value is
"Disp1".
I saw in server explorer window, that connection have parameter Case
Sensitive, which value is False, but it is desabled and I can't change.
How to solve this problem.
ThanksCollation is an attribute of the column in the table. A database has a default collation which is
applied if you don't specify a collation in the CREATE TABLE statement. Also, if you want a query to
be resolved with a different collation than the data is stored with, you can use COLLATE keyword in
the query.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Vaidas" <Vaidas@.discussions.microsoft.com> wrote in message
news:8E0BF60C-1A43-49F3-A41B-E1E05E30BE23@.microsoft.com...
>I am using VS2005 with sql server 2005 express.
> I have database with atached datafile. when I am using Select command from
> created table, there is not case sensitive in the result. I mean I have in
> the table the row with value "Disp1" in col1, and when I am selecting with
> filter Where col1="disp1" , I amd getting this one row where value is
> "Disp1".
> I saw in server explorer window, that connection have parameter Case
> Sensitive, which value is False, but it is desabled and I can't change.
> How to solve this problem.
> Thanks
>

problem with sqlserver 2005 express

Eric

problem with sqlserver 2005 express

Problem with SQLServer 2000

i installed the Visual Studio 2004+ Framework.NET 2

and SQLserver 2005

after those

i installed SQLserver 2000

and i got this :

http://img240.imageshack.us/img240/7392/sql2fk.jpg

thank you

This is the wrong forum. From your screenshot it looks like you should be checking the Express forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=385&SiteID=1

In the meantime, have you checked in the Services panel that SQL Server is running?

Have you enabled remote conenctions using the Surface Area configuraiton tool?

-Jamie

|||what should i change here?

http://img86.imageshack.us/img86/746/remote6np.jpg

thank you|||

From the screenshot http://img240.imageshack.us/img240/7392/sql2fk.jpg - it looks like you are trying to access SQL Server 2005 Express Edition from SQL Server Enterprise Manager.

Try accessing SQL Server 2005 express edition from SQL Server Management Studio (which is equivalent of SQL Server 2000 Enterprise manager for SQL Server 2005.)

Thanks,
Loonysan

|||i dont know what do u mean...

i even dont need SQL server 2005 i need only the 2000...

but i have heard that removing SQL server 2005 from my computer wont work...

can someone give me step by step what to do to solve the problem...

thank you :D|||

deViance wrote:
i dont know what do u mean...
i even dont need SQL server 2005 i need only the 2000...
but i have heard that removing SQL server 2005 from my computer wont work...
can someone give me step by step what to do to solve the problem...
thank you :D

For a starter, you are in the wrong place.

If you don't need SQL2005 why did you install it? What exactly are you trying to do?

-Jamie

Wednesday, March 28, 2012

Problem with SQL Server and odbc, please help me!

I have Visual Studio Dot.Net on Win XP and use the MSDE to access to Sql
Server.
This morning I've attempt to create a new ODBC DSN for Sql Server so
I've executed the wizard for a new System DSN by the ODBC administrator
of Windows. But when it attempts to connect to the server (the third
step of wizard) it give me somewhat like:
Connection impossible.
SQLState: '01000'
SQL Server error: 10049
SQLState: '08001'
SQL Server error: 17
I've tried to go forward with the manual configuration (uncheck the item
"Connect to an SQL Server for the default settings.." and press the Next
button), but at the end, when I press "Verify the data source", I have
no connection. So I've canceled the wizard.
The problem is that after that moment I have no connection with the server.
The console of MSDE indicate that the server is normally running, but I
can't connect to it neither by the Server Explorer of VS nor by osql.
I have always a message like:
[DBNETLIB][ConnectionOpen(Connect()).]Server non found or access denied.
Can someone help me?
Thanks
Tonio Tanzi
P.s. the messages of the server are probably a little different by the
ones indicate by me because I've translated them from the italian version.Tonio,
Is this a development server? If so try stopping the SQL Server service and
restarting it.
HTH
Jerry
"Tonio Tanzi" <vi.tan.gr@.inwind.it> wrote in message
news:m8c%e.3633$EZ.98724@.twister1.libero.it...
>I have Visual Studio Dot.Net on Win XP and use the MSDE to access to Sql
>Server.
> This morning I've attempt to create a new ODBC DSN for Sql Server so I've
> executed the wizard for a new System DSN by the ODBC administrator of
> Windows. But when it attempts to connect to the server (the third step of
> wizard) it give me somewhat like:
> Connection impossible.
> SQLState: '01000'
> SQL Server error: 10049
> SQLState: '08001'
> SQL Server error: 17
> I've tried to go forward with the manual configuration (uncheck the item
> "Connect to an SQL Server for the default settings.." and press the Next
> button), but at the end, when I press "Verify the data source", I have no
> connection. So I've canceled the wizard.
> The problem is that after that moment I have no connection with the
> server.
> The console of MSDE indicate that the server is normally running, but I
> can't connect to it neither by the Server Explorer of VS nor by osql.
> I have always a message like:
> [DBNETLIB][ConnectionOpen(Connect()).]Server non found or access denied.
>
> Can someone help me?
> Thanks
> Tonio Tanzi
> P.s. the messages of the server are probably a little different by the
> ones indicate by me because I've translated them from the italian version.|||Jerry Spivey ha scritto:
> Tonio,
> Is this a development server? If so try stopping the SQL Server service a
nd
> restarting it.
Yes. I've just stopped and restarted both Sql Server and computer many
times widhout any result.
Other suggest?
Bye
Tonio Tanzi

Friday, March 23, 2012

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg Pagan
I found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg PaganI found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg PaganI found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Hello
sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
posting there, I realised that this issue would probably appeal to a much
wider audience than the original newsgroup, hence my crossposting. Thanks for
not flaming me ;-)
Hello,
I am experiencing the following problem with DTS:
on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
the following upgrades:
- Windows SP2 --> no problem with DTS
- SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
small table anymore into an Excel spreadsheet)
I did repeat the test, and the problem was shwon to be consistent. I could
track it down to registering a few dlls of dts to have the machine behaving
correctly again.
Questions:
- did somebody also experienced something similar? If so, is any solution
known?
- does registering the dlls from DTS solve completely the problem? Are there
any related problems with other tools?
With kind regards,
Emmanuel
Hello,
as a follow-up, I most probably found the origin of the problem: a problem
with the image of the machine which I used to rebuild the PC. Namely, when
using sysprep, some permissions errors did probably occur (this is a know
problem), and using SubInAcl (a tool from Microsoft) did solve the problem.
Not that I'll trust this image anymore, though ...
Regards,
Emmanuel
"Emmanuel" wrote:

> Hello
> sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
> posting there, I realised that this issue would probably appeal to a much
> wider audience than the original newsgroup, hence my crossposting. Thanks for
> not flaming me ;-)
>
> Hello,
> I am experiencing the following problem with DTS:
> on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
> the following upgrades:
> - Windows SP2 --> no problem with DTS
> - SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
> small table anymore into an Excel spreadsheet)
> I did repeat the test, and the problem was shwon to be consistent. I could
> track it down to registering a few dlls of dts to have the machine behaving
> correctly again.
> Questions:
> - did somebody also experienced something similar? If so, is any solution
> known?
> - does registering the dlls from DTS solve completely the problem? Are there
> any related problems with other tools?
> With kind regards,
> Emmanuel
>
sql

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Hello
sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
posting there, I realised that this issue would probably appeal to a much
wider audience than the original newsgroup, hence my crossposting. Thanks fo
r
not flaming me ;-)
Hello,
I am experiencing the following problem with DTS:
on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
the following upgrades:
- Windows SP2 --> no problem with DTS
- SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
small table anymore into an Excel spreadsheet)
I did repeat the test, and the problem was shwon to be consistent. I could
track it down to registering a few dlls of dts to have the machine behaving
correctly again.
Questions:
- did somebody also experienced something similar? If so, is any solution
known?
- does registering the dlls from DTS solve completely the problem? Are there
any related problems with other tools?
With kind regards,
EmmanuelHello,
as a follow-up, I most probably found the origin of the problem: a problem
with the image of the machine which I used to rebuild the PC. Namely, when
using sysprep, some permissions errors did probably occur (this is a know
problem), and using SubInAcl (a tool from Microsoft) did solve the problem.
Not that I'll trust this image anymore, though ...
Regards,
Emmanuel
"Emmanuel" wrote:

> Hello
> sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
> posting there, I realised that this issue would probably appeal to a much
> wider audience than the original newsgroup, hence my crossposting. Thanks
for
> not flaming me ;-)
>
> Hello,
> I am experiencing the following problem with DTS:
> on a box running Windows XP SP1 and SQL Server 2000 client tools only, I d
id
> the following upgrades:
> - Windows SP2 --> no problem with DTS
> - SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
> small table anymore into an Excel spreadsheet)
> I did repeat the test, and the problem was shwon to be consistent. I could
> track it down to registering a few dlls of dts to have the machine behavin
g
> correctly again.
> Questions:
> - did somebody also experienced something similar? If so, is any solution
> known?
> - does registering the dlls from DTS solve completely the problem? Are the
re
> any related problems with other tools?
> With kind regards,
> Emmanuel
>

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Hello
sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
posting there, I realised that this issue would probably appeal to a much
wider audience than the original newsgroup, hence my crossposting. Thanks for
not flaming me ;-)
Hello,
I am experiencing the following problem with DTS:
on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
the following upgrades:
- Windows SP2 --> no problem with DTS
- SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
small table anymore into an Excel spreadsheet)
I did repeat the test, and the problem was shwon to be consistent. I could
track it down to registering a few dlls of dts to have the machine behaving
correctly again.
Questions:
- did somebody also experienced something similar? If so, is any solution
known?
- does registering the dlls from DTS solve completely the problem? Are there
any related problems with other tools?
With kind regards,
EmmanuelHello,
as a follow-up, I most probably found the origin of the problem: a problem
with the image of the machine which I used to rebuild the PC. Namely, when
using sysprep, some permissions errors did probably occur (this is a know
problem), and using SubInAcl (a tool from Microsoft) did solve the problem.
Not that I'll trust this image anymore, though ...
Regards,
Emmanuel
"Emmanuel" wrote:
> Hello
> sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
> posting there, I realised that this issue would probably appeal to a much
> wider audience than the original newsgroup, hence my crossposting. Thanks for
> not flaming me ;-)
>
> Hello,
> I am experiencing the following problem with DTS:
> on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
> the following upgrades:
> - Windows SP2 --> no problem with DTS
> - SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
> small table anymore into an Excel spreadsheet)
> I did repeat the test, and the problem was shwon to be consistent. I could
> track it down to registering a few dlls of dts to have the machine behaving
> correctly again.
> Questions:
> - did somebody also experienced something similar? If so, is any solution
> known?
> - does registering the dlls from DTS solve completely the problem? Are there
> any related problems with other tools?
> With kind regards,
> Emmanuel
>

Problem with sp_change_users_login

Hello,
I am trying to connect the user 'dbo' for a user database to an existing SQL
Server login, which, according to SQL Server BOL, should be accomplished by
using this syntax:
use MyUserDB
go
sp_change_users_login 'update_one', 'dbo', 'MyServerLogin'
I get an error message stating that 'dbo' is a forbidden value for the login
parameter in this procedure.
I tried reversing the order, but I get the same error.
If anyone has any clues to what is wrong I would appreciate a comment
I am working with a server which is to be a backup server for one of our Web
servers.
I am changing the setup to match the live server, where the 'dbo' user is
mapped to a login.
I did not set up either of them initially and I am not quite sure which user
names have to have a login, so I am playing it safe by matching the setup of
the live server.
Thank you
Ragnar
Use "sp_changedbowner"
Geoff N. Hiten
Microsoft SQL Server MVP
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:O6CaM$vWFHA.2060@.tk2msftngp13.phx.gbl...
> Hello,
> I am trying to connect the user 'dbo' for a user database to an existing
> SQL Server login, which, according to SQL Server BOL, should be
> accomplished by using this syntax:
> use MyUserDB
> go
> sp_change_users_login 'update_one', 'dbo', 'MyServerLogin'
> I get an error message stating that 'dbo' is a forbidden value for the
> login parameter in this procedure.
> I tried reversing the order, but I get the same error.
> If anyone has any clues to what is wrong I would appreciate a comment
> I am working with a server which is to be a backup server for one of our
> Web servers.
> I am changing the setup to match the live server, where the 'dbo' user is
> mapped to a login.
> I did not set up either of them initially and I am not quite sure which
> user names have to have a login, so I am playing it safe by matching the
> setup of the live server.
> Thank you
> Ragnar
>
|||Thank you Geoff,
It worked!
I did not try that because according to sp_helpdb the user with the login I
want to connect to dbo was already the owner.
However, when I displayed the users for the DB there was no login name shown
for the dbo user.
In the logins, under Security, this user name has the master as the default
DB, but that is true for the live server too.
I thought maybe this was similar to a case of orphaned users, which happens
when I restore database from a backup of the live server DB, even though dbo
was not shown as an orphaned user when I ran the report..
BTW, I assume the problem with orphaned users is because I have not been
able to restore the master DB with a backup from the live server, because I
have not been able to start SQL Server in single user mode.
I stop it, then start it from the command line with sqlservr.exe -c, -m, as
described in SQL Server BOL
Ragnar

Problem with sp_change_users_login

Hello,
I am trying to connect the user 'dbo' for a user database to an existing SQL
Server login, which, according to SQL Server BOL, should be accomplished by
using this syntax:
use MyUserDB
go
sp_change_users_login 'update_one', 'dbo', 'MyServerLogin'
I get an error message stating that 'dbo' is a forbidden value for the login
parameter in this procedure.
I tried reversing the order, but I get the same error.
If anyone has any clues to what is wrong I would appreciate a comment
I am working with a server which is to be a backup server for one of our Web
servers.
I am changing the setup to match the live server, where the 'dbo' user is
mapped to a login.
I did not set up either of them initially and I am not quite sure which user
names have to have a login, so I am playing it safe by matching the setup of
the live server.
Thank you
RagnarUse "sp_changedbowner"
Geoff N. Hiten
Microsoft SQL Server MVP
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:O6CaM$vWFHA.2060@.tk2msftngp13.phx.gbl...
> Hello,
> I am trying to connect the user 'dbo' for a user database to an existing
> SQL Server login, which, according to SQL Server BOL, should be
> accomplished by using this syntax:
> use MyUserDB
> go
> sp_change_users_login 'update_one', 'dbo', 'MyServerLogin'
> I get an error message stating that 'dbo' is a forbidden value for the
> login parameter in this procedure.
> I tried reversing the order, but I get the same error.
> If anyone has any clues to what is wrong I would appreciate a comment
> I am working with a server which is to be a backup server for one of our
> Web servers.
> I am changing the setup to match the live server, where the 'dbo' user is
> mapped to a login.
> I did not set up either of them initially and I am not quite sure which
> user names have to have a login, so I am playing it safe by matching the
> setup of the live server.
> Thank you
> Ragnar
>|||Thank you Geoff,
It worked!
I did not try that because according to sp_helpdb the user with the login I
want to connect to dbo was already the owner.
However, when I displayed the users for the DB there was no login name shown
for the dbo user.
In the logins, under Security, this user name has the master as the default
DB, but that is true for the live server too.
I thought maybe this was similar to a case of orphaned users, which happens
when I restore database from a backup of the live server DB, even though dbo
was not shown as an orphaned user when I ran the report..
BTW, I assume the problem with orphaned users is because I have not been
able to restore the master DB with a backup from the live server, because I
have not been able to start SQL Server in single user mode.
I stop it, then start it from the command line with sqlservr.exe -c, -m, as
described in SQL Server BOL
Ragnarsql

Wednesday, March 21, 2012

Problem with SnapShot replication

Hi
I'm trying to set up a snapshot replication to replicate data out to a SQL
server in our DMZ. I have created the snapshot etc. but when I then run the
distribution agent to synchronize data out to the server, it stops after a
few seconds and comes up with the error message below:
Line 17: Incorrect syntax near 'UPDATE STATISTICS '.
(Source: xxx.xxx.xxx.xxx (Data source); Error number: 170)
The name ' ' is not permitted in this context. Only constants, expressions,
or variables allowed here. Column names are not permitted.
(Source: xxx.xxx.xxx.xxx (Data source); Error number: 128)
The name 'Statistics have been updated for all tables.' is not permitted in
this context. Only constants, expressions, or variables allowed here. Column
names are not permitted.
(Source: xxx.xxx.xxx.xxx (Data source); Error number: 128)
I'm a little bit stucked with this.error message. The Source is the IP
adress of my SQL server in the DMZ (subscriber) so it looks like it's
something out that isn't right. Is there anywhere I can view the slq
statements that are being ran? Since it refers to a Line 17 it must run some
code somewhere. I'm also a bit stumped on why it does an "UPDATE
STATISTICS", but that's maybe a part of the Replication job?
Regards
Steen
Problem solved...(I hope...).
I tried to run a trace on the subscriber, to see which commands it was
actually running when trying to apply the subscription. I then found that
one of the stored procedures it applied from the source, had a syntax error.
When I omit that SP from the synchronization, it works......
Regards
Steen
Steen Persson wrote:
> Hi
> I'm trying to set up a snapshot replication to replicate data out to
> a SQL server in our DMZ. I have created the snapshot etc. but when I
> then run the distribution agent to synchronize data out to the
> server, it stops after a few seconds and comes up with the error
> message below:
> Line 17: Incorrect syntax near 'UPDATE STATISTICS '.
> (Source: xxx.xxx.xxx.xxx (Data source); Error number: 170)
> ----
--
> --
> The name ' ' is not permitted in this context. Only constants,
> expressions, or variables allowed here. Column names are not
> permitted. (Source: xxx.xxx.xxx.xxx (Data source); Error number: 128)
> ----
--
> --
> The name 'Statistics have been updated for all tables.' is not
> permitted in this context. Only constants, expressions, or variables
> allowed here. Column names are not permitted.
> (Source: xxx.xxx.xxx.xxx (Data source); Error number: 128)
> ----
--
> --
> I'm a little bit stucked with this.error message. The Source is the IP
> adress of my SQL server in the DMZ (subscriber) so it looks like it's
> something out that isn't right. Is there anywhere I can view the slq
> statements that are being ran? Since it refers to a Line 17 it must
> run some code somewhere. I'm also a bit stumped on why it does an
> "UPDATE STATISTICS", but that's maybe a part of the Replication job?
> Regards
> Steen

Problem with SnapShot replication

Hi
I'm trying to set up a snapshot replication to replicate data out to a SQL
server in our DMZ. I have created the snapshot etc. but when I then run the
distribution agent to synchronize data out to the server, it stops after a
few seconds and comes up with the error message below:
Line 17: Incorrect syntax near 'UPDATE STATISTICS '.
(Source: xxx.xxx.xxx.xxx (Data source); Error number: 170)
----
--
The name ' ' is not permitted in this context. Only constants, expressions,
or variables allowed here. Column names are not permitted.
(Source: xxx.xxx.xxx.xxx (Data source); Error number: 128)
----
--
The name 'Statistics have been updated for all tables.' is not permitted in
this context. Only constants, expressions, or variables allowed here. Column
names are not permitted.
(Source: xxx.xxx.xxx.xxx (Data source); Error number: 128)
----
--
I'm a little bit stucked with this.error message. The Source is the IP
adress of my SQL server in the DMZ (subscriber) so it looks like it's
something out that isn't right. Is there anywhere I can view the slq
statements that are being ran? Since it refers to a Line 17 it must run some
code somewhere. I'm also a bit stumped on why it does an "UPDATE
STATISTICS", but that's maybe a part of the Replication job?
Regards
SteenProblem solved...(I hope...).
I tried to run a trace on the subscriber, to see which commands it was
actually running when trying to apply the subscription. I then found that
one of the stored procedures it applied from the source, had a syntax error.
When I omit that SP from the synchronization, it works......
Regards
Steen
Steen Persson wrote:
> Hi
> I'm trying to set up a snapshot replication to replicate data out to
> a SQL server in our DMZ. I have created the snapshot etc. but when I
> then run the distribution agent to synchronize data out to the
> server, it stops after a few seconds and comes up with the error
> message below:
> Line 17: Incorrect syntax near 'UPDATE STATISTICS '.
> (Source: xxx.xxx.xxx.xxx (Data source); Error number: 170)
> ----
--
> --
> The name ' ' is not permitted in this context. Only constants,
> expressions, or variables allowed here. Column names are not
> permitted. (Source: xxx.xxx.xxx.xxx (Data source); Error number: 128)
> ----
--
> --
> The name 'Statistics have been updated for all tables.' is not
> permitted in this context. Only constants, expressions, or variables
> allowed here. Column names are not permitted.
> (Source: xxx.xxx.xxx.xxx (Data source); Error number: 128)
> ----
--
> --
> I'm a little bit stucked with this.error message. The Source is the IP
> adress of my SQL server in the DMZ (subscriber) so it looks like it's
> something out that isn't right. Is there anywhere I can view the slq
> statements that are being ran? Since it refers to a Line 17 it must
> run some code somewhere. I'm also a bit stumped on why it does an
> "UPDATE STATISTICS", but that's maybe a part of the Replication job?
> Regards
> Steen

Saturday, February 25, 2012

Problem with Provider=SQLXMLOLEDB.3.0

Hi!

When I make a connection to the sqlserver database, everything work
fine.
Recently I connected to a huge db 1.4 GB.
The querys are executed with the same time however making a connection
is taking a long time.

I am using the following connection string.

My_CONNECTION = "Provider=SQLXMLOLEDB.3.0;" & _
"Data Provider=SQLOLEDB;" & _
"Network Library=DBMSSOCN;" & _
"Data Source=" & MY_SERVER & ";" & _
"Initial Catalog=BigDB;" & _
"User Id=sa;" & _
"Password=sa"

Thanks is advance,
JaiJai (jaijai_kumar@.hotmail.com) writes:
> When I make a connection to the sqlserver database, everything work
> fine.
> Recently I connected to a huge db 1.4 GB.
> The querys are executed with the same time however making a connection
> is taking a long time.
> I am using the following connection string.
> My_CONNECTION = "Provider=SQLXMLOLEDB.3.0;" & _
> "Data Provider=SQLOLEDB;" & _
> "Network Library=DBMSSOCN;" & _
> "Data Source=" & MY_SERVER & ";" & _
> "Initial Catalog=BigDB;" & _
> "User Id=sa;" & _
> "Password=sa"

Take out Network Library from the connection string. Not sure if it
helps, but I don't think that DBMSOCN is one of the preferred onces.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks a lot for ur message...
It did not help?
Any other idea...?

Thanks,
Jai

Erland Sommarskog <sommar@.algonet.se> wrote in message news:<Xns94934E9BA02EYazorman@.127.0.0.1>...
> Jai (jaijai_kumar@.hotmail.com) writes:
> > When I make a connection to the sqlserver database, everything work
> > fine.
> > Recently I connected to a huge db 1.4 GB.
> > The querys are executed with the same time however making a connection
> > is taking a long time.
> > I am using the following connection string.
> > My_CONNECTION = "Provider=SQLXMLOLEDB.3.0;" & _
> > "Data Provider=SQLOLEDB;" & _
> > "Network Library=DBMSSOCN;" & _
> > "Data Source=" & MY_SERVER & ";" & _
> > "Initial Catalog=BigDB;" & _
> > "User Id=sa;" & _
> > "Password=sa"
> Take out Network Library from the connection string. Not sure if it
> helps, but I don't think that DBMSOCN is one of the preferred onces.|||Jai (jaijai_kumar@.hotmail.com) writes:
> Thanks a lot for ur message...
> It did not help?
> Any other idea...?

There was not an overflow of information in your post, so it is
difficult to suggest anything. But let's look at it again.

>> > When I make a connection to the sqlserver database, everything work
>> > fine.
>> > Recently I connected to a huge db 1.4 GB.
>> > The querys are executed with the same time however making a connection
>> > is taking a long time.

Is the database that is slow to connect to on the same server as
the one that is fast to connect to? (My assumption is that is not.)

If you connect to the slow server from Query Analyzer, does that
also take time? If that is fast, what if you connect with SQLOLEDB
only; that is "Provider=SQLOLEDB"?

Assuming that you connect slow no matter the method, the problem may
be in the network somewhere. Not really my field of expertise to
say what that may be. Did you try connecting by IP-addrress directly?

Finally, most people would find a 1.4GB a moderately size database,
or even smallish...

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Friday, March 30, 2012

problem with sqlserver 2005 express

problem with sqlserver 2005 express

problem with sqlserver 2005 express

problem with sqlserver 2005 express

problem with sqlserver 2005 express

Problem with SQLServer 2000

Wednesday, March 28, 2012

Problem with SQL Server and odbc, please help me!

Friday, March 23, 2012

Problem with SP4 installation and REPLSYS.SQL

Problem with SP4 installation and REPLSYS.SQL

Problem with SP4 installation and REPLSYS.SQL

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Problem with sp_change_users_login

Problem with sp_change_users_login

Wednesday, March 21, 2012

Problem with SnapShot replication

Problem with SnapShot replication

Saturday, February 25, 2012

Problem with Provider=SQLXMLOLEDB.3.0

PAGE HEADER

Blog Archive

About Me