Er mag maar 1 binding staat op iis.
Tijdens de installatie worden er 2 ingezet. De server naam en de url van de website.
Heb ze beide weggehaald en 1 binding neergezet die luistert naar alle aanvragen.
Een bug dus.
Als ik veel moet copy-pasten gaat er altijd een belletje rinkelen. .. t.b.c.
1. Suppose you are inserting an (in humanly eyes) large dataset (say 200.000 records) into a target table and this gives a primary key violation. The question is which record(s) cause this violation.
e.g. insert into target select * from source
Troubleshoot technique I)
Insert the dataset into a table wihout constraints (no prim key) and
e.g. insert into test_target select * from source
Ia) select on the fields that make the primary key with a having count(*)>1 option to get the duplicate records.
select column1, column2 from test_target group by column1, column2 having count(*)>1
Ib) Inner join the result with the target table to get already present records.
select * from test_target t
inner join target on t.column1=target.column1 and t.column2 =target.column2
2. How to find out which records caused an error in an SSIS Data flow task.
3. Suppose you have a very large primary key (say 10 columns). Is there a solution to the annoying fact that you have to join every column every time.
Make a new job and add the following T-SQL step:
declare @path as nvarchar(500) set @path = N'D:\Data\Backup\DbName_'+convert(varchar, year(getdate())) + '_' + convert(varchar, month(getdate()))+ '_' + convert(varchar, day(getdate()))+'.bak' select @path BACKUP DATABASE [DbName] TO DISK = @path WITH NOFORMAT, NOINIT, NAME = N'DbName-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10 GO
Step 1.
Download and install the SAS OLE/DB Connector, here. http://support.sas.com/techsup/. Apparantly installing just a OLE/DB client still takes about 700MB’s these days. (I used the Client only setting)
Step 2.
In your SSIS package create a new OLE DB Connection Manager.
type: Native OLE DB\SAS Local Data Provider 9.3
In the Server name or file name textbox fill in the Path to the folder than contains the sas7bdat files. (or use advanced connection properties and fill in the Datasource ).
Enter V7 in the SAS file format (advanced properties) or something like this depending on your version
Step 3.
The files in the folder specified in step 2 with sas7bdat extension are your tables. Create a new data flow task and place a OLE DB Source in here, when you click on name of table or view, you will see the filename.
Step 4.
Create an OLE DB Destination for MSSQL and map all columns. All datatypes should be retained.
Step 5.
Connect Source with destination.
Step 6.
Go with the flow. Execute package.
Step 7.
We discovered that date fields are supplied as a float that represents the offset versus Jan-01-1960.
Bekijk hier ons artikel dat is gepubliceerd in database magazine(DBM) van December 2011
Een inleiding in Anchor Modeling, plus de voor- en nadelen.
We horen graag uw mening.
with date_gen as(
select cast(’2005-01-01′ as datetime) d
union all
select d + 1
from date_gen
where d + 1 < ’2079-01-01′
)
select d date_id, CONVERT(varchar, d,107) date_description,
YEAR(d) *100 + MONTH(d) date_year_month, YEAR(d) date_year,
MONTH(d) date_month, datename(month, d) date_month_name
from date_gen
OPTION (MAXRECURSION 0)
Eind November verschijnt in Database Magazine (DB/M) een artikel over Anchor Modeling. Een agile modeleertechniek in de zesde normaalvorm die veel overeenkomsten heeft met Data Vault.