MS Sqlserver 2005: Displaying only dbs user has a right to?

Hi;

My company just installed MS SQLServer 2005 ( see below the dotted
line ).

When a user logs into management studio all of the databases on the
server are displayed in the right hand column.

What can we do to have only the databases the user has rights to,
display?

Thanks much in advance for any info.

Steve

--------------------
Microsoft SQL Server Management Studio9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML2.6 3.0 4.0 6.0
Microsoft Internet Explorer7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System5.1.2600Steve (tinker123@.gmail.com) writes:

Quote:

Originally Posted by

My company just installed MS SQLServer 2005 ( see below the dotted
line ).
>
When a user logs into management studio all of the databases on the
server are displayed in the right hand column.
>
What can we do to have only the databases the user has rights to,
display?

What you can do is to revoke the permission VIEW ANY DATABASE from public,
or DENY this permission to the users in question. Alas, the user would then only see tempdb and msdb (or was it master?), databases he owns, and
possibly his current database. He would have to issue a USE database in
the dark to get there.

This is not an uncommon question, so I filed a suggestion for an improvement
in SQL Server. You can vote on it at
https://connect.microsoft.com/SQLSe...edbackID=273830
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

MS SQL: syntax error in create table sql

Using Management Studio (for MS SQL server 8) I had created a table, given a primary key and created a unique key.
I then had the management studio "script 'create' to file" and it saved an SQL statement (below).
I then dropped/deleted the table and tried to execute the creation statement.
It says "Incorrect syntax near '('. " and references the block connected with the "WITH" statement. (Actually both of them cause the error and removing them gets rid of it.
Is there a way to keep the information contained in the WITH statement in my table creation SQL? Is it even required info?

Code: ( sql )

USE [MyProducts]GO/****** Object: Table [dbo].[Category] Script Date: 10/12/2007 11:22:52 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOSET ANSI_PADDING ONGOCREATE TABLE [dbo].[Category]( [CategoryID] [int] IDENTITY(1,1) NOT NULL, [Name] [varchar](50) NOT NULL, [CategoryNumber] [int] NOT NULL, [ModifiedDate] [datetime] NOT NULL, CONSTRAINT [PK_Category] PRIMARY KEY CLUSTERED ( [CategoryID] ASC ) WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON ) ON [PRIMARY], CONSTRAINT [IX_UniqueCategoryNumber] UNIQUE NONCLUSTERED ( [CategoryNumber] ASC ) WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON ) ON [PRIMARY]) ON [PRIMARY] GOSET ANSI_PADDING OFF

Usually you never use With statement while creating a table.

Remove this statement and create table without it then go to table definition and see it should be picked by default.

Good Luck.|||it "appeared" to create correctly without the WITH statements.
I was just bothered by the management studio auto-createing the statement then telling my there were syntax errors. The msdn help on the T-SQL for it shows WITH statements in the smae style.
All well, I'll just remove them.

Thanks.|||You can change some settings but not all.
Most of them are server level settings and can not be changed and just read only.

For example you see ON [PRIMARY] and it allows you to put data on one device and indexes on different devices or even spread tables among several devices but server should see your other devices first before you are trying to create something on them. So it is available but for people who know what they doing
You are doing grate so good luck.

MS SQL server management studio express

hi there !

Well i hope u all great people are having great time. Well i am new to asp.net and struggling in database deployment to server. I took webhosting from datapacket.net, and using helm control panel. to deploy database, i used sql management studio express as suggested by some one. Now i am not able to access any of database or tables, although i got connected when i altered configuration surface setting to allow server to go to remote server. Now please help me, how to deploy database ?

Thanks

I did not understand you question.

You get connected to the server, but you cannot see the database ? So how do you know you are connected to the server ?

Or

you can connect to the server all of the databases in the server are listed in the object explorer of you Managment studio express and you cannot connect to the database ? If is this option it is probably your credencials.

Are there any errors message ? Can you post them if it is ?

|||

Hi,

Since you haven't give us the detail situation, so I just conclude some of the reasons which is generally happened for you to refer.

From your words, " i got connected when i altered configuration surface setting to allow server to go to remote server", it seems you have connected to the remote database server successfully by your management tool. So I guess, the problem is occurred while connecting to your database in your application. If so, there's nothing related with the deployment of the database. Please do check your connection string which your application use to see if it is working properly.

If the situation is just like after you have uploaded your database onto your server, you can see the database and tables but you can't implement some action such as select,update,delete and etc, then it seems the problem is caused by the wrong setting of database or tables' owners or roles. Just try to find if the role on your SqlServer has the permission to implement these database objects.

Thanks.

MS SQL Server Management Studio - permissions and stored procedures

Hi

My website uses GET variables a lot and i'm trying to safe guard as much as possible against SQL injection attacks. I'm trying to create permissions which will deny a user to Delete/Insert/Update various tables.

I have managed this with the tables themselves, but when using a stored procedure, the tables do not take into account the user permissions which were set for that table!

Basically, how do i stop a stored procedure from Deleting/Inserting/Updating tables? :(

many thanksYour best bet is to avoid dynamic code within your stored procedure. Failing that, you need to avoid actually executing any submitted parameters within you stored procedure. Failing that, you need to thoroughly verify parameter strings before including them in any executed sql.|||hi blindman

I am not using any dynamic code, i am just passing in variables to my stored proc.

I'm not sure what you mean by:

Failing that, you need to avoid actually executing any submitted parameters within you stored procedure.

I'm using SELECT statements only in my stored proc, for example:

SELECT t3.sub_id, t2.SIC_id, t1.business_name, t1.venue_id, t1.address1, t1.address2, t1.address3, t1.address4, t1.county, t1.town, t1.postcode, t1.tel, t1.img_thumb
FROM VENUE AS t1 INNER JOIN SIC AS t2 ON t1.venue_id = t2.venue_id INNER JOIN SUBSCRIPTION AS t3 ON t1.venue_id = t3.venue_id INNER JOIN SIC_TYPE AS t4 ON t2.SIC_id = t4.SIC_id
WHERE (t3.sub_id = 1) AND (t2.SIC_id = 8 OR t2.SIC_id = 9) AND (t1.town = @.city OR @.city = '0') AND (postcode LIKE @.postcode + '%' OR @.postcode = '0') AND (county = @.county OR @.county = '0')

Can you see anything wrong with that with regards to injection attacks?

thanks|||The code you posted is not susceptible to SQL injection attacks.

MS SQL Server 2005 timeout error when using Management Studio

Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
Hi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:

> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>
|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

MS SQL Server 2005 timeout error when using Management Studio

Hi,
When I try to update a column value using MS SQL Server 2005 Management
Studio (SMS), I am getting "timeout period elapsed prior to the completion
of the operation".
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
VN
Hi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:

> Hi,
> When I try to update a column value using MS SQL Server 2005 Management
> Studio (SMS), I am getting "timeout period elapsed prior to the completion
> of the operation".
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
> VN
>
>

MS SQL Server 2005 timeout error when using Management Studio

Hi,
When I try to update a column value using MS SQL Server 2005 Management
Studio (SMS), I am getting "timeout period elapsed prior to the completion
of the operation".
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
Thanks
VNHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:

> Hi,
> When I try to update a column value using MS SQL Server 2005 Management
> Studio (SMS), I am getting "timeout period elapsed prior to the completion
> of the operation".
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
> VN
>
>sql

MS SQL Server 2005 timeout error when using Management Studio

Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
ThanksHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:

> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update
a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update
a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where eve
r
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having an
y
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

MS SQL Server 2005 timeout error when using Management Studio

Does anyone know, how to solve "timeout period elapsed prior to the
completion of the operation" problem which occured when I tried to update a
column value using MS SQL Server 2005 Management Studio (SMS).
Our server setup is:
2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
connected to second server using linked server. So if I update any column
value in Server A, it should automatically change the value in Server B
also. This works fine when I use update query in management studio. But if
directly open the table in management studio and try to update the column
value, I am keep getting the above mentioned error even though I have set
the timeout to large value (say 600 to 3,000 secs) in all places where ever
values related to timeout.
The above mentioned scenario works fine with 2 MS SQL 2000 servers running
in Win 2k OS and it is being in production for long time without having any
problem.
Any idea, as I have tried out all possible solutions.
ThanksHi
You seem to have posted this separately to several news groups. This can
cause people unnecessary effort if the solution is solved elsewhere.
John
"Venkat N" wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
>|||Venkat N wrote:
> Does anyone know, how to solve "timeout period elapsed prior to the
> completion of the operation" problem which occured when I tried to update a
> column value using MS SQL Server 2005 Management Studio (SMS).
> Our server setup is:
> 2 identical MS SQL 2005 installed in Windows 2003 OS and the first server
> connected to second server using linked server. So if I update any column
> value in Server A, it should automatically change the value in Server B
> also. This works fine when I use update query in management studio. But if
> directly open the table in management studio and try to update the column
> value, I am keep getting the above mentioned error even though I have set
> the timeout to large value (say 600 to 3,000 secs) in all places where ever
> values related to timeout.
> The above mentioned scenario works fine with 2 MS SQL 2000 servers running
> in Win 2k OS and it is being in production for long time without having any
> problem.
> Any idea, as I have tried out all possible solutions.
> Thanks
>
The simple answer, and the one you're likely to get from this group, is
to not modify your tables using the GUI. It's simply not intended for
that use.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

MS SQL database not connecting problem

hi

I usually did my database in SQL Server Management Studio Express then when I was in Visual Studios I would connect to it in the server explorer tab but I wanted to try to do it through Visual studios so I took my database files then went to my app_data folder and added them as existing items. I then went back to the server explorer tab and set it up.

Everything thing seemed to set up but when I run it I get an error.

I get this error when it does conn.Open();

Error:

1System.Data.SqlClient.SqlException was unhandledbyuser code2 Message="Cannotopen database \"Japanese\" requestedby the login. The login failed.\r\nLogin failedforuser'HOWSER\\chobo'."3 Source=".Net SqlClient Data Provider"4 ErrorCode=-21462320605 Class=116 LineNumber=655367 Number=40608Procedure=""9 Server="localhost\\SqlExpress"10 State=111 StackTrace:12 at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)13 at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)14 at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)15 at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)16 at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)17 at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)18 at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)19 at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentityidentity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)20 at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)21 at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)22 at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)23 at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)24 at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)25 at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)26 at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)27 at System.Data.SqlClient.SqlConnection.Open()28 at Practice.Page_Load(Object sender, EventArgs e)in h:\Website\Japanese\Practice.aspx.cs:line 2829 at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)30 at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)31 at System.Web.UI.Control.OnLoad(EventArgs e)32 at System.Web.UI.Control.LoadRecursive()33 at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)34

This is what I have as my connection stuff

webconfig

1 <connectionStrings>2 <add name="Japanese" connectionString="Server=localhost\SqlExpress;3 Database=Japanese; Integrated Security=True"4 providerName ="System.Data.SqlClient"/>5 </connectionStrings>67

In my file

 
1 SqlConnection conn;2 SqlCommand comm;3 SqlDataReader reader;45string connectionString = ConfigurationManager.ConnectionStrings["Japanese"].ConnectionString;6 conn =new SqlConnection(connectionString);78 comm =new SqlCommand("SELECT HiraganaCharacter,HiraganaImage FROM Hiragana", conn);9 conn.Open();10 reader = comm.ExecuteReader();
 Thanks 

Hi,

can you check your code connection string?

it would be usually in this format for SQLserver connection in the config file:

connectionString="Data Source=yourservername;Initial Catalog=yourdatabasename;User ID=userid"

providerName="System.Data.SqlClient"

Hope this helps

MS Sql 2005 Master DB sysprocess with ASP

I am having issue trying to obtain data from a query to MS SQL 2005 master database using a ASP to view the information. When I use management studio and run this query, I get the correct result.

Code: ( text )

1. select hostname, count(*) from master.sys.sysprocesses group by hostname

When trying to implement this to write out to a asp page, the result is the machine that is hitting the DB and nothing more. This works for a MS SQL 2000 but why doesn't it work for 2005. Here is the ado snippt I am using to connect to the DB using DSN.

Code: ( text )

1. Set objConn = server.CreateObject("ADODB.Connection")

3. objConn.Open "dbserver", "user", "password"

5. strSQL = "select hostname, count(*) as ""Connection"" from master..sysprocesses (nolock) group by hostname order by ""Connection"" desc"

7. Set sqlData = objConn.Execute(strSQL)

What error do you get?
It occurs on objConn.Open, or on objConn.Execute?|||The odd thing is, I am not getting any Errors.
The page works but it doesn't show the correct information.
What it shows is the web machine that is accessing the sql 2005 machine.|||

Quote:

Originally Posted by rvl1980

The odd thing is, I am not getting any Errors.
The page works but it doesn't show the correct information.
What it shows is the web machine that is accessing the sql 2005 machine.

This is what I get from 2000 and 2005 sql from my asp.

From MS SQL 2000 using asp to display
Host Num of Connection(s)
Server123 118
WSX0160 90

From MS SQL 2005 using asp to display
Host Num of Connection(s)
TRACKING 1|||I guess there no help with this?

MS SQL 2005 Management Studio

Where do I find the Management Studio to install on my laptop?
I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and it
says I cannot use regular old EM to register the server on my laptop.Apparently there are more people having the same problem. Microsoft should
address this issue in a KB.
Thanks
Matt
"Steve Z" wrote:

> Where do I find the Management Studio to install on my laptop?
> I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and i
t
> says I cannot use regular old EM to register the server on my laptop.|||Well - I found it...
Just like in the old version, it's installed from the same CD (actually
DVD!) that the server is installed from.
The difference, and what stopped me from going forward, was the I had to go
truly far into the install process - even putting in the product-key - to ge
t
to a selection list that allowed only the CLIENT TOOLS.
On a laptop that's already running MS SQL 2000 developers edition - that was
a big leap to take - possibly installed MS SQL 2005 on the laptop - which I
did not want to do.
The readme and help files are pretty vague in this area.
But at any rate - I've got it installed now on the laptop and it can see the
MS SQL 2005 server on the network and can even see my laptop instance runnin
g
MS SQL 2000.
Now I get to play!
"Matt" wrote:
[vbcol=seagreen]
> Apparently there are more people having the same problem. Microsoft should
> address this issue in a KB.
> Thanks
> Matt
> "Steve Z" wrote:
>|||Which Server do you mean? SBS or SQL? We have only 1 CD for SQL Server 2005
Standard. Any help is appreciated.
"Steve Z" wrote:
[vbcol=seagreen]
> Well - I found it...
> Just like in the old version, it's installed from the same CD (actually
> DVD!) that the server is installed from.
> The difference, and what stopped me from going forward, was the I had to g
o
> truly far into the install process - even putting in the product-key - to
get
> to a selection list that allowed only the CLIENT TOOLS.
> On a laptop that's already running MS SQL 2000 developers edition - that w
as
> a big leap to take - possibly installed MS SQL 2005 on the laptop - which
I
> did not want to do.
> The readme and help files are pretty vague in this area.
> But at any rate - I've got it installed now on the laptop and it can see t
he
> MS SQL 2005 server on the network and can even see my laptop instance runn
ing
> MS SQL 2000.
> Now I get to play!
> "Matt" wrote:
>|||I mean that the CLIENT TOOLS are installed from the same CD (in our case it'
s
actually a DVD from MS) that the SQL SERVER is installed from. That is the
same way the old SQL 2000 installed work.
The difference that struck me was that you were told early on in the install
process with SQL 2000 that the CLIENT TOOLS were only available (as the
machine is a workstation!).
With the SQL 2005 install CD you go through many steps, including the
licence-key (not required with SQL 2000 client install).
This appears that you are installing SQL SERVER on the workstation, but you
finally get to a selection screen where you just check off client tools...
"Matt" wrote:
[vbcol=seagreen]
> Which Server do you mean? SBS or SQL? We have only 1 CD for SQL Server 200
5
> Standard. Any help is appreciated.
> "Steve Z" wrote:
>

MS SQL 2005 Management Studio

Where do I find the Management Studio to install on my laptop?
I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and it
says I cannot use regular old EM to register the server on my laptop.Apparently there are more people having the same problem. Microsoft should
address this issue in a KB.
Thanks
Matt
"Steve Z" wrote:
> Where do I find the Management Studio to install on my laptop?
> I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and it
> says I cannot use regular old EM to register the server on my laptop.|||Well - I found it...
Just like in the old version, it's installed from the same CD (actually
DVD!) that the server is installed from.
The difference, and what stopped me from going forward, was the I had to go
truly far into the install process - even putting in the product-key - to get
to a selection list that allowed only the CLIENT TOOLS.
On a laptop that's already running MS SQL 2000 developers edition - that was
a big leap to take - possibly installed MS SQL 2005 on the laptop - which I
did not want to do.
The readme and help files are pretty vague in this area.
But at any rate - I've got it installed now on the laptop and it can see the
MS SQL 2005 server on the network and can even see my laptop instance running
MS SQL 2000.
Now I get to play!
"Matt" wrote:
> Apparently there are more people having the same problem. Microsoft should
> address this issue in a KB.
> Thanks
> Matt
> "Steve Z" wrote:
> > Where do I find the Management Studio to install on my laptop?
> >
> > I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and it
> > says I cannot use regular old EM to register the server on my laptop.|||Which Server do you mean? SBS or SQL? We have only 1 CD for SQL Server 2005
Standard. Any help is appreciated.
"Steve Z" wrote:
> Well - I found it...
> Just like in the old version, it's installed from the same CD (actually
> DVD!) that the server is installed from.
> The difference, and what stopped me from going forward, was the I had to go
> truly far into the install process - even putting in the product-key - to get
> to a selection list that allowed only the CLIENT TOOLS.
> On a laptop that's already running MS SQL 2000 developers edition - that was
> a big leap to take - possibly installed MS SQL 2005 on the laptop - which I
> did not want to do.
> The readme and help files are pretty vague in this area.
> But at any rate - I've got it installed now on the laptop and it can see the
> MS SQL 2005 server on the network and can even see my laptop instance running
> MS SQL 2000.
> Now I get to play!
> "Matt" wrote:
> > Apparently there are more people having the same problem. Microsoft should
> > address this issue in a KB.
> >
> > Thanks
> >
> > Matt
> >
> > "Steve Z" wrote:
> >
> > > Where do I find the Management Studio to install on my laptop?
> > >
> > > I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and it
> > > says I cannot use regular old EM to register the server on my laptop.|||I mean that the CLIENT TOOLS are installed from the same CD (in our case it's
actually a DVD from MS) that the SQL SERVER is installed from. That is the
same way the old SQL 2000 installed work.
The difference that struck me was that you were told early on in the install
process with SQL 2000 that the CLIENT TOOLS were only available (as the
machine is a workstation!).
With the SQL 2005 install CD you go through many steps, including the
licence-key (not required with SQL 2000 client install).
This appears that you are installing SQL SERVER on the workstation, but you
finally get to a selection screen where you just check off client tools...
"Matt" wrote:
> Which Server do you mean? SBS or SQL? We have only 1 CD for SQL Server 2005
> Standard. Any help is appreciated.
> "Steve Z" wrote:
> > Well - I found it...
> >
> > Just like in the old version, it's installed from the same CD (actually
> > DVD!) that the server is installed from.
> >
> > The difference, and what stopped me from going forward, was the I had to go
> > truly far into the install process - even putting in the product-key - to get
> > to a selection list that allowed only the CLIENT TOOLS.
> >
> > On a laptop that's already running MS SQL 2000 developers edition - that was
> > a big leap to take - possibly installed MS SQL 2005 on the laptop - which I
> > did not want to do.
> >
> > The readme and help files are pretty vague in this area.
> >
> > But at any rate - I've got it installed now on the laptop and it can see the
> > MS SQL 2005 server on the network and can even see my laptop instance running
> > MS SQL 2000.
> >
> > Now I get to play!
> >
> > "Matt" wrote:
> >
> > > Apparently there are more people having the same problem. Microsoft should
> > > address this issue in a KB.
> > >
> > > Thanks
> > >
> > > Matt
> > >
> > > "Steve Z" wrote:
> > >
> > > > Where do I find the Management Studio to install on my laptop?
> > > >
> > > > I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and it
> > > > says I cannot use regular old EM to register the server on my laptop.

MS SQL 2005 Management Studio

Where do I find the Management Studio to install on my laptop?
I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and it
says I cannot use regular old EM to register the server on my laptop.
Apparently there are more people having the same problem. Microsoft should
address this issue in a KB.
Thanks
Matt
"Steve Z" wrote:

> Where do I find the Management Studio to install on my laptop?
> I've just installed MS SQL 2005 on a SBS 2003 machine in the office, and it
> says I cannot use regular old EM to register the server on my laptop.
|||Well - I found it...
Just like in the old version, it's installed from the same CD (actually
DVD!) that the server is installed from.
The difference, and what stopped me from going forward, was the I had to go
truly far into the install process - even putting in the product-key - to get
to a selection list that allowed only the CLIENT TOOLS.
On a laptop that's already running MS SQL 2000 developers edition - that was
a big leap to take - possibly installed MS SQL 2005 on the laptop - which I
did not want to do.
The readme and help files are pretty vague in this area.
But at any rate - I've got it installed now on the laptop and it can see the
MS SQL 2005 server on the network and can even see my laptop instance running
MS SQL 2000.
Now I get to play!
"Matt" wrote:
[vbcol=seagreen]
> Apparently there are more people having the same problem. Microsoft should
> address this issue in a KB.
> Thanks
> Matt
> "Steve Z" wrote:
|||Which Server do you mean? SBS or SQL? We have only 1 CD for SQL Server 2005
Standard. Any help is appreciated.
"Steve Z" wrote:
[vbcol=seagreen]
> Well - I found it...
> Just like in the old version, it's installed from the same CD (actually
> DVD!) that the server is installed from.
> The difference, and what stopped me from going forward, was the I had to go
> truly far into the install process - even putting in the product-key - to get
> to a selection list that allowed only the CLIENT TOOLS.
> On a laptop that's already running MS SQL 2000 developers edition - that was
> a big leap to take - possibly installed MS SQL 2005 on the laptop - which I
> did not want to do.
> The readme and help files are pretty vague in this area.
> But at any rate - I've got it installed now on the laptop and it can see the
> MS SQL 2005 server on the network and can even see my laptop instance running
> MS SQL 2000.
> Now I get to play!
> "Matt" wrote:
|||I mean that the CLIENT TOOLS are installed from the same CD (in our case it's
actually a DVD from MS) that the SQL SERVER is installed from. That is the
same way the old SQL 2000 installed work.
The difference that struck me was that you were told early on in the install
process with SQL 2000 that the CLIENT TOOLS were only available (as the
machine is a workstation!).
With the SQL 2005 install CD you go through many steps, including the
licence-key (not required with SQL 2000 client install).
This appears that you are installing SQL SERVER on the workstation, but you
finally get to a selection screen where you just check off client tools...
"Matt" wrote:
[vbcol=seagreen]
> Which Server do you mean? SBS or SQL? We have only 1 CD for SQL Server 2005
> Standard. Any help is appreciated.
> "Steve Z" wrote: