Database Explorer

Table to Insert Incremental Values

databaseexplorer — Thu, 22 Oct 2009 16:40:00 +0000

Objective: To populate multiple incremental values in table.

Create Table test (val float)
insert into test values (0.001)
declare @t float
select @t = max(val) from test
Insert into test
select val + @t from test

Or
DECLARE @idt float
SET @idt = 0
WHILE (@idt < 10)
BEGIN
SELECT @idt = @idt + 0.001
insert into tablename (columnname)
select @idt
END

DECLARE @idt int
SET @idt = 0
WHILE (@idt < 100)
BEGIN
SELECT @idt = @idt + 1
insert into tablename (columnname)
select @idt
END

>Export Import Tool – Microsoft VSS to Vault Source Gear

databaseexplorer — Tue, 22 Sep 2009 16:12:00 +0000

>Objective: To import all files from Microsoft to Source Gear

Install tools from source gear website

http://www.sourcegear.com/vault/downloads2.html

Installation will carry forward like below from VSS Import Tool

Give the path where the file comes from. For example the network path from microsoft Visual source safe and their credentials

The below screen shot is vault admin username and password

click on Continue when the error raises something like below:

once examining the project, all microsoft VSS will be imported to Source Gear.

>Vault Source Gear Installation

databaseexplorer — Tue, 22 Sep 2009 16:02:00 +0000

>Objective: To install source gear in windows 2003 server

http://www.sourcegear.com/vault/support/install/

Source Gear File for installing ver 4

Once installed, you can access through Program Files from Windows OS

The below screen shot is the admin page where you can manage everything (For eg. Add users, import, export etc)

Export Import Tool – Microsoft VSS to Vault Source Gear

databaseexplorer — Tue, 22 Sep 2009 16:12:00 +0000

Objective: To import all files from Microsoft to Source Gear

Install tools from source gear website

http://www.sourcegear.com/vault/downloads2.html

Installation will carry forward like below from VSS Import Tool

Give the path where the file comes from. For example the network path from microsoft Visual source safe and their credentials

The below screen shot is vault admin username and password

click on Continue when the error raises something like below:

once examining the project, all microsoft VSS will be imported to Source Gear.

Vault Source Gear Installation

databaseexplorer — Tue, 22 Sep 2009 16:02:00 +0000

Objective: To install source gear in windows 2003 server

http://www.sourcegear.com/vault/support/install/

Source Gear File for installing ver 4

Once installed, you can access through Program Files from Windows OS

The below screen shot is the admin page where you can manage everything (For eg. Add users, import, export etc)

>SQL Agent Jobs – Permission

databaseexplorer — Mon, 14 Sep 2009 16:07:00 +0000

SQLAgentReaderRole

The SQLAgentReaderRole is a database role located in the msdb database. It is one of three new roles in this database aimed at allowing the database administrator the ability to assign more granular permissions when it comes to the administration of SQL Agent jobs. Assigning a user or group to be a member of this role allows the user to see any SQL Agent job located on the server instance, even the jobs in which that user does not own. The user can see the job, along with any history saved to the job. However, the group is not allowed to execute the jobs. To add a user as a member of the SQLAgentReaderRole, you can execute the following command:

use msdb

EXECUTE sp_addrolemember

@rolename = 'SQLAgentReaderRole',

@membername = 'username'

It is also worth mentioning the other two SQL Agent roles available in SQL Server 2005. The SQLAgentUserRole allows users to create jobs and to manage the jobs that they create. The SQLAgentOperatorRole allows users all of the rights assigned to the SQLAgentReaderRole along with the permissions necessary to execute local jobs that they do not own.

Further you can view some more details in this below blog:

http://blogs.techrepublic.com.com/datacenter/?p=428

SQL Agent Jobs – Permission

databaseexplorer — Mon, 14 Sep 2009 16:07:00 +0000

SQLAgentReaderRole

use msdb

EXECUTE sp_addrolemember

@rolename = 'SQLAgentReaderRole',

@membername = 'username'

Further you can view some more details in this below blog:

http://blogs.techrepublic.com.com/datacenter/?p=428

>Route Add

databaseexplorer — Thu, 10 Sep 2009 15:10:00 +0000

Static Route Add in the server:

If you cannot ping or net use, then you may manually add the route in the server where you are targeting

route ADD 10.1.1.0 MASK 255.255.255.0 192.168.1.8

10.1.1.0 or 10.1.1.12 – Destination IP or Destination Subnet or Target Server IP

255.255.255.0 – Target or Destination Server subnet mask

192.168.1.8 – Gateway IP Address – Target Server Gateway

Adding a TCP/IP Route to the Windows Routing Table

Adding routes to your machine is a useful testing tool for some of these situations.

Or another explanation is:

Syntax:

route ADD “network” MASK “subnet mask” “gateway ip”

For example, if you were on the 192.168.1.0 network, and you had a gateway on 192.168.1.12 configured to access the 10.10.10.0/24 network, you would use a route add statement like this:

route ADD 10.10.10.0 MASK 255.255.255.0 192.168.1.12

Your routing table should now reflect that change, and all traffic to the 10.10.10.x range will now be sent over to the gateway machine.

The route add change will only stick across reboots if you add it with the -p flag, as in the following:

route -p ADD 10.10.10.0 MASK 255.255.255.0 192.168.1.12
route -p add 10.0.1.0 mask 255.255.255.0 10.0.0.2

Please see below link as well

http://www.mydigitallife.info/2008/12/25/how-to-add-route-to-tcpip-routing-table-with-windows-routing-and-remote-access-console-or-dos-prompt/

Route Add

databaseexplorer — Thu, 10 Sep 2009 15:10:00 +0000

Static Route Add in the server:

If you cannot ping or net use, then you may manually add the route in the server where you are targeting

route ADD 10.1.1.0 MASK 255.255.255.0 192.168.1.8

10.1.1.0 or 10.1.1.12 – Destination IP or Destination Subnet or Target Server IP

255.255.255.0 – Target or Destination Server subnet mask

192.168.1.8 – Gateway IP Address – Target Server Gateway

Adding a TCP/IP Route to the Windows Routing Table

Adding routes to your machine is a useful testing tool for some of these situations.

Or another explanation is:

Syntax:

route ADD “network” MASK “subnet mask” “gateway ip”

For example, if you were on the 192.168.1.0 network, and you had a gateway on 192.168.1.12 configured to access the 10.10.10.0/24 network, you would use a route add statement like this:

route ADD 10.10.10.0 MASK 255.255.255.0 192.168.1.12

Your routing table should now reflect that change, and all traffic to the 10.10.10.x range will now be sent over to the gateway machine.

The route add change will only stick across reboots if you add it with the -p flag, as in the following:

route -p ADD 10.10.10.0 MASK 255.255.255.0 192.168.1.12
route -p add 10.0.1.0 mask 255.255.255.0 10.0.0.2

Please see below link as well

http://www.mydigitallife.info/2008/12/25/how-to-add-route-to-tcpip-routing-table-with-windows-routing-and-remote-access-console-or-dos-prompt/

>How to fix orphaned SQL Server users

databaseexplorer — Thu, 10 Sep 2009 13:42:00 +0000

——————————————————————————–

Brief:

When you restore a MS SQL Server database on a different machine, you cannot access the database until you fix the permissions.

——————————————————————————–

Detail

The problem is that the user in the database is an “orphan”. This means that there is no login id or password associated with the user. This is true even if there is a login id that matches the user, since there is a GUID (called a SID in Microsoft-speak) that has to match as well.

All of these should be done as a database admin, with the restored database selected.

Firstly, make sure that this is the problem. This will lists the orphaned users:

EXEC sp_change_users_login ‘Report’

If you already have a login id and password for this user, fix it by doing:

EXEC sp_change_users_login ‘Auto_Fix’, ‘user’

If you want to create a new login id and password for this user, fix it by doing:

EXEC sp_change_users_login ‘Auto_Fix’, ‘user’, ‘login’, ‘password’