How do i access the SQL server from a website.

How do I access the SQL server from a website, using my Machine Account, not the ASP.NET account?

thanks.

.intrino.On www.connectionstrings.com you can see all of the possible types of connection strings.

When you say "my machine account" do you mean a SQL Server Login, or using impersonation and your Windows account. If you want to use your Windows account, are both machines in the same Windows domain, and do you have a domain account?|||I want to use my account that is like so:

myDomain/Intrino

Instead the site connects as myDomain/ASPNET to the SQL server...and the connection string that i have set up is the SSPI and my IIS is setup as Windows Authentication and it setup as well in the web.config to use the Windows login.

I would like to connect as myDomain/Intrino...how do I transfer the login into the connection string?|||Anyone have any information on this?...|||You need to have ASP.NET run under a different account (your account).

In the Web.Config:

<identity impersonate="true" userName="domain\Jane" password="pass"/>|||So no way to the Web.Config dynammically to impersonate the user logged on?

Thanks for the answer.

.intrino.sql

how deploying a local database to target machine?

how deploying a local database to target machine?224071 - INF Moving SQL Server Databases to a New Location with Detach-Attach

How could I know the version of Reporting Services in my machine?

How could I know the version of Reporting Services in my machine?

thanks

SELECT @.@.version

Or take a look at this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=445611&SiteID=1

How can you determine which version of SQL Server is installed on a machine? -

How can you determine which version of SQL Server is installed on a machine?select @.@.version|||Try the below mentioned query to even find Product Version, Product Level as well as the edition of SQL Server ...

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

--Sandu_Bangalore

How can I verify that the sqlserver on my development is accessable from internet

Hello!
I'm trying to figure out if it's possible to reach the database on my
development machine from the outside (internet). To test this I'm trying to
connect to the database from the development machine by using my public IP
address. I also opned port 1433 in my firewall.
Is there any other ports I need to open? How can I verify that the sqlserver
on my development is accessable from internet?
Thanks!"Nutshell" <nospam@.nospam.com> wrote in message
news:%239FNk8bgHHA.596@.TK2MSFTNGP05.phx.gbl...

> I'm trying to figure out if it's possible to reach the database on my
> development machine from the outside (internet). To test this I'm trying
> to connect to the database from the development machine by using my public
> IP address. I also opned port 1433 in my firewall.
> Is there any other ports I need to open?
You'll want to give this a read (and some of the related links):
http://support.microsoft.com/kb/823938/en-us

> How can I verify that the sqlserver on my development is accessible from
> internet?
You should be able to use Query Analyzer or OSQL as a basic test
mechanism...
Steve|||Hello Steve,
I'll guess that the SQL Server need to use a static port?
1. From SQL Server Network Utility I'll see that port 1433 is default.
2. In the registry the settings looks like dynamic port allocation
3. The log displays:
2007-04-19 07:49:42.21 server SQL server listening on 192.168.0.6: 1433.
2007-04-19 07:49:42.34 server SQL server listening on 127.0.0.1: 1433.
2007-04-19 07:49:42.34 server SuperSocket Info: Bind failed on TCP port
1433.
2007-04-19 07:49:42.60 server SuperSocket Info: Bind failed on TCP port
1433.
I have tested to change the port to 1500, but I get the same bind error,
"Bind failed on TCP port 1500".
I have both SQL Server 9, and SQL Server Express on this machine. Is that
the problem?
Thanks!
"Steve Thompson" <stevethompson@.nomail.please> skrev i meddelandet
news:eOtYGIfgHHA.4916@.TK2MSFTNGP06.phx.gbl...
> "Nutshell" <nospam@.nospam.com> wrote in message
> news:%239FNk8bgHHA.596@.TK2MSFTNGP05.phx.gbl...
>
> You'll want to give this a read (and some of the related links):
> http://support.microsoft.com/kb/823938/en-us
>
> You should be able to use Query Analyzer or OSQL as a basic test
> mechanism...
> Steve
>

How can I verify that the sqlserver on my development is accessable from internet

Hello!
I'm trying to figure out if it's possible to reach the database on my
development machine from the outside (internet). To test this I'm trying to
connect to the database from the development machine by using my public IP
address. I also opned port 1433 in my firewall.
Is there any other ports I need to open? How can I verify that the sqlserver
on my development is accessable from internet?
Thanks!
"Nutshell" <nospam@.nospam.com> wrote in message
news:%239FNk8bgHHA.596@.TK2MSFTNGP05.phx.gbl...

> I'm trying to figure out if it's possible to reach the database on my
> development machine from the outside (internet). To test this I'm trying
> to connect to the database from the development machine by using my public
> IP address. I also opned port 1433 in my firewall.
> Is there any other ports I need to open?
You'll want to give this a read (and some of the related links):
http://support.microsoft.com/kb/823938/en-us

> How can I verify that the sqlserver on my development is accessible from
> internet?
You should be able to use Query Analyzer or OSQL as a basic test
mechanism...
Steve
|||Hello Steve,
I'll guess that the SQL Server need to use a static port?
1. From SQL Server Network Utility I'll see that port 1433 is default.
2. In the registry the settings looks like dynamic port allocation
3. The log displays:
2007-04-19 07:49:42.21 server SQL server listening on 192.168.0.6: 1433.
2007-04-19 07:49:42.34 server SQL server listening on 127.0.0.1: 1433.
2007-04-19 07:49:42.34 server SuperSocket Info: Bind failed on TCP port
1433.
2007-04-19 07:49:42.60 server SuperSocket Info: Bind failed on TCP port
1433.
I have tested to change the port to 1500, but I get the same bind error,
"Bind failed on TCP port 1500".
I have both SQL Server 9, and SQL Server Express on this machine. Is that
the problem?
Thanks!
"Steve Thompson" <stevethompson@.nomail.please> skrev i meddelandet
news:eOtYGIfgHHA.4916@.TK2MSFTNGP06.phx.gbl...
> "Nutshell" <nospam@.nospam.com> wrote in message
> news:%239FNk8bgHHA.596@.TK2MSFTNGP05.phx.gbl...
>
> You'll want to give this a read (and some of the related links):
> http://support.microsoft.com/kb/823938/en-us
>
> You should be able to use Query Analyzer or OSQL as a basic test
> mechanism...
> Steve
>

How can I troubleshoot eratic, slow SQL Backup job?

I have a SQL 2000 sp3 server running on a server class machine with
local drives.
I'm backing up a 50 gig db from the e partition to the F: partition.
Sometimes the backup takes 20 minutes...sometimes it takes 2.5 hours.
There are no jobs running when the backups execute, no index rebuilds,
no veritas, no virus scans running.
I'll run a backup and it will take 20 minutes. I rerun it again
right away and it takes 2.5 hours.
I run a statistics IO trace, and the only difference is the cumulative
wait time...which is much much higher when the backup takes 2.5 hours.
Any suggestions on how to troubleshoot this? Or why it might be
happening?On Apr 16, 5:51 pm, "Sanctus" <mch...@.hotmail.com> wrote:
> I have a SQL 2000 sp3 server running on a server class machine with
> local drives.
> I'm backing up a 50 gig db from the e partition to the F: partition.
> Sometimes the backup takes 20 minutes...sometimes it takes 2.5 hours.
> There are no jobs running when the backups execute, no index rebuilds,
> no veritas, no virus scans running.
> I'll run a backup and it will take 20 minutes. I rerun it again
> right away and it takes 2.5 hours.
> I run a statistics IO trace, and the only difference is the cumulative
> wait time...which is much much higher when the backup takes 2.5 hours.
> Any suggestions on how to troubleshoot this? Or why it might be
> happening?
Here are some ideas...
E: to F: - are these different drives on a san and does the backup
have to go accross the network - higher network traffic at times?
Network saturation?
Are their heavier user processes at times? Heavy duty queries/long
running transactions?
Is this a dedicated SQL Server, could another application be hogging
the Memory or IO?
As you can see, I am just shooting blind. Maybe some of these ideas
can help you think how to investigate?

How can I troubleshoot eratic, slow SQL Backup job?

I have a SQL 2000 sp3 server running on a server class machine with
local drives.
I'm backing up a 50 gig db from the e partition to the F: partition.
Sometimes the backup takes 20 minutes...sometimes it takes 2.5 hours.
There are no jobs running when the backups execute, no index rebuilds,
no veritas, no virus scans running.
I'll run a backup and it will take 20 minutes. I rerun it again
right away and it takes 2.5 hours.
I run a statistics IO trace, and the only difference is the cumulative
wait time...which is much much higher when the backup takes 2.5 hours.
Any suggestions on how to troubleshoot this? Or why it might be
happening?On Apr 16, 5:51 pm, "Sanctus" <mch...@.hotmail.com> wrote:
> I have a SQL 2000 sp3 server running on a server class machine with
> local drives.
> I'm backing up a 50 gig db from the e partition to the F: partition.
> Sometimes the backup takes 20 minutes...sometimes it takes 2.5 hours.
> There are no jobs running when the backups execute, no index rebuilds,
> no veritas, no virus scans running.
> I'll run a backup and it will take 20 minutes. I rerun it again
> right away and it takes 2.5 hours.
> I run a statistics IO trace, and the only difference is the cumulative
> wait time...which is much much higher when the backup takes 2.5 hours.
> Any suggestions on how to troubleshoot this? Or why it might be
> happening?
Here are some ideas...
E: to F: - are these different drives on a san and does the backup
have to go accross the network - higher network traffic at times?
Network saturation?
Are their heavier user processes at times? Heavy duty queries/long
running transactions?
Is this a dedicated SQL Server, could another application be hogging
the Memory or IO?
As you can see, I am just shooting blind. Maybe some of these ideas
can help you think how to investigate?

How can I troubleshoot eratic, slow SQL Backup job?

I have a SQL 2000 sp3 server running on a server class machine with
local drives.
I'm backing up a 50 gig db from the e partition to the F: partition.
Sometimes the backup takes 20 minutes...sometimes it takes 2.5 hours.
There are no jobs running when the backups execute, no index rebuilds,
no veritas, no virus scans running.
I'll run a backup and it will take 20 minutes. I rerun it again
right away and it takes 2.5 hours.
I run a statistics IO trace, and the only difference is the cumulative
wait time...which is much much higher when the backup takes 2.5 hours.
Any suggestions on how to troubleshoot this? Or why it might be
happening?
On Apr 16, 5:51 pm, "Sanctus" <mch...@.hotmail.com> wrote:
> I have a SQL 2000 sp3 server running on a server class machine with
> local drives.
> I'm backing up a 50 gig db from the e partition to the F: partition.
> Sometimes the backup takes 20 minutes...sometimes it takes 2.5 hours.
> There are no jobs running when the backups execute, no index rebuilds,
> no veritas, no virus scans running.
> I'll run a backup and it will take 20 minutes. I rerun it again
> right away and it takes 2.5 hours.
> I run a statistics IO trace, and the only difference is the cumulative
> wait time...which is much much higher when the backup takes 2.5 hours.
> Any suggestions on how to troubleshoot this? Or why it might be
> happening?
Here are some ideas...
E: to F: - are these different drives on a san and does the backup
have to go accross the network - higher network traffic at times?
Network saturation?
Are their heavier user processes at times? Heavy duty queries/long
running transactions?
Is this a dedicated SQL Server, could another application be hogging
the Memory or IO?
As you can see, I am just shooting blind. Maybe some of these ideas
can help you think how to investigate?